A commonly used workflow action is to request approval to complete an action for an employee. Common use cases for this would be to start offboarding an employee, removing unused paid licenses or granting access to an application when a user requests it from the app catalog. To do this you would use the "Request approval" action within a workflow or app access policy.
This action will send an email or Slack notification requesting the user to approve or decline a question. Here is a how it would look like when sent via email:
Once the message recipient clicks "Approve" the action configured after "Request approved" will run. If the user clicks "Decline" the action configured after "Request declined" will run.
To configure the action, take the following steps:
- From the workflow, Click to add a new action, and select "Request Approval" from the Torii actions section.
- Pick the sending method - either email or Slack.
- Configure the message recipients and content. You can add any personalization token to the message content to make it clearer and personalized. For Slack only you can also customize the buttons text. For example, if your use case is to ask the user whether they approve removing their license you can set the buttons text to: "Reclaim License", "Keep License" so that the recipient has a clearer outlook of what clicking each button would actually do.
- Configure actions that to you wish will be triggered once the request is approved and once the request is declined.
You will be able to monitor the approval process via the Workflow audit log.
When an approval request is sent to multiple email recipients, Slack users or channels, how does Torii determine which button click takes precedence?
The first user who clicks will take precedence. In Slack all other messages will be updated to reflect that the request was already approved or declined. For email messages, if a user clicks a message that was already approved or declined by someone else, they would get a notification.