The job of this console
Find an event, open the timeline, and export when an auditor asks. Filter by actor, record, and window. This is investigation, not a place to undo a change.
Admin · Compliance
Audit & Compliance
Organization-wide audit event register and timeline — who did what, when, on which record.
Scroll to Flowcharts. Scenario: Review security audit events.
Who did what, when
The org-wide register of meaningful actions
Audit & compliance is the organization-wide event register and timeline — who did what, when, on which record — across admin, people, and delivery activity the product already records.
Admin → Audit & compliance
Route
/admin/audit
Org flag auditEnabled
HR Admin · Org Admin
Seat at the table
Administrators and compliance operators. Employees do not get an org-wide audit. Sensitive fields stay masked according to persona policy.
The working rhythm
Set a window, filter, open a row, follow the record link into the owning console if you need to correct data there. Use compliance export when the ask is a pack, not a single event.
Moments that bring you here
Someone changed a flag and menus vanished. A leave balance looks rewritten. An auditor wants last quarter’s admin actions. After a suspected privilege change.
ⓘ
Masked summaries for sensitive fields
Salary, bank, tax, and similar values are not stored raw in audit snippets when persona masking applies. Follow the security console for the masking policy itself.
Flowcharts
1 — Investigate an event spike
Filter the register, switch to timeline, then export CSV if needed.
flowchart TD
A[Open Audit] --> B[Scan KPI / volume]
B --> C[Search actor or entity]
C --> D[Register or timeline]
D --> E[Open event]
E --> F[Export CSV if required]
- 1Open AuditAdmin → Audit & compliance.
- 2Search firstActor, action, entity, or headline.
- 3Switch viewRegister for scanning, timeline for day grouping.
- 4ExportCSV is for evidence — still masked where policy requires.
Overview
This console is the admin register over the unified audit stream. Entity screens (project, profile, leave) show the same events in context — see the HRMS Unified Audit Trail guide.
How to use
1. Writes are best-effort
Audit never blocks a save or approval.
2. No legacy backfill
History starts when audit writes were enabled.
3. Delegate vs actor
Delegation actions record both parties.