# 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.

> **Note:** **Access governance is different from an Identity Provider (IdP)
> integration.** An [IdP integration](https://www.tryrisotto.com/docs/integrations/idp/okta) is about
> *directory sync and group membership* — Risotto reads groups and can add or
> remove users directly. Access governance is about *delegated fulfillment* —
> Risotto submits a request to an external system that owns the approval
> workflow and performs the grant. The two are independent: you can use Okta for
> identity **and** a separate platform for access fulfillment at the same time.

## 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](https://www.tryrisotto.com/docs/integrations/idp/okta) — no access governance provider is required.

## How it works

1. **User requests access in Slack**

   An employee asks Risotto for access to an application, the same way they would for any other request.

2. **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.

3. **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.

4. **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.

5. **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

- [Opal](https://www.tryrisotto.com/docs/integrations/access-governance/opal): Connect Opal (opal.dev) as an access governance provider so Risotto routes requests into Opal's approval and fulfillment workflows.
- [Okta Identity Governance](https://www.tryrisotto.com/docs/integrations/access-governance/okta-identity-governance): Submit 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  |

> **Tip:** These axes are independent. A customer can connect Okta as their identity
> provider for group membership **and** route fulfillment through Opal — the two
> integrations do not conflict.

## 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

- [Connect Opal](https://www.tryrisotto.com/docs/integrations/access-governance/opal)
- [Connect Okta Identity Governance](https://www.tryrisotto.com/docs/integrations/access-governance/okta-identity-governance)

Source: https://www.tryrisotto.com/docs/integrations/access-governance/overview
