Module guide
Activity
Tenant-wide audit stream: who did what, when, and where.
Overview
Activity is the single feed of every state-changing event across the tenant: task created, project archived, PAT minted, webhook delivery failed, member invited. Every entry carries the actor (or PAT), the affected resource, and a structured diff where applicable.
Highlights
The capabilities worth knowing before you dive in.
- Filter by actor, resource type, or PAT prefix
- Deep links to the affected resource (task, project, or webhook)
- Webhook deliveries are first-class events; replay from the row
- Compliance-friendly: 90-day retention plus optional export
Important to know
Limits, permissions, and sharp edges to keep in mind.
- Audit rows are immutable. The original record persists even after the resource is deleted.
- PAT-attributed actions show the token prefix (atlas_pat_xxxx...) so you can trace stolen-key abuse.
- Filtering is server-side; the URL holds your filter state for shareable links.
How to use it
The primary workflow, start to finish.
- Open it with `g a` or click Activity in the sidebar.
- Use the filter bar at the top to scope by actor, resource, or PAT.
- Click any row to open the affected resource in a drawer.
FAQ
- How long are events retained?
- Default retention is 90 days. Self-hosted deployments can override AUDIT_RETENTION_DAYS; events are pruned by a nightly job.
- Can I subscribe to the stream?
- Yes. Every audit event is also published to the webhook bus. Subscribe at /settings/webhooks with a topic of `audit.*`.
- Can I tell which API token performed an action?
- Yes. An action attributed to a personal access token shows the token prefix, so a suspected stolen key can be traced to its activity without exposing the token itself.
Automate this module
Everything on this screen is scriptable. Drive it from the REST API, or let an AI agent run it through the MCP server.
Was this page helpful?