# Access Grants

See every access request and revocation Risotto has handled: who got which access, on which ticket, and when it expires. Expire a grant early or make it permanent.

The [Access Grants page](https://dashboard.tryrisotto.com/access-grants) is the ledger of every access request and revocation Risotto has handled: who received access, to which application, on which ticket, and when that access is set to expire. A single ticket can carry more than one grant (a new-hire request might provision three applications at once), and this page lists each grant as its own row, so you audit grants rather than re-reading ticket threads.

[Access rules](https://www.tryrisotto.com/docs/dashboard/applications/access-rules) define *how* access gets granted. The Access Grants page shows *what actually happened* as a result.

To watch one request asked and approved in Slack, then found here, expired early and exported, see the [three-minute video](https://www.tryrisotto.com/docs/guides/access-requests-video).

> **Note:** Open **Access Grants** from the sidebar. You see the grants whose tickets are
> in a department where you can read tickets, as an Agent or Supervisor. A grant
> without a ticket does not show.

## The grants list

The table has one row per grant, newest first, with these columns:

- **Status**: the request's status, for example **Awaiting Approval**, **Awaiting Duration**, **Awaiting Reason**, **Awaiting Manual Grant**, **Solved**, **Denied**, or **Canceled**. Click it to open the grant.
- **Type**: **Access** for a request for access, **Revocation** for a request to remove it
- **Application**: the application, linked to its page
- **Access rule**: the access rule that matched the request, linked to the rule
- **Target user**: the person who receives (or loses) the access
- **Ticket**: the ticket the grant came from, linked
- **Duration**: the length of access that was requested, for example "1 hour 30 minutes"
- **Expires**: the date a time-limited grant expires
- **Created**: the date of the request

The **View** menu sorts the table and shows the hidden **Requestor**, **Granted**, and **Revoked** columns.

*Product example: The Access Grants page: its filters, Export, and one row per grant with its status, application, target user and expiry.*

Approvers decide with the **Approve** and **Deny** buttons in the Slack approval message. See [Access rules](https://www.tryrisotto.com/docs/dashboard/applications/access-rules#approvals). An Org Admin can also approve a pending request from this page (see [Approve a request as an Org Admin](#approve-a-request-as-an-org-admin)). This page has no **Deny** button. To stop a pending request, resolve or close its ticket, or the requester asks Risotto in the ticket thread to cancel it. Risotto then cancels the open access requests on the ticket. A request handed to Opal or Okta Identity Governance stays open: the requester withdraws it in that system. See [Ticket lifecycle](https://www.tryrisotto.com/docs/concepts/ticket-lifecycle#access-approvals).

### Pending approvals

Click the **Awaiting approval** tab above the filters to see the requests that wait for an approver. The tab shows how many requests it holds under your other filters. It also includes requests that wait for approval in Opal or Okta Identity Governance.

- The oldest request is first. Choose another sort to change the order.
- The **Reason** column shows the reason the requester gave. It takes the place of the **Expires** column. Hover over a reason to see all of it.
- Click **All** to go back to every grant. In **All**, the **Reason** column is hidden: turn it on in the **View** menu.

### Approve a request as an Org Admin

An Org Admin can approve a request that waits for Risotto approvers, without waiting for them. Managers cannot do this.

1. **Open the request**

   Click the request in the **Awaiting approval** tab.

2. **Approve it**

   Click **Approve**, then click **Approve request** in the **Approve this
   request?** dialog.

Risotto then does these things:

- It grants the access, the same as when the last approver approves.
- It removes the buttons from the approval messages that are still open. Approvers who did not answer can no longer approve or deny.
- It adds an internal note to the linked ticket and tells the requester in the ticket thread.
- The grant's **Lifecycle** shows "Approval bypassed by" and your name.

The **Approve** button does not show for requests that wait in Opal or Okta Identity Governance. If the approval chain does not allow self-approval, you cannot approve your own request.

### Filter grants

Narrow the list with the filters above the table:

- **Search grants**: matches the requested software, the requestor, the target user, and the access rule's name
- **Status**, **Type**, **Target user**, and **Application**
- **Expiration**: **Expiring** (granted, with an expiration still ahead), **Expired** (granted, and the expiration has passed), or **Permanent** (granted, with no expiration). This filter shows only access that was granted, never pending, denied, or revocation requests.
- **Created Date** and **Expires**: a date or a date range

Click **Clear filters** to reset them.

### Export grants

Click **Export** and select **Download current view as CSV** for the columns the table shows, or **Download all fields as CSV** for every column. Both files include only the grants that match the filters. The current view includes the **Reason** column when you turned it on.

## A grant's page

Click a grant's **Status** to open its page. The top shows the access rule's name, whether the grant is an **Access grant** or an **Access revocation**, and the request's status. Below them, a badge shows where the access stands:

- **Active**, with when it expires, or **Permanent access** or **No expiration**
- **Expired**, **Revoked**, **Denied**, or **Canceled**, with when
- the request's status while the request is still in progress

**Details** shows the **Target user**, the **Requestor**, the **Access rule**, the **Application**, the **Ticket**, the **Duration**, and the requestor's **Reason**.

**Lifecycle** lists what happened, in order: **Requested**, each approval (**Approved by**, **Denied by**, or **Awaiting approval** from the approver), **Manually granted** with the grantor's email, **Access granted**, **Converted to permanent access**, **Access revoked**, and when the access **Expires** or **Expired**. When no one had to approve, it says "Granted automatically — no approval was required."

When Okta Identity Governance or Opal handles the request, the page says so, and **Open in portal** opens the request in that provider.

## Time-limited grants

When an access rule grants access for a limited time, the expiration is tracked here:

- Before a grant expires, Risotto reminds the person who has it, and can offer a one-click extension. See [Renewing time-limited access](https://www.tryrisotto.com/docs/dashboard/applications/access-rules#renewing-time-limited-access).
- When the expiration passes, Risotto revokes the access automatically. If a license server (Zoom or Tableau) refuses to remove the license, Risotto alerts your org admins to remove it by hand. See [License servers](https://www.tryrisotto.com/docs/dashboard/applications/license-servers#troubleshooting).

### Expire a grant early

Cut access before its scheduled date, for example when someone changes teams or a review flags something.

1. **Open the grant**

   On **Access Grants**, click the grant's **Status**. Use the **Expiration** filter on **Expiring** to find grants that are still active.

2. **Click Expire access now**

   At the top of the grant's page, click **Expire access now**.

   *Product example: A Figma Editor access grant's page: Active, with Expire access now, its details and its lifecycle.*

3. **Confirm**

   In the **Expire access now?** dialog, click **Expire access now**. Risotto removes the access, shows "Access expired", notifies the person who had the access, and adds an internal note to the linked ticket. You cannot undo this.

   *Product example: The Expire access now? confirmation over an access grant's page.*

**Expire access now** shows only on an active, time-limited grant, and only to an Agent or Supervisor in the department of the grant's ticket. The Org Admin role alone is not enough, and approving the original request does not give this permission. It also shows on a grant whose access Risotto could not remove, because a script tool failed or because your identity provider did not remove the user from the group: expiring it now runs the removal again. Such a grant stays **Granted**, and the automatic expiry skips it until you retry. Your org admins get a notice, for example "Failed to remove access to '*rule*' for *email*. The grant stays active." This includes a time-limited request that ended before the access was granted. For that request, Risotto does not notify the person, because they never had the access. You cannot expire a grant that Okta Identity Governance or Opal handles from Risotto.

### Make a grant permanent

Cancel a grant's expiration to keep the access with no end date.

1. **Open the grant**

   On **Access Grants**, click the grant's **Status**.

2. **Click Convert to permanent access**

   At the top of the grant's page, click **Convert to permanent access**.

3. **Confirm**

   The dialog shows when the access is scheduled to expire. Click **Convert to permanent access**, or **Keep expiration** to leave it. Risotto shows "Expiration canceled — access is now permanent".

   *Product example: The Convert to permanent access? confirmation over an access grant's page.*

The grant's **Lifecycle** shows **Converted to permanent access** with who converted it, and Risotto adds an internal note to the linked ticket. Risotto also clears the expiration of the person's other granted requests for the same access rule or group, so an older grant cannot remove the access when it expires. You can still revoke the access later.

**Convert to permanent access** shows only to Org Admins and Org Managers, and only on an active grant that has an expiration. It does not show on grants that Okta Identity Governance or Opal handles.

## Common uses

- **Compliance audits**: answer "who currently has access to X" or "show me every grant for this application" without digging through individual tickets
- **Cost audits**: for seat-based tools, cross-reference active grants against your bill to spot unused or forgotten access
- **Offboarding checks**: confirm a departing employee's grants have actually expired or been revoked, not just requested

## Notes on manual grants

For applications fulfilled by a manual grantor (a human doing the provisioning), the grant reflects what the grantor confirms: they mark the account created when provisioning, and mark it deprovisioned when revoking. If a manual grant looks stuck on **Awaiting Manual Grant** or **Awaiting Manual Deprovision**, check whether the grantor confirmed the action in Slack. The grant can't advance without it. Once the grantor confirms, Risotto tells the requestor in the ticket thread and resolves the ticket. If the grantor confirms after the request ended, the grant still shows here, and its time limit starts when the grantor confirmed. A confirm on a denied request records no grant. See [Manual grantors](https://www.tryrisotto.com/docs/dashboard/applications/access-rules#manual-grantors).

## Related

- [Access rules](https://www.tryrisotto.com/docs/dashboard/applications/access-rules): configure how access requests get fulfilled
- [License servers](https://www.tryrisotto.com/docs/dashboard/applications/license-servers): grant access by provisioning a license directly
- [Applications](https://www.tryrisotto.com/docs/dashboard/applications): the catalog access rules attach to

Source: https://www.tryrisotto.com/docs/dashboard/applications/access-grants
