Read the audit log

The audit log is the place to start when the workspace behaves differently and nobody remembers changing it. Use it to establish what happened before you make another change.

Read the timelineCopy Anchor Link

Open Audit log to see recent actions, resource types, resolved names or short identifiers, timestamps, IP addresses, and details. An entry such as a policy update or an integration change gives you a starting point for checking the affected page.

Enlarge

Filter the action listCopy Anchor Link

Use the search field and the date, actor and category filters to narrow the list. Apply a filter before you copy a result into an incident note. A short list is easier to verify than a screenshot of the entire history.

Enlarge

Filter by resourceCopy Anchor Link

Choose Category when you know which area changed. For example, filter to conversations when an assignment looks wrong, or to integrations when an external connection stopped syncing.

Enlarge

Trace a change to its sourceCopy Anchor Link

Advanced filters include Source and Outcome. Source separates the dashboard, API, widget, automation and integration events. Outcome distinguishes successful, failed and blocked operations. You can also group system events to reduce repetition in a busy log.

Suppose a TopSoft4U conversation stops receiving its billing tag. Narrow the list to Automation and the relevant dates, then check the Rule that should have matched. If you find a failed API request, review its key under Account security.

Record the investigationCopy Anchor Link

Record the timestamp and the next page you checked. That small note saves time when the same issue returns later.