Overview

The Requests tab provides a centralized view of all application access requests in your organization.

It allows admins to track, review, and manage requests across all applications from a single place.

What you can see in the Requests tab

In this page, you can view:

Requests:

• Pending requests awaiting approval
• Approved requests
• Rejected requests
• Past requests for historical tracking

Active temporary access:

• Access pending revocation
• Revoked access

This gives you full visibility into both current and past access activity.

Predefined views

To help you quickly focus on relevant requests, the Requests tab includes predefined views:

• Open requests – all currently pending requests
• Open for more than 1 week – requests that may require attention
• All requests – a complete history of requests

How to view Requests

Requests is a top-level item in the left navigation. It has two tabs:

• Access requests — all access requests and their status
• Active temporary access — currently active temporary access grants, with expiry and time remaining. Use Show revoked history to see grants that have already been revoked, and View request to open the originating request.

Managing requests

From the Requests tab, you can:

• Review request details
• Track request status
• Monitor activity across applications

Exploring a Single Request

While the Requests page gives you the full list, the request page shows everything about one specific access request in a single place — including its complete history from submission through provisioning or revocation.

Viewing a request

There are three ways to get there:

• Click anywhere on a request's row in the Requests table
• Click the eye icon at the end of the row
• Open the approval task related to the request and use the Access request link in the task details

The activity timeline

The left side of the page shows the full lifecycle of the request as a vertical timeline. Each stage appears as its own step, so you can see at a glance exactly where the request is and what has already happened:

• Request submitted — when the request was created
• Approval — one step per approval stage in the policy. Each approver is listed by name and links to their user profile, with an icon showing whether the step is waiting, pending on that person, or approved (including the date and time of the decision). Where a step allows any one of several people to approve, it appears as One of the following approvers. Requests handled by an automatic policy show a single Auto-approved step instead.
• Provisioning — whether provisioning is waiting, completed, or failed. When provisioning completes, the workflow that ran is shown.
• Access granted — when the provisioning workflow end successfully and user received access
• Active temporary access — for temporary access grants
• Temporary access revocation — whether revocation is pending, completed, or failed, along with the deprovisioning workflow that ran

Cancelled and declined requests show where in the process they stopped. Requests an admin manually marked as granted or revoked are also recorded in the timeline.

Troubleshooting a request that didn't complete

A request can stall in two different places, and each has its own place to look.

Waiting on a person. The request sits at an approval step. The Waiting on approver and Time waiting columns show who and how long. The Open For More Than 1 Week view surfaces these; each approval step is also a Torii approval task assigned to the approver.

Failed automation. The approval went through but the provisioning workflow errored — an integration permission issue, a missing license, a ticketing action that couldn't run.

If provisioning or a temporary access revocation fails, the timeline marks the step with a red icon and offers two options:

• View failure details — see the error returned by the app or workflow
• Mark as complete — record that the access was granted or revoked manually outside of Torii, so the request no longer shows as failed

Tip: Turn on Error alerts in App catalog settings so failures are pushed to you instead of waiting to be noticed. Temporary access that fails to revoke appears as Revocation failed on the Active temporary access tab.

Using request data

Request data can be used beyond day-to-day management:

• Export to CSV for further analysis or sharing
• Create reports to track trends and activity
• Use in dashboards for ongoing visibility and monitoring

How this fits into the process

• Users submit access requests through the Application Catalog
• Requests appear in the Requests tab
• Requests follow the configured approval flow (or auto approval)
• After approval, a provisioning workflow handles access