Organisation, team and billing
The audit log
Every change, who made it and when, including changes made through the API.
- Last updated
- 4 minute read
- Organisation
- Audit
The audit log answers the question that comes up after any change: who did that, and when. It is included on every plan.
What is recorded
Audit log
Every change made across your organisation, newest first.
- Sam Kerr template.updatedCompany standard2 minutes ago
- Microsoft 365 sync users.synced3 job titles updatedToday, 09:14
- Amelia Hart banner.createdAutumn open studio1 hour ago
- Priya Nair rule.createdDepartment: SalesYesterday
- Sam Kerr api_key.createdWebsite sync14 Sep
| Area | Examples |
|---|---|
| Signatures | Created, updated, made default, duplicated, deleted |
| People | Added, edited, imported, synced, deactivated, deleted |
| Rules and departments | Created, changed, deleted |
| Campaigns | Scheduled, edited, ended |
| Settings | Company defaults, disclaimer, logo changed |
| API keys | Created, rotated, revoked |
| Microsoft 365 | Connected, synced, disconnected |
Note: Every entry names the person who made the change. Changes made by an API key name the key instead of leaving the actor blank, so a key that edits signatures does not disappear into the log.
Using it
- Filter by action when you know roughly what changed.
- Read newest first: the thing you are looking for is usually near the top.
- Use it before and after a rollout, so you can tell what changed and what was always that way.
Tip: "Yesterday someone changed the Sales signature" is a five-second answer with the audit log and an hour of guessing without it. Check it before you start investigating a report.
How long it is kept
Audit entries are kept for the life of the organisation. API key usage records are pruned after 90 days, so a key's own activity history is shorter than the audit log itself.
Related articles
- Plans, trials and billingTwo plans priced per user, a 14-day trial of Pro, and what happens when a payment fails.
- Create and manage API keysOne key per system, the narrowest scopes that work, and a rotation plan you have actually written down.
- Team, roles and invitationsTwo roles, a short invitation flow, and how to make sure you are not the only owner.
Something here out of date, or a step that did not work? Tell us and we will fix the article. Every page is checked against the running product, so corrections are welcome.