Appearance
Audit trail and activity
Also known as
- audit log
- audit trail
- history
- change log
- who changed
- activity
- timeline
- traceability
- compliance
- SOX
Roari ERP records every create, change, status transition, approval decision, upload and deletion in an append-only audit log: who did it, when, a one-line summary and the fields that changed with their old and new values. Nobody can edit or delete an entry, and the log is never purged by data retention. You read it in three places: the Activity panel of each record, the Activity page for the whole organisation, and the compliance Audit explorer for auditors.
See the history of one record
- Open the record (a purchase order, a journal entry, an employee …).
- Look at the Activity panel in the right column. Each entry shows the person, what they did and how long ago.
- Select Show changes (n) under an entry to see each changed field as old value → new value. Select Hide changes to fold it again.
- If the record has more than eight entries, select Show all n at the bottom.
Entries made by a platform administrator working inside your organisation carry a platform tag.
Search the whole audit log
- Select Activity under Workspace in the spine (Activity).
- Narrow the log:
- Search summaries: words in the summary, for example a document number
PO-2026-00037. - Person: who made the change.
- Record type: Items, Purchase orders, Sales orders, Finance, Settings or Tenant.
- Date: a date range.
- Search summaries: words in the summary, for example a document number
- Select Show changes on an entry to see the field values.
- Use the pager at the bottom to go back in time (30 entries per page). Select Clear filters to start again.
The header shows how many entries match, and "Append-only audit log".
Investigate for an audit (compliance)
The Audit explorer (Compliance module) is the auditor's version of the same log, with more filters (Module, Record type, Action, Person, Platform admin, Record id, Period, Search inside changes, Changed field), a Field changes drawer per entry and, with
Permission:compliance.audit.export, Export CSV, Export Excel and Export PDF for yourauditors' working papers.
What is recorded
| Action | Example summary |
|---|---|
| Create | "Purchase order PO-2026-00037 created for Steelworks Supply Co. (58017.00 USD)" |
| Update | the changed fields, before and after |
| Transition | "Submitted for approval (Procurement: purchase orders ≥ 25000)", "Pay run PR-2026-0018 approved and posted (JE-2026-00833)" |
| Posting | "Posted JE-2026-00834 (3579.54 USD) from hr.pay_run_payment PR-2026-0018" |
| Approval decision | approved, rejected or reassigned, with the comment |
| Files | "Deleted file …" |
| Settings | approval rules, sequences ("Changed format to …"), custom fields, roles, users, API keys |
Where it appears
| Where | What you see | Needs |
|---|---|---|
| Activity panel on documents and master records in every module (see Documents and their states) | The history of that one record | Permission to view the record |
| Activity (Workspace) | The whole organisation's log | Permission: audit.view |
| Audit explorer | Full search and export for auditors | Permission: compliance.audit.view |
| Platform audit | Actions of platform administrators across organisations | Platform administrators only |
Differences by role
- Every user sees the Activity panel of the records they can open.
- Without Permission:
audit.viewthe Activity page shows "The audit log could not be loaded." In the demo company the account administrator and the Finance role have it.
Limits and things to know
- The log is append-only: entries cannot be changed or deleted, by anyone, and Data retention never removes them. That is what makes it usable as SOX or ISO evidence.
- Field names in Show changes are the system names in plain words ("Vendor id", "Line count"); ids are shown as ids.
- Reading records is not logged, only changes. Sign-ins are counted for the platform console.
- Background jobs and automations appear as System.
