Use case
Identity governance, automated from first request to last day
Risotto automates identity governance in Slack and Microsoft Teams. Employees ask for access in plain words. Risotto gets the approval your policy requires, grants access through your identity provider and removes it when time is up. It acts on its own when Rippling, BambooHR or HiBob reports a hire or a departure, and every step is on record for your audit.
Access sprawl starts in a Slack thread
Before Risotto, most access starts as a message to IT. Someone finds the approver in a spreadsheet, chases them in a DM, adds the person to a group by hand, and nobody removes the access later. Standing access builds up, and the audit evidence is spread across threads. A governance portal fixes the controls, but it gives employees one more tool to learn.
“Managing access requests manually is never a good idea because it’s error prone, inconsistent, and your time-to-resolution suffers.”
How does Risotto automate access governance?
Risotto runs each access request as one flow in Slack or Teams, with a ticket behind it.
- The employee asks. “I need Salesforce for the Q4 project” is enough. Risotto asks only for what is missing, such as the duration or a business reason.
- Your policy picks the approver. Risotto checks the business reason, and the manager or app owner approves in Slack, Teams or email.
- Your identity provider grants it. Risotto adds the employee to the right group in Okta, Microsoft Entra ID, Google Workspace or JumpCloud. For an app with no group, the access rule runs a script tool that grants access through the app’s API. For access you govern in Opal or Okta Identity Governance, Risotto files the request there and reports the decision in the thread.
- Access ends on time. Risotto offers a renewal before the window closes, can require approval again, and removes the access when time is up, through the same group or script that granted it.
- Every step is on record, on the ticket and on the access grants page.
Dec 8 · Ana's DM
Dec 12 · The ticket
Joiners, movers and leavers, handled from HR events
Risotto automations start on their own when your HR system or Okta reports a change, so access follows the employee without a ticket.
- Joiner. Rippling reports a new hire. Risotto activates the Okta account and adds the groups for their team.
- Mover. BambooHR reports a status change, such as a contractor who becomes full time. Risotto updates their groups to match.
- Leaver. HiBob reports a departure. Risotto removes the Okta groups, suspends the Google Workspace account and moves Drive files to the manager.
Okta events, such as a deactivated account, can start an automation too. You choose which steps wait for IT approval.
IT sets the rules. Risotto follows them.
Risotto changes access only inside the rules IT writes.
- An access rule for each app and role. It names the group, or the script tool that grants and removes access through the app’s API, plus who may ask, whether a reason is required, the maximum duration and the approval policy.
- Approval policies you write once, such as “contractors need IT approval, employees do not”, for access rules, tools and runbook steps.
- Block self-approval, so nobody approves their own access.
- Verified requesters. Before a sensitive change, the requester confirms who they are with an Okta Verify push or a sign-in to your Okta.
Adding a new app is one request to the Assistant. It drafts the access rule on an approval card, and the rule grants nothing until you turn it on.
Who has what, until when, ready for the audit
Risotto keeps the records an access review or a SOC 2 audit asks for.
- The access grants page lists every grant Risotto made, with its holder, ticket and expiry date. Expire a grant now, make it permanent, or export a CSV.
- The ticket holds every step: who asked, who approved, what changed and when.
- The audit log records configuration changes, such as an edited approval policy. Your SIEM reads it through the audit-events API.
- A removal that fails gets flagged, not dropped. If an app’s removal script fails, IT gets an alert, and the grant stays on the access grants page until someone retries it with “Expire access now”.
“Our control for SOC 2 is that access to privileged systems is approved by a manager. Risotto is able to automate the approval process and ticket tracking portion which is exactly what we needed.”
Results on access requests
Ironclad reports a 91% autosolve rate on access requests with Risotto. It now writes an access rule as a standard step each time it buys a new app. Read the Ironclad story
Frequently asked questions
What is IGA automation?
IGA (identity governance and administration) automation requests, approves, grants, removes and records access without manual work. Risotto does this in Slack and Microsoft Teams, on top of Okta, Microsoft Entra ID, Google Workspace or JumpCloud, and keeps a record of every grant.
Can Risotto automate just-in-time access?
Yes. Each Risotto access rule sets how long access lasts. Risotto grants it through your identity provider, or through a script tool for an app with no group, and removes it the same way when the window closes. Renewals can require approval again. Access requests
Can Risotto remove access when an employee leaves?
Yes. A Risotto automation starts when Rippling, BambooHR or HiBob reports a termination, or when Okta reports a deactivated account. It runs the offboarding steps you write, with approval where you require it. For an app reached through a script tool, asking Risotto to revoke someone’s access runs the script’s remove step even if that access was granted outside Risotto, so it can clean up an account someone set up by hand. Automations
How does Risotto help with access reviews and audits?
Risotto’s access grants page lists every grant with its holder, ticket and expiry date, and exports to CSV. Each request’s approvals and changes are on its ticket, and configuration changes go to an audit log that your SIEM can read. Security and trust
