Audit log

Administrator

Audit log in the Workspace area (Admin) — route /workspace/audit-log.

Updated August 12, 2026Reviewed July 30, 2026

Audit log lives in the Workspace area of the dashboard, under Admin.

At a glance#


Dashboard route	`/workspace/audit-log`
Area	Workspace (`workspace`)
Group	Admin
Platforms	Available for every app platform.

What it does#

The audit log records administrative actions taken in the workspace — who did what, and when — and can be exported. Entries expand to show their detail.

The recorded actions cover the changes that matter for security and for explaining a surprise:

Organisation and membership — org updated; member added, role changed, removed; invite created, revoked, accepted.
Apps and environments — app created; environment created; sessions purged.
SDK keys — created, revoked, rotated.
Integrations and webhooks — integration connected and disconnected; webhook created, deleted, secret rotated, and auto-disabled.
Data governance — retention updated, data purged, redaction updated, export requested, export downloaded.

When to use it#

Three situations, and it earns its place in all three.

"Why did the data change?" A retention update or an environment purge explains a discontinuity that looks like an instrumentation failure. This is the first place to look, before you go debugging the SDK.

"Who revoked that key?" SDK key lifecycle is recorded, which turns a production incident into a lookup.

Access review. Membership and role changes over time, in one list.

Workflow#

Filter by action before scanning
The log is chronological across every category. Filtering to the action type you care about is much faster than reading.
Expand the entry
The summary line names the action; the detail carries what actually changed.
Export for anything you need to keep
Retention applies here as it does elsewhere. If a record matters for compliance, export it rather than relying on it being available later.

Permissions and prerequisites#

Requires ADMIN or OWNER. An audit log readable by everyone it audits is not an audit log.

Limits and edge cases#

Administrative actions only. This is not a record of who viewed which dashboard page, and it does not log data reads.
webhook.auto_disabled has no actor. The system disabled the webhook after repeated failures; nobody did it.
Entries are append-only and cannot be edited or removed from the dashboard, which is the property that makes the log worth having.
Subject to retention. Export what you need to keep.

Troubleshooting#

An action I know happened is not listed. Check the action list above — activity outside those categories is not audited. Also check the date range.

A purge appears that nobody remembers. Expand it for the actor and the environment. Scheduled retention purges are recorded as retention.purged rather than as a member action.

Where the data comes from#

Served by

Admin