Access requests in Slack and Teams, granted in Okta and removed on time
Employees ask for apps in Slack or Microsoft Teams, and Risotto gets whatever approval your access rule requires before it touches Okta.
How do I automate access requests in Slack or Teams with Okta?
Connect Okta and Slack or Teams to Risotto, then give each app an access rule: its Okta group, who may ask, how long access lasts and its approval policy. When someone asks, Risotto checks they don’t already have the app and asks only for what’s missing.
91% of access requests auto-solved at Ironclad. Read the Ironclad story
“The problem we faced is other AI support bots were not confident in themselves. If you asked, ‘Can I have access to Salesforce?’ It would respond, ‘do you want access to Salesforce?’ Or worse it wouldn’t find the app at all.”
Write “contractors need IT approval” once
A Risotto approval policy attaches to access rules, tools and runbook steps, so one edit changes all of them.
- Who it covers: employment type, department or group membership from your identity provider.
- Who approves: the requester’s manager, named people, a group or a Slack channel, answering in Slack, Teams or email. Pick a group, and one person’s vacation doesn’t strand a request.
- Steps: add more than one approver step, such as the manager and then IT. Risotto asks them in order or all at once, and needs a yes from any one of them or from all of them.
- Tools: the AI can’t loosen a tool’s approvals. The Assistant can add an approval requirement, but only a person can remove one.
Business reasons that actually say something
Tell Risotto what a good reason looks like for an app, such as “name the customer or project”, and it checks each one before access is granted. A vague one goes back to the employee with a question.
“We always wanted to require a reason for application access, but it was really difficult to integrate that into JSM. Risotto adds that functionality to JSM and so much more.”
Time-bound access that removes itself
Each Risotto access rule sets how long someone can hold the app. Before it ends, Risotto offers a one-click renewal, which can require a new approval. Skip it, and the access is gone on the end date.
No Okta group for it? A script grants access and takes it back.
Your apps with no Okta group or SCIM still get approvals and end dates in Risotto. Give the app’s access rule a script tool, which the Assistant writes for you against the app’s API. Once the request is approved, the script grants access. When access ends, the same script removes it.
An engineer asks for Sentry for 14 days to debug checkout errors from the last release. Their manager approves in Slack, the script invites them to your Sentry org on the checkout team, and on day 14 it takes them out again. If a removal ever fails, Risotto doesn’t pretend it worked: IT gets an alert, and the grant stays open until someone retries it with “Expire access now”.
The page your auditor will ask for
Risotto’s access grants page lists every grant it made, with the holder, the requester, the ticket and the expiry date. Expire a grant on the spot, make one permanent, or export a CSV for your access review.
“Before Risotto compliance reports could take days to figure out but now I can pull everything needed in seconds.”
Your identity provider stays the system of record
With Risotto, access is granted in your identity provider’s own groups, by your governance tool, or through the app’s own API.
| Tool | What Risotto does |
|---|---|
| Okta, Microsoft Entra ID, Google Workspace, JumpCloud | Adds and removes group members, with end dates |
| Okta Identity Governance, Opal | Collects the details in chat, then hands the request over for that tool’s own approvals |
| Any other app | A script tool on the access rule grants and removes access through the app’s API, or the app owner gets an approved, complete request |
Frequently asked questions
Can I stop employees approving their own access requests?
Yes. Turn on self-approval blocking for an approval chain in Risotto, and requesters can’t approve their own requests.
Can Risotto check who is really asking?
Yes. Before a sensitive tool runs, Risotto can ask for an Okta Verify push or a sign-in to your own Okta. Security and trust
Can Risotto grant and remove access in apps that aren’t connected to Okta?
Yes. Give the app’s access rule a script tool, and Risotto runs it against the app’s API: it grants access once the request is approved and removes it when access ends. Each rule runs one script with its own settings, such as the role, so an app with a member role and an admin role gets a rule for each. Script tools
Does Risotto keep a record of each access request?
Yes. Each Risotto access request is a ticket that records the approval and every step taken. See ticketing

