# Opal + Risotto: access requests from Slack and Teams, governed by Opal

Risotto gives employees one place to ask for access: Slack or Microsoft Teams. For the apps, resources, groups and bundles you govern in Opal, Risotto files the request with the business reason and duration. Opal's reviewers decide, and Risotto reports the outcome in the same thread. Controls built for security, and fast access for everyone else.

[Book a demo](/demo)

## Access requests in plain words, governed by Opal

- **Your Opal catalog, in chat.** Import Opal apps, resources, groups and bundles as access employees can ask for, at the level you choose.
- **Requests understood.** Employees describe what they need. Risotto matches the right Opal item and asks a follow-up when something is missing.
- **Filed for the employee.** Risotto submits the request in Opal with the business reason and duration.
- **Sensible time windows.** Risotto honors the duration asked for, up to your maximum, or uses the recommended one, and tells the employee their window.
- **Outcome in the thread.** When Opal approves or denies, Risotto updates the thread and the ticket.
- **One click to Opal.** Each request links to its item in your Opal catalog.

## Live in three steps

1. **Connect Opal.** Your policies, reviewers and roles stay as they are.
2. **Choose what employees can request.** Import the Opal items you want in chat, and set access levels and time limits.
3. **Employees ask.** In Slack or Teams. Opal decides, and Risotto keeps the employee informed and logs each step.

[Read the setup guide](/docs/integrations/access-governance/opal)

## Opal stays in charge of access

Risotto adds the conversation. Opal keeps the controls.

- **Least privilege, enforced.** Opal's policies and reviewers decide every request Risotto files.
- **Time limits that enforce themselves.** The duration goes to Opal with the request, so access ends on time and no standing access builds up.
- **A record in both places.** The request and decision live in Opal. The conversation and outcome live on the Risotto ticket.

For access you manage in your identity provider, Risotto can grant it directly, with approval policies. See [Okta](/integrations/okta) and [Access and approvals](/product/access-requests).

> "Our target SLA was 2 days and we're now beating that, averaging only 1 day to ticket close using Risotto." — Charlie Verrey, IT Manager, Retool

## Frequently asked questions

### Does Risotto replace Opal?

Risotto works on top of Opal, which stays your access governance system and system of record. Risotto is the front door in Slack and Teams that files requests in Opal and keeps employees informed.

### Who approves Opal requests that come through Risotto?

Opal's reviewers, in Opal, as they do today. Risotto files the request with the business reason and reports the decision in the thread.

### How does time-limited access work with Opal?

Risotto sends the duration to Opal with the request, capped at your maximum. Opal removes the access when the window closes, so nobody has to follow up.

### Does this change our Opal configuration?

No. Risotto works with your existing Opal policies, roles and approval workflows. You choose which Opal items appear in Risotto.

### Can Risotto use Okta Identity Governance instead of Opal?

Yes. Risotto also files access requests in Okta Identity Governance. [Okta integration](/integrations/okta)

## See how access requests flow from Slack into Opal

[Book a demo](/demo)

Source: https://www.tryrisotto.com/integrations/opal
