How can we help?

App Catalog Settings

Merav Doron
Merav Doron
  • Updated

Overview

App Catalog Settings control how the catalog looks to employees, what they can request, and how they are notified. Open them from App CatalogApp catalog settings.

CleanShot 2026-08-23 at 19.11.18.png

Two controls sit outside this page:

  • Enable for all employees — the toggle at the top of the App Catalog page. Turn it on when the catalog is ready to publish.
  • Which apps appear in the catalog — the Apps visible in catalog filter at the top of the Access request policies tab. (This moved out of Settings; it is no longer a "Select applications" section.)

The settings page has eight sections.

CleanShot 2026-08-23 at 19.08.25.png

 


Select logo

Add your company logo to the catalog. Recommended size: 1320 x 300 px.


Select application fields

Choose which fields employees see in the app's side panel, and drag to reorder them. Both Torii fields (description, owner, tags, users) and your custom application fields are available.


Request access to an application

Controls the Request access button employees see on an app.

Setting What it does
Enable request access button Shows or hides the button in the catalog
Button name The label employees see. Default: Request access
Button action What the button does — see below
Ask for license type Asks the requester which license or seat type they need, so approvers and provisioning workflows know what to grant
View and edit policies Jumps to the Access request policies tab

 

Button action

Set this to Run policy. It is the recommended action and the only one that runs the app's access request policy — meaning eligibility groups, approval flows, provisioning automation, temporary access, the Requests page and reporting all apply.

Two legacy actions remain available for organizations that configured them before access request policies existed:

  • Compose mail — opens the employee's email client with a pre-filled message to the app owner. Sending it is up to the employee, and Torii does not record it.
  • Open link — redirects the employee to an external portal, such as a Jira Service Desk form.

Both bypass Torii: no approval flow, no provisioning automation, no temporary access, and no request history to audit later.

Note: Compose mail is not the same as a policy that emails the app owner. With Compose mail, the employee has to send the email themselves and nothing is tracked. With Run policy, Torii submits the request, runs approval and provisioning automatically, and records it on the Requests page.

To configure what actually happens per application, see App Catalog - Configuring Access Request Policies.


Access duration

Sets the access types and durations employees can choose: Permanent access, Temporary access, or both, plus the Allowed durations list (3 hours, 1 day, 7 days and 30 days out of the box) and whether employees may request a duration not in this list.

These are the global defaults. They apply to every access request policy set to Use default; a policy set to Custom options overrides them.

CleanShot 2026-08-23 at 19.16.39.png

 

For the full temporary access lifecycle and deprovisioning, see App Catalog - Timed Access Request.


Request new application

Controls the button employees use to ask for an app the organization doesn't have yet, and the policy that handles those requests. See Application Catalog - How to automate new application requests.


Notifications

Choose how users are notified about new tasks — email, Slack, Microsoft Teams — and turn on Notify requesters of access request progress so requesters are updated automatically as their request moves through approval and provisioning.

Note: These settings are shared with Tasks notifications; changes here apply there too.


Error alerts

Alerts admins when something in the request flow fails — for example a provisioning workflow action that errors, or a temporary access revocation that doesn't complete. Keep this on; it is how failures reach you without someone watching the Requests page.


Slack agent

Shows whether the Slack agent is connected, and lets you install it. Once connected, employees can discover apps, request access and check status conversationally in Slack. See Requesting App Access via Slack (Slack Agent) and Requesting App Access via Microsoft Teams (Teams Agent).


Publishing the catalog

When the settings are ready, go back to the App Catalog page and turn on Enable for all employees. Share the Catalog link shown at the top of the page.


FAQ

Where did "Select applications" go? 

App visibility is now the Apps visible in catalog filter at the top of the Access request policies tab.

Can employees still request Closed or Hidden apps? 

Closed apps can be requested. Hidden apps show a Request blocked label.


Appendix (legacy) – Making "Compose mail" open the email client

Only relevant when Button action is set to Compose mail. The catalog uses a mailto: link, so behavior depends on the browser. Chrome allows these by default, but the setting can be turned off.

  1. Go to chrome://settings/handlers and make sure Allow sites to ask to become default handlers is on.
  2. Open Gmail, click the handlers icon in the address bar, and choose Allow.
  3. Return to chrome://settings/handlers and confirm mail.google.com is listed.

Related articles

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request