Audit trail
Roles control what can happen. The audit trail records what did happen — a durable log of actions across your company, kept for accountability and compliance.
What's recorded
Each entry captures the essentials of an action:
- Who did it — the actor
- Whether it was a person or the AI — every event is tagged human or AI, so the Associate's actions are always distinguishable from a teammate's
- What happened — the event and the entity it affected (a task, document, etc.)
- Where — the project and workspace
- When — the timestamp
- Supporting details for context
You can tell humans and AI apart
Because every entry is tagged by actor type, you can filter the log to just the AI's actions — a clear, reviewable record of everything the Associate has done on your behalf. That's a big part of trusting an AI that can act.
Tamper-evident by design
The audit trail is append-only and tamper-evident: each entry is cryptographically chained to the one before it. If a record were altered or removed, the chain would no longer line up — so the log can be trusted as an accurate history, which is exactly what compliance frameworks like SOC 2 expect.
Where to find it
Company owners can open Company Settings → Security & Governance → Audit trail to review activity across every workspace and project in the company. A project's Activity tab remains the place for day-to-day, project-specific history; links to the former project Audit tab open the company audit trail with that project filter applied.
Who can see it
The company audit trail is owner-only because it crosses workspace boundaries. Company admins, managers, members, and read-only roles cannot access it. Project Activity continues to follow the permissions of its project.
Filtering and export
Owners can filter the log by event, actor or actor type, entity, workspace, project, and date range. Loaded records can also be searched and inspected in full, verified against the integrity chain, or exported as CSV or JSON.
Next
Last updated: 2026-07-27