Documentation
Plan

53 of 187 pages

How To?

Audit Log

The audit log provides an append-only record of every significant action in your workspace — feature and story changes, user management, configuration updates, and security events (login, MFA, SSO, RBAC).

Screenshot: Audit Log page
Retention is configurable on Admin → Security (default 365 days) or inherited from organisation policy. Entries expire automatically via server-side TTL.

What is audited?

  • Features — create, update (field-level diffs for status, size, priority), delete
  • Stories / Work Items — create, update (status, points, assignment), delete
  • Sprints — create, start, complete, stories added/removed
  • Users — invite, role change, deactivate
  • Settings — access matrix changes, RBAC overrides, integration configuration
  • Security — login success/failure, logout, MFA challenge, SSO login, RBAC changes

Reading the audit log

1

Navigate to the Audit Log

Go to Admin → Audit Log. You must have the Admin role to view audit log entries.

2

Filter by entity or user

Use the filters to narrow down by entity type (Feature, Story, Sprint, User), by the user who made the change, or by date range. Each entry shows:

  • Timestamp (UTC)
  • User who performed the action
  • Entity type and ID
  • Action (create / update / delete)
  • Before and after values for key fields
3

Export for compliance or SIEM

Click Export CSV or Export JSON to download up to 10,000 filtered rows. For security operations tooling, use Export for SIEM — this writes a JSON bundle to encrypted storage and opens a presigned download URL valid for 24 hours.

Audit log and compliance

The audit log is append-only — entries cannot be modified or deleted by any user, including Admins. Organisation admins have a separate Organisation Audit Log for org-wide security events (SSO, SCIM, policy changes). See the guide for enterprise deployments.

All How To? documentation

Build v0.3.2 · deployed 2026-10-19T23:52:31Z