Every action in the system is recorded, who did what, to which document, and which fields changed. It comes in two layers: a quick per-document history anyone can see, and a full audit engine for administrators.
- What is captured on every action
- The per-document history at a glance
- The full audit engine for administrators
What is captured
As people work, the system records the trail: the entities they touch, the actions they take (a status change, an edit, a creation), and the field changes themselves, what a value was before and after. Nothing meaningful happens without leaving a record.
The per-document history
On a document, a button (top right) opens its own history: the recent activity on that record, who touched it and what they did, grouped sensibly so it reads as a story rather than a flood. It answers “what has happened to this document?” at a glance, for anyone working on it.
The full audit engine
Behind that everyday view sits a complete audit engine, available to a system administrator: a system-wide explorer that can query all activity, filtered by date, user, document type or keyword. Where the per-document history tells one document's story, the audit engine is the forensic view of the whole organisation, the source of truth for “who changed this, and when?”.
Why two layers
The split matches who needs what. Everyday users get the document's own history without ceremony; administrators get the deep, queryable audit when a question demands it. Same underlying record, two windows onto it.
Good practice
- Check the history when something looks off on a document; the answer is usually in its recent activity.
- Reach for the audit engine for anything system-wide or forensic.
Related
- Reference: Document Lifecycle
- Reference: Users and access (who can see the full audit)