Audit log

The audit log records who did what in your workspace: the person or agent that acted, the action, such as a task update, what it was done to, such as a particular task, and extra context about the change. When a platform operator acts on behalf of a person, the row also names that operator. Only workspace owners and administrators can read the log. Automations and webhooks react to the same events, and you can export them as CSV or JSON Lines.

• Filter by one or more actions chosen from a list, by actor, and by time range: the last 24 hours by default, a preset, or a custom start and end
• Filters are kept in the address of the page, so a reload or a shared link keeps them
• Export the filtered events as CSV or JSON Lines from the buttons in the page header
• Events also trigger automations and webhook deliveries

• Audit events are append-only; they are never mutated or deleted.
• Atlas replaces email addresses, links, tokens and long codes in the context with redacted markers and shortens long text, but it cannot recognise every kind of personal data, so keep personal data out of the context.
• Under super-admin impersonation, actingAs is stamped server-side and cannot be spoofed by the client.

1. 1Open Settings, then Audit log.
2. 2Choose one or more actions, enter an actor, or pick a time range.
3. 3Export the filtered list as CSV or JSON Lines from the page header.

Can an audit entry be edited or removed?

No. The events listed here are append-only: no screen or endpoint edits or deletes one. The audit retention window an administrator can set removes entries only from the separate sealed audit log, never from this list.

Can I tell when somebody acted through impersonation?

Yes. The acting identity is stamped on the row by the server and cannot be set by the client, so an action taken while impersonating carries both the account it was taken as and the operator who took it.

Is it safe to put anything I like in the context field?

No. The context keeps the metadata you give it. Atlas redacts email addresses, links, tokens and long codes and shortens long text, but it cannot recognise every kind of personal data, so keep personal data out of it and record identifiers instead.