Audit log
Who changed what, when, and what it was before, across every module. Staff, automation rules, the AI layer, API keys and learners all write to the same log, and no one can edit it.
Entries today
412
61 by staff, 290 by rules and flows, 44 by API, 17 by AI
Sensitive changes, 7 days
9
Prices, roles, refunds, certificates, API keys
Changes outside office hours
3
1 by a person; open for review
Log kept since
6 Apr 2026
184,206 entries, integrity check passed today
| When | Who | Module | Record | Action | Before and after |
|---|
Retention
- Finance, orders, invoices, refunds
- 7 years
- Certificates and attendance
- 10 years
- Learner and CRM records
- 5 years
- Roles, sign-ins, API keys
- 2 years
- AI prompts and drafts
- 1 year
- Sync and delivery detail
- 90 days
These periods are working assumptions. Confirm them with the company's accountant and legal adviser before go-live; tax and data-protection rules decide the minimum and maximum.
After the period, entries are deleted except a one-line summary. When a learner asks for erasure, their name is replaced by a reference in the log; the fact of the change stays.
Entries by module, 7 days
Saved views
Insight. A price was changed on Thursday at 22:41, outside office hours, and changed back 9 minutes later. Both edits were by the same admin. Nothing was sold at the lower price.
How the log is protected
- Append-only: entries cannot be edited or deleted by any role.
- Each entry carries a hash of the one before it; a daily check proves nothing was removed.
- Reading the log needs the Audit permission in roles and permissions.
- Exports of the log are themselves logged.