How can we help?

App Catalog - Customizing the Request Form

Merav Doron
Merav Doron
  • Updated

Overview

The request form is what employees fill in when they request access to an app: in the App Catalog, through the Slack or Teams agent, or when requesting on behalf of someone else. You decide which questions it asks. The answers go to approvers and can drive your provisioning workflows.

Open the request form

Go to App Catalog → App catalog settings → Request form.

CleanShot 2026-11-18 at 15.27.30@2x.png

Add and edit questions

  1. Click Add question.
  2. Enter the question as employees will see it.
  3. Choose an Answer type:
    • Short text (up to 255 characters)
    • Paragraph (up to 1,000 characters)
    • Single choice or Multiple choice, with options you define
    • Yes / No
    • Date
  4. Select Required if employees must answer before submitting.
  5. To add a line of guidance under the question, open the question's Actions menu (⋮) and turn on Helper text.
  6. Drag questions to reorder them.
  7. Click Save / Use Discard changes to undo unsaved edits.

A form can have up to 50 questions.

Conditional questions

You can show a question only after a certain answer to an earlier question. For example, show "Which access level do you need?" only when "Have you completed security training?" is Yes.

  1. In the question's Actions menu (⋮), select Conditional.
  2. Under Shown when, pick the earlier question and set the condition: is a specific answer, or is answered (any answer).
CleanShot 2026-11-18 at 15.30.50@2x.png

 

The live preview shows them only once their condition is met. The first question on the form can't be conditional.

Access duration

If temporary access is enabled, the form includes an Access duration question. Its options come from App Catalog settings → Access duration, so change them there. See App Catalog - Timed Access Request.

 

Live preview

The panel on the right shows the form exactly as employees will see it. Conditional questions appear once their condition is met.

Where the answers are used

  • Approval flows automaticly see every answer in the approval request, by email, Slack or Teams.
  • Workflows can use the answers as dynamic values and in if/else conditions or as a personalization token. For example, you can route by the license someone selected.
  • The Slack and Teams agents ask the same questions in the conversation.
  • The API and MCP can read the form and submit answers.

Use the answers in workflows/approval flows (personalization tokens)

Every question on the request form becomes a personalization token in your App Catalog workflows. Add these tokens to any text field in a workflow action, such as a Slack message, an email or a ticket description, so whoever handles the request gets the requester's answers without having to ask.

The tokens are listed with the other trigger tokens, under Trigger.Form:

Token What it adds
Trigger.Form.Answers.[question] The answer to one question. Each question gets its own token, named after the question, for example Trigger.Form.Answers.Reason or Trigger.Form.Answers.License-type.
Trigger.Form.All-answers Every question and its answer, in one block. Useful when you want the full request in a ticket or message.
Trigger.Form.Answers.Access-duration The access duration the requester chose, for example "7 days".
Trigger.Form.Answers.Access-duration-days
Trigger.Form.Answers.Access-duration-hours
The same duration as a number of days or hours, for actions that need a number.

Example: a provisioning workflow that opens a ticket for IT could use this description:

New access request from the App Catalog.
License type: {Trigger.Form.Answers.License-type}
Reason: {Trigger.Form.Answers.Reason}

You can also use the answers in If/Else conditions to route a request differently depending on what the requester answered, for example to send requests for an admin license to an extra approver.

Before you delete a question

Each question shows where it's used, for example "Used in 6 flows". If a question is used in a workflow or a condition, Torii warns you before you delete it, so a workflow doesn't break without anyone noticing.

FAQ

What happened to "Reason" and "Ask for license type"?
They're now questions on the request form. Existing workflows that used them were updated to use the new form answers.

Related articles

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request