What it covers
Authorised administrators can filter workspace audit history by supported criteria and inspect the evidence behind configuration and business-record changes.
Customisation and integrations
Workspace audit log
Review accountable changes with the actor, action and time in view.
How it works
Find the change behind a question
The workspace audit log helps an authorised administrator answer a practical question: who changed something, what action was recorded and when did it happen? It provides filtered access to workspace audit evidence through Settings. An administrator can narrow the history with supported search and date criteria rather than treating the newest events as the entire story. Audit entries support accountability for business operations and configuration changes. They complement the lifecycle history on an individual record, which often contains the specific decision or transition needed to understand that record.
In practice
The log is available to authorised workspace administrators. Filtered events help identify the actor, action and time; the underlying record history supplies more context for the decision or business change.
When to use it
Useful situations
- Investigate when a shared workspace setting was changed.
- Identify the recorded actor and action behind a business-record update.
- Review a bounded period of history during an operational handover or internal review.
A working path
How the work moves
Define the question
Open the Audit log in Settings and decide which change you need to understand. Use a relevant record, action or time period to keep the review focused instead of reading unrelated events from the entire workspace.
Narrow the evidence
Apply supported filters and search criteria, then review the actor, action, entity and timestamp. Check the scope of the result before treating a filtered page as a complete account of every change made during that period.
Follow the record context
Use the underlying business record or configuration history to interpret the audit event. A change entry can establish that an action was recorded; the related lifecycle and decision evidence explain why it occurred and what the current state means.
Illustrative scenario
Reviewing a configuration change
An administrator notices that a team’s working default has changed. They filter the audit history to the relevant period, identify the recorded actor and setting action, then discuss the intended result with that person before making a correction.
Before you start
What to check
- Workspace audit access is an administrative capability, while individual record histories continue to follow their own visibility rules.
- Audit evidence does not by itself establish regulatory certification or explain every business reason behind a recorded action.
Is the workspace audit log available to every teammate?
No. It requires current owner or administrator authority, People and access visibility and the Business Audit History capability.
Does an audit event replace record history?
No. Use both where relevant: the audit identifies an action, while a record’s lifecycle history provides its operational context.
Get started
See your customer work in one place.
Start with the core CRM for free, then add the tools your team needs.