Audit Logs

Audit Logs

An audit log is a chronological record of significant actions taken across a workspace — who did what, to which resource, and when. Where a defect or a launch tells you about your product's quality, an audit log tells you about your workspace's own activity: configuration changes, membership changes, and administrative actions.

Why Audit Logs Matter

Audit logs exist for three main reasons:

• Compliance — many regulated industries require a record of who changed what and when, independent of any single team member's memory or Slack history.
• Security investigations — if something unexpected changes (a permission, an integration, a deleted resource), the audit log is the source of truth for tracing it back to an actor and a timestamp.
• Workspace history — for any team, understanding how settings or membership evolved over months is otherwise easy to lose track of.

What Gets Logged

Each entry records an actor (the user, or system for automated operations), the action taken (created, updated, deleted, etc.), the resource type and resource affected, and a timestamp. Entries can be filtered by actor type, action, resource type, and date range.

Audit logs are a workspace-level feature — they cover activity across every project in the workspace, not just one.

Availability

Audit logs require the Scale plan or above. Retention is 90 days on Scale and 1 year (with custom options) on Enterprise.

Related

• Audit Logs Reference — log entry fields, filtering, and retention detail
• Workspace Settings Reference — where audit logs live alongside other workspace-level configuration
• Users & Roles — the actors an audit log entry can reference