Access Governance Overview
Route Risotto access requests through an external approval and fulfillment platform like Opal or Okta Identity Governance
Access governance integrations let Risotto hand off an access request to an external approval and fulfillment platform instead of granting the access itself. The requester still starts in Slack with Risotto, but the approval workflow, policy evaluation, and the actual grant happen in your governance tool — and the audit trail lives there.
When to use access governance
Use an access governance provider when:
- Your organization already runs access requests, approvals, and reviews in a dedicated platform (Opal, Okta Identity Governance) and wants that to remain the system of record.
- You need approval workflows, time-bound (just-in-time) grants, or segregation-of-duty policies that live outside Risotto.
- You want a single, auditable approval trail in your governance tool while still letting employees request access conversationally through Slack.
If you instead want Risotto to evaluate access rules and update group memberships directly, configure an Identity Provider — no access governance provider is required.
How it works
User requests access in Slack
An employee asks Risotto for access to an application, the same way they would for any other request.
Risotto collects what the provider needs
Risotto gathers the fields the governance platform requires (for example, a business justification or a specific access level) before dispatching the request, so the hand-off succeeds on the first try.
Risotto dispatches to the provider
Instead of granting access itself, Risotto submits the request to the configured access governance provider on the user's behalf.
Approval happens in the provider
Reviewers approve or deny the request in Opal or Okta — using their existing policies and workflows. Risotto links back to the request so everyone can follow along.
Risotto reflects the outcome
When the provider resolves the request (approved, denied, or fulfilled), Risotto updates the Slack thread and the ticket. Risotto receives outcomes through a secure webhook, with a reconciliation backstop that keeps state accurate even if an event is missed.
Available providers
Connect Opal (opal.dev) as an access governance provider so Risotto routes requests into Opal's approval and fulfillment workflows.
Okta Identity GovernanceSubmit access requests through Okta Identity Governance (OIG) using Access Requests V2 (RCAR).
Provider versus Identity Provider
| Capability | Identity Provider | Access Governance Provider |
|---|---|---|
| Reads groups and memberships | ✅ Yes | ❌ No |
| Grants access directly | ✅ Risotto updates group membership | ❌ The provider performs the grant |
| Owns the approval workflow | ❌ Risotto / runbooks | ✅ The provider |
| System of record for the audit trail | Risotto | The provider (Opal / Okta) |
| Can be combined with the other axis | ✅ Use IdP for identity | ✅ Use a provider for fulfillment |
Per-application selection
Access governance is configured per application. When you import or edit an application in Risotto, you choose how its access is fulfilled — directly through your IdP, or by routing requests to a connected access governance provider. Applications that are not routed to a provider continue to use your existing access rules.
Next steps
Something wrong or missing? Report an issue · View as Markdown