Skip to main content

Audit log

Every workspace has an audit trail of security-relevant actions: who did what, to what, and when.

What makes it evidence​

  • Append-only. There is no way to edit or delete an entry - not in the console, not in the API. The one exception is pseudonymisation when an account is deleted (below).
  • Written with the action. An entry is written in the same database transaction as the action it records, so an action cannot succeed without its entry, and an action that failed leaves none.
  • Exact order. Each entry is timestamped when it happens, so several actions in one request stay in the order they happened.

What is recorded​

AreaEntries
API keysCreated, revoked.
WebhooksCreated, secret rotated, disabled.
Single sign-on and SCIMEvery change to identity providers, domains (claimed, verified, failed verification, released) and SCIM tokens (created, revoked).
IntegrationsSelf-service registration, approval, rejection; and from the console, a connected system created, disabled, re-enabled, its signing secret rotated (never the secret itself), and an activity linked or unlinked.
Activities and sessionsA version published; a session created, started and ended; every presenter control in between (next, close voting, reveal, timer changes, pause, resume), each with who pressed it - a member, or an API key - and the question it applied to.
Projector wallsA wall PIN issued (by whom), and a wall opened with it. Never the PIN.
BrandingThe logo or the wall's theme changed (by whom), with the logo before and after, the accent colour, the background and the typeface.
ResultsResponses exported.
ModerationEach board post approved, rejected, highlighted or marked answered - by outcome, never by its text.
DataSession deleted (by a person, or by the retention sweep with no actor), participant erased (counts only), retention setting changed (from and to), workspace exported.
MembersMember removed when their account is deleted (recorded as done by the system).

What is never recorded​

An entry records what changed, never the content. A role name, a scope list, a count or a question id may appear; a participant's answer, contact details, a token or a post's text never does. A rejected post is recorded by outcome, so a slur that was removed from the board is not preserved verbatim in a table admins can export.

IP addresses are stored only as one-way hashes: enough to tell sources apart, not to identify them.

The actor is recorded by account and by the label they had at the time, so renaming an account does not rewrite history. An API key acting is named by its pk_ prefix, which identifies it without being usable as a credential.

Reading and exporting​

The audit log is read through the workspace API by an owner:

  • GET /api/v1/audit - newest first, filterable by action, actor_user_id, target_id, and a since / until time range, with limit (up to 500) and offset. The response includes the total and the list of possible actions.
  • GET /api/v1/audit/export - the trail as CSV (UTF-8 with a byte-order mark), filterable by action and time range. It is capped at 50,000 rows and says so in an X-Truncated header when it truncates, rather than quietly dropping rows.

The workspace export also includes the full audit log.

When an account is deleted​

Entries keep the actor's email address as it was. When someone deletes their account, every entry in which they appear - in every workspace, including ones they left long ago - is rewritten once:

  • their name and email become deleted user followed by eight characters, the same in every entry, so "the person who did this is the person who left" can still be answered;
  • any field holding exactly their email or user id becomes the same pseudonym;
  • the entry is marked as pseudonymised, and when.

The action, time and workspace stay, and nobody else's entries change. This is pseudonymisation, not anonymisation: the operator of the deployment could still work out who a pseudonym was from its own application logs. Workspace admins and exports cannot. Entries written about accounts deleted before this behaviour was introduced still carry the email address.

When a workspace is deleted​

The audit trail is the workspace's own data, so it is deleted with the workspace.