Reading the audit log
What is recorded, what is deliberately not, and who can see it.
A record of sensitive admin actions on this team.
Only team admins can view it.
What is recorded
The actions that change who can reach what:
- API keys: created, revoked, renamed, scopes updated
- Contacts sync passwords: created, revoked
- Members: invited, added, role changed, removed
Each entry names the person, the action and when.
What is not recorded
Ordinary work. Editing a project, logging time, issuing an invoice: none of that is here.
That is a deliberate scope, not a gap. An audit log that records everything is a log nobody reads, and the questions this one answers are the security questions: who let that key exist, who changed that person's role, when did this account gain access.
For the history of a document, the document itself is the record. An issued invoice and its correction are a complete account of what happened to it.
Deleted people
Entries survive the person. Where an account no longer exists, the entry shows Deleted user rather than disappearing, because an audit log that erases itself when somebody leaves is not an audit log.
When it is empty
Admin actions on API keys and members will appear here.
An empty log on a new workspace is normal. It fills as soon as you invite somebody or create a key.