Audit Trail
The Audit Trail is a company-wide, append-only record of configuration changes across your control room: who changed a customer, site, contact, billing plan, subscription, invoice, payment, Brain SOP, checklist template or monitoring setting — and exactly what changed, and when. It exists for compliance and dispute defence: when a setting is questioned later, the trail shows the full before/after and the person responsible.
It is distinct from the live, per-event action log used while handling alarms (that lives in CleverCommand) and from the curated activity feed on service jobs and billing. The Audit Trail captures full before/after snapshots of back-office configuration records.
Where to find it
There are two entry points:
- Per control room — open Audit trail in the More section of the CleverOps sidebar. You see the changes for the control room you are currently working in.
- Across companies (super admin) — open Super Admin in the sidebar, then the Audit Logs tab. With super-admin mode on, this shows the configuration changes for every control room belonging to the selected company. See Super Admin.
What is tracked
Each entry records the change type (created, updated or deleted), the record it applies to, the person who made the change (or system for automated changes), the control room, and a full before/after snapshot. Changes are captured for:
- Customers — account, billing and contact details
- Sites — site details, address and response instructions
- Site config / monitoring — monitoring package and mode, call list, routing and the rest of the per-site configuration
- Contacts / keyholders
- Billing plans, Subscriptions, Invoices and Payments
- Brain SOP and Checklist templates
- Site state / test mode — on-test and scheduled status changes
- Supervision & escalation — hub-offline and other staged-escalation ladders
To keep the trail meaningful, routine runtime changes are not recorded — for example arming and disarming a site, siren timers, and other live operational state. Machine-maintained fields (such as automatically learned note templates) are likewise skipped. The trail focuses on intentional configuration changes, not moment-to-moment activity.
Using the Audit Trail
The page shows the most recent changes for your scope, newest first, 50 at a time with Prev / Next beneath the table. Turning a page returns you to the top of the list. Use the controls along the top to narrow it:
- Search — free-text match on the entity, record id, action, actor or the names of the fields that changed. It runs across the whole trail, not just the page you are looking at, so a change from months ago is found by typing the record id.
- Entity — limit to one type (Customers, Sites, Invoices, and so on).
- Actor — limit to one person, or system for automated changes.
- From / To — limit to a date range.
Click any row to expand it:
- For an update, a table lists every changed field with its before and after value.
- For a created or deleted record, the expanded view shows the record snapshot.
Export to CSV
Click Export CSV to download the entries currently on screen as audit-log-YYYY-MM-DD.csv. The export includes the timestamp, control room, entity, record id, action, actor, the list of changed fields and the full before/after snapshots — suitable for archiving or sharing with an auditor. A toast confirms the download.
Set the entity and date filters before exporting: the export covers the page you are on, and those filters are what narrow the trail down to the change you are after.
A note on the count: while a search is running the footer shows "Showing 1–50" without a total. Counting every match of a free-text search means reading the whole trail — hundreds of thousands of rows on an established control room — so the page fetches your page and tells you whether there is another one, rather than making you wait for a number. Every other filter still shows an exact total.
Visibility and retention
- Scoping — you only see entries for control rooms you manage. A super admin (with super-admin mode on) sees every control room.
- Append-only — entries cannot be edited or deleted from the app; the trail is tamper-resistant by design.
- Retention — entries are kept for 24 months by default.
Audit entries can contain sensitive customer, billing and configuration details. Handle exported audit files according to your company's data-security policy.