Setting Up Audit Logs and Reviewing Bot Actions in Console
How activity tracking works in Console
Console provides visibility into requests and executed actions through its request tracking and monitoring surfaces.
When a request is submitted, it is captured in Console and processed according to the configured workflow. Actions taken as part of that workflow are recorded and visible within the platform.
Activity tracking supports operational review and ongoing oversight of automated workflows.
Reviewing requests in Inbox and Requests
All submitted requests are visible within Console.
Teams can:
View pending requests
Review completed requests
See the status of a request
Identify who submitted the request
Confirm who approved the request
Inbox and Requests provide a centralized view of workflow activity, allowing teams to review what actions have been initiated and completed.
Monitoring bot-executed actions
When workflows trigger actions, those actions are processed through Console and associated with the originating request.
Teams can trace activity from submission through execution, reviewing the request that initiated the action, the approval steps that occurred, and the resulting change. This linkage supports accountability across automated workflows.
Using Insights for operational visibility
Insights provides visibility into activity trends and workflow performance.
From Insights, teams can:
Monitor request volume
Review activity over time
Identify patterns in workflow execution
You can also ask Insights questions in a single prompt to quickly surface operational metrics. Dashboards and views can be generated with a single click, enabling teams to analyze workflow activity without manual configuration.
Operational visibility helps teams understand how automation is being used across the organization.
Maintaining ongoing oversight
Regular review of request history and executed actions supports accountability and governance. Teams can periodically review completed requests, confirm approvals were followed, monitor sensitive workflow activity, and investigate unexpected changes.
By reviewing request history and action execution within Console, organizations maintain structured visibility into automated operations.
If a request can’t be automated, it is routed to a human for resolution. Console surfaces the source and context used to inform the response and allows teams to review the outcome. Teams can then decide whether similar requests should be automated going forward.
This review process mirrors the approval model used for bot-executed actions, providing visibility into how decisions are made while enabling controlled expansion of automation.