Introduction
Torii displays a centralized filterable and exportable audit log, containing a complete list of actions that were taken in Torii.
The log includes:
- Workflow actions - actions executed in the context of specific workflow run
- App catalog policies actions - actions executed in the context of specific app request policy run
- Recommendations applied - actions executed when applying license recommendations
- Offboarding actions - actions executed when offboarding an employee
- Manual actions taken from application users tab
- Manual actions taken from inactive licenses list
The actions log allows easy troubleshooting and answering auditing questions.
Questions that you can answer by looking at the actions log:
- Did someone remove a Salesforce license from an employee?
- Who requested access to Asana during last 6 months?
- Which automations usually result in errors and why?
- Which approval requests have not been answered?
Action log columns and filters
| Column name | This column shows | Is filterable | Example value |
| Triggered at | When an action was triggered | Yes |
June 19, 2024
3:32 AM (UTC)
|
| Action | Action details. This column is also shown on the Workflow actions executions page. |
Yes. 2 filters are available: Action type - the name of the specific action User from action - the user on whom the action was applied |
Revoke all JetBrains licenses for user Mary Rose in JetBrain1 account |
| Status | If an action was completed successfully, is in progress or erred | Yes | In progress |
| App name | App related to the action | Yes | Slack |
| Action trigger |
The context in which an action was executed:
|
Yes |
|
| Workflow / policy name | The name of workflow or policy in which an action was executed | Yes | Master onboarding |
| Workflow/ policy trigger details | Details about an entity that triggered workflow or policy (user, app, contract or license). This column is also shown on the Workflow runs (Triggered) page. |
Yes. 4 filters are available:
|
|
| Manually triggered by | User who triggered actions manually. The column will remain empty if an action was triggered automatically via workflow or app request policy. | Yes | User pic of a user |
| Workflow / policy execution | Link that takes to the specific execution page | No | 12354 |
| Completed at | When an action was completed | Yes |
June 20, 2024
3:32 AM (UTC)
|
| Details | Action response details, including error details | No |
The specified channel name already exists. |
How to find answers in the log
Let's see how we can apply filters to answer questions listed at the beginning of the article.
1. Did someone remove a Salesforce license from an employee (e.g. Mary Rose)?
Filter the log by:
- Action type is Remove Salesforce license
- User from action is Mary Rose.
2. Who requested access to Asana during last 6 months?
Filter the log by:
- Action trigger is App request policy
- App from action is Asana
- Triggered at 120 days from now
3. Which automations usually result in errors and why?
Filter the log by:
- Status is Error
Now you can export the log to CSV and perform advanced analysis, grouping the actions by Action type.
4. Which approval requests have not been answered?
Filter the log by:
- Action type is Request approval
- Status is In progress
FAQ
Q: What is the timeframe for actions displayed in the log?
A: We present all actions, from the moment an organization was created in Torii.
Q: Does the log include updates made as a result of an integration sync? For example, if a user was removed from an app because they did not return in the last sync, will that be reflected?
A: No. We only expose actions that happened in Torii, as a result of Torii automation or Torii user manual action.