Iru + Risotto: device support in Slack and Teams, without the console

Risotto connects to Iru (formerly Kandji) so device requests get resolved in Slack and Microsoft Teams. Risotto looks up devices, locks lost ones, and retrieves FileVault recovery keys, unlock PINs and Recovery Lock passwords. By default it acts on the requester’s own devices, with the approvals you set. IT can add more Iru actions from a ready-made API template.

Book a demo

Risotto · Direct message
  1. Maya Patel8:15 AM

    I forgot my Mac's FileVault password after an update.
  2. RisottoApp8:15 AM

    Let's confirm it's you. I've sent an Okta Verify push to your phone.

    ✓ Verified with Okta Verify

  3. RisottoApp8:16 AM

    FileVault recovery key for your MacBook Pro (serial C02FX4Q1MD6T, last check-in today):

    T7KQ-••••-••••-••••-••••-9WMX

    Logged to the ticket

Device fixes in chat, not in the queue

  • Device details. Look up a device by email or serial number: model, OS version, last check-in, Blueprint and installed apps.
  • Lock a lost device. Remotely lock an Apple or Android device. For a Mac, Risotto returns the 6-digit unlock PIN.
  • Unlock PINs. Retrieve the PIN for a Mac locked by an MDM command.
  • FileVault recovery keys. Get a locked-out employee back into their Mac.
  • Recovery Lock passwords. For Apple silicon Macs, or the firmware password for Intel Macs.
  • Audit log search. Dig into lock problems, enrollment issues and MDM command history.
  • More Iru actions. Add restart, Lost Mode, Blueprints, tags and Prism reports from the ready-made Iru API template. IT tests and approves each tool before it runs.

Security for every device action

  • The requester’s own devices. By default, each Iru tool acts only on devices assigned to the person asking.
  • Approvals you choose. Require IT or manager approval before a lock or key retrieval.
  • Identity checks. Ask for an Okta Verify push or an Okta sign-in before Risotto returns a key or PIN.
  • A log of every action. Who asked, which device, what Risotto did, and when.

Up and running in three steps

  1. Connect Iru with an API token scoped to what you want Risotto to do.
  2. Set the rules. Choose the tools Risotto can use, who can use them, and which need approval or an identity check.
  3. Employees ask in Slack or Teams. Risotto runs the right Iru action, or escalates with the device details attached.

Frequently asked questions

What Iru actions can Risotto run?

Risotto looks up devices, locks them, retrieves unlock PINs, FileVault recovery keys and Recovery Lock passwords, and searches Iru audit events. IT can add more actions from the Iru API template. Automations

Does Risotto work with Kandji?

Yes. Kandji is now Iru, and Risotto’s Iru integration works with your Kandji tenant and API token.

Can we control which employees can run device actions?

Yes. You choose which tools Risotto can use, who can use them, and which need approval or an identity check. By default, each tool acts only on the requester’s own devices.

What happens when a request needs IT?

Risotto opens a ticket with the conversation and device details, so the employee never repeats themselves. The Assistant investigates, posts a plan and works through it, with IT approving each change.

Let your IT team build a workflow once, and let Risotto run it

Book a demo