Audit log

What the workspace audit log records, who can read it, what each row shows, and how to read older entries with the date range.

Written for
admin
Roles
owner
Requires
Owner
Feature
audit

The audit log is the workspace's record of administrative and structural actions: who changed a role, closed a period, deleted a ticket, or turned forced single sign-on off. It is append-only and belongs to the workspace, so it outlives the people who wrote it. Owners read it under Settings → Organization → Audit log.

Before you start

You need the Owner role. Admins cannot read the audit log.

What is recorded

Each entry is structural: the time, the acting account, whether the action was made on that person's behalf through a personal API token, the action, the type and id of the target, and for some actions a reason (for example the placeholder assigned when a person was pseudonymised, or the reason given for a redaction). Content is never recorded: no ticket text, comments, time notes, or attachments.

The page shows the 200 most recent entries, or the 200 most recent between the dates you choose, with four columns:

  • When: the time of the action.
  • Who: the acting account's name and address. An action made through a personal API token reads "{person} via API key {token}"; an agent account's key reads "API key {token}"; an action with no acting account (a scheduled job such as the daily mailbox retention pass) reads "System". A person who has since left the workspace shows their placeholder ("Former member 3").
  • What: a plain-language description of the action ("Closed a period", "Turned forced single sign-on on for a domain"), with the recorded action name underneath. An action without a description shows the name alone.
  • Details: the target, as its type and a label when SAQ can still resolve one (the ticket key, the project or client name, the person, the API key's name) or the first characters of its id otherwise (the whole id is in the tooltip), and the reason when one was recorded.

Above the table, From date and To date bound the entries fetched; both are inclusive whole days in your browser's time zone, and either can be left empty. When 200 entries are shown, the page says so and older entries in the same range are not listed: narrow the dates to reach them. Filter by action then narrows the fetched entries to those whose name or description contains the text; the count reads "{shown} of {total} entries". The full history stays in the workspace and is part of the workspace export.

Recorded action families

Family Examples
Members and invitations invitation.create, invitation.accept, invitation.revoke, membership.role.admin, membership.remove, membership.leave, membership.agent_create, membership.provision.jit, membership.provision.scim, identity.pseudonymise
API tokens api_token.create, api_token.agent_create, api_token.revoke
Authentication domain.add, domain.remove, domain.force_sso.on, domain.force_sso.off, sso.status.active, sso.delete, scim.token.create, scim.token.revoke, scim.user.create, scim.group.create
Workspace and workflow workspace.settings.update, workspace.feature.on, workspace.feature.off (the feature as the reason), membership.expected_week.set, workflow.settings.update, workflow.state.create, workflow.kind.create, workflow.priority.create
Clients and projects client.create, client.update, client.archive, client.user.add, client.user.remove, client.user.tickets_link, client.billing_recipient.add, contact.upsert, project.create, project.update, project.archive, project.member.remove, project.collaborators.set
Time and billing period.close, time.reattribute, billing_run.create, billing_run.void, rate.set, rate.delete, policy.set, bank.create, bank.update, bank.adjust, category.create, document.download, period.review.set, period.review.clear (the member as the reason)
Tickets ticket.delete, ticket.redact, and, for writes made through an API key, the ticket event (ticket.state, ticket.assignee, and so on) and comment.create
Mail mail.connect, mail.merge, mail.promote, mail.retry_processing, mail.retention.set, mail.retention.off, mail.retention.run (the daily pass, no acting account), mail.purge (period and counts as the reason), mail.secret_expiry.set (the date as the reason)
Organization organization.invoice.request, organization.company.set (the country and the terms version as the reason), subscription.cancel_at_period_end, workspace.export_started, workspace.exported, workspace.export_expired, workspace.delete_scheduled (reason inactive when the workspace was unused), workspace.inactivity_warning (first or final), workspace.restore_inactive

Day-to-day ticket edits made in the browser are not audit entries; they are in the ticket's history, which everyone who can see the ticket can read.

Delegated tokens

When someone acts through a personal API token, the entry is attributed to the token's owner and marked as made on their behalf, so an integration's work is traceable to the person who minted the key. An agent account is its own actor. Tickets and comments created this way are also marked with source api or mcp on the ticket. See API tokens and agent accounts.

Common problems

I cannot open the audit log. Only owners can. Anyone else sees "You do not have permission to do this."

An entry is missing. The page shows at most the 200 most recent entries in the chosen range. Set From date and To date around the day you are looking for; the full history is also in the workspace export.

The target shows an id instead of a name. The target no longer exists (a deleted ticket, a removed API key), or it is a kind of target SAQ does not label. For a deleted ticket the reason holds its key and title.

I need to know who changed a ticket field. Open the ticket's history; browser edits are recorded there, not in the audit log.