Security & governance

Audit trail · who did what and when

The audit trail records the organization's relevant actions, with the author, the action, the object affected and the exact moment. Entries are only ever appended: not even an administrator can change or delete an event once it is written.

When someone asks who deleted that deal, who changed that person's role or who exported the database on Friday night, the answer has to come from a record nobody can tamper with. That is what the audit trail is for.

Where to see it

Open Settings and click Audit.
The table shows When, User, Action and Record, newest first.
When the event points at a specific record, the Open link takes you straight to it.

What usually shows up

Created, Changed, Deleted and Merged records.
Attached file and Removed attachment.
Added user, Changed role and Changed user status.
Changed security, Sessions ended and Access blocked by IP.
Login.
Data export and data subject anonymization.
Configured AI, plus changes to roles and permissions.

The trail cannot be edited

The database refuses any attempt to change or delete a row of the trail, and that protection holds even for the database owner. There is no clear audit button, not in the product and not behind it. What went in, stays in.

Choosing what gets recorded

At the top of the screen, the Log configuration block lets you turn whole categories on and off. By default everything is enabled. Turning a category off reduces the number of entries and the storage consumed by that kind of action.

Access and permissions.
Records, which covers creating, editing, deleting and also the activities about them.
Data, which covers importing, exporting and anonymizing.
Settings and metadata.
Automations and rules.
Other actions.
Security, which is always recorded and cannot be turned off.

Example: A company with heavy import volume turns the Records category off to keep storage growth in check, and leaves Security, Access and permissions and Data on. From then on, bulk contact creation stops producing rows in the trail, but who exported the database and who changed a role still show up.

💡 Turning a category off applies from that moment forward and does not erase what was already written. On the other hand, it is not recovered later either: the period when the category was off will be missing those events forever. Think twice before turning off something your external auditor may ask for.

An honest limitation

Each event is written without holding up the main operation: if for some reason the write fails, the user's action still goes through instead of being canceled. In practice this is rare, but it means the trail is very strong evidence of what happened, and not a lock that prevents an action from occurring without a log.

Who can see it

Only people with permission to manage settings can open the trail. As with everything else in the system, isolation by organization applies here: one organization's trail never shows another organization's events.

To investigate with filters

Filters by user, action, object and date range, a summary by category and CSV export are all described in the advanced auditing article.

Open this article inside the system →