Investigate audit events, live access, and routing
Find relevant events and distinguish current access from historical activity.
Table of Contents
Who this is for: authorized administrators investigating workspace activity, record visibility, or approval routing.
Open Audit log in admin view. Use Events for historical activity, Live access for current access explanations, and Routing trail for a submission's routing and decisions.
Find historical events
- Open Events.
- Choose the relevant Event type, time range, and Target. Check the time zone displayed by the time filter.
- Decide whether to include audit-log views, then select Apply filters. Use Clear filters to reset the search.
- Review Event, Actor, Target, Details, and Time together. Narrow the time and target before assuming a similarly named event is the one you need.
- Open the relevant event where detail controls are available. Access to redacted values and raw event JSON requires separate permission.
The list may show a loaded count with more available. Do not treat the currently loaded rows as the full history. Read events and administrative views can themselves be recorded.

Inspect current access
- Open Live access.
- Use Search people and select the intended account, checking its email as well as its name.
- Inspect what the person can access now and the explanation for that access.
- Compare the result with role assignments, org-unit membership, capability grants, and applicable access rules.
Coverage limitation: the current inspector states that coverage is bounded to the record types the backend models today, which are records. The reverse question, who can access a particular record, is tracked separately. Do not interpret a current-access explanation as a complete historical permission report.
Investigate approval routing
- Open Routing trail.
- Enter the exact Submission reference and select View trail.
- Review how the submission was routed, who made decisions, and the displayed reasons.
- Compare it with the record's Review timeline and the relevant form configuration and version.
A routing trail, current workflow configuration, and current user permissions describe different things. Use the actual request history when investigating a past decision; do not infer its past route solely from today's form settings.

Use the right source for the question
| Question | Start here |
|---|---|
| Who changed configuration, and when? | Events, filtered by target and time |
| Why can this person access a record now? | Live access, then roles and policies |
| Why did this request reach a particular reviewer? | Routing trail and the record's Review timeline |
| Was an outbound email sent? | Email → Delivery records |
| Was a reporting extract delivered? | The extract delivery log, not the internal application audit trail |
Escalate an investigation
Provide the record reference or configuration target, the relevant time and time zone, the action attempted, and the specific event or access explanation. Use your approved support channel and include only information necessary to investigate.
Check access for a person and record
For a specific access question, open System → Check access. Choose the Person, enter the exact Record reference, and use As of when investigating a particular date. Select Check access and read the returned explanation. This is separate from Audit log → Live access; do not substitute a current-access result for an as-of investigation.
Review related configuration under Record access, Deny rules, and role assignments. See Manage roles, capabilities, and access policies.
