Understand the working context
History serves a different purpose from a customer note. A note explains the conversation or business context. An audit entry describes an action recorded by the application. Use both when investigating a change: the audit can identify the edit, while the note may explain why the colleague made it. Check the scope of the history available in each area rather than assuming that every external action or service event appears in the same place.
Put it into practice
- Identify the record or setting that changed.
- Review the relevant time and recorded actor.
- Compare the change with the customer or operational context.
- Use the supported permission controls when correcting access.
A practical example
A colleague notices that a customer’s contact details changed. They review the record history and the account notes to understand the update. For a user-access question, an administrator instead checks the workspace administration audit and the current permissions. These are related investigations but use different views.
In the current workspace
Atlas records supported record changes and workspace/platform administration actions. The application audit is not a promise of an independently archived compliance system or a complete log of every provider-side event.
Explore the productAtlas feature scope reviewed 17 October 2026. Plan availability and connection setup apply.