What is recorded
Every mutating administrative action. An entry carries who acted, when, what resource, what action, and — for updates — the before and after values.Actions
Create · Update · Delete · Approve · Reject · SignOut
Categories
Resources
Entries name what was touched — employee, role, punch, day record, leave request, regularization, overtime, swap, document, device, session, organization, roster, shift, salary component, payroll cycle, compliance filing, leave type, salary revision, payroll line override, report, integration, API key, webhook, device, terminal user mapping.Reading it
Facets
Facets
Counts per category, so you can jump straight to the payroll changes or the attendance overrides without scrolling.
Period filters
Period filters
Day, week and month windows, with counts.
Load more
Load more
Paginated rather than infinite — a long-serving employee’s trail is large.
Export
CSV of the current view.Where approvals appear
Approvals are audited unconditionally, on both outcomes — an approval and a rejection both produce an entry, and the entry is written whether or not the notification succeeded. So the audit trail is the authoritative record of a decision, not the notification.What the audit log is good for
Explaining a payslip
An attendance override or a compensation revision in the relevant month usually explains a surprising number, and names who made it.
Access review
Permission-category entries show when someone’s role changed and who changed it.
Dispute resolution
An approval entry records who decided, when, and what the request said.
Statutory inspection
Manual attendance entries carry the reason that was given at the time.
Limits
The audit view is per employee. There is no organization-wide audit browser — you look up a person, not a time window across everyone. If you need cross-employee analysis, export from several records or use the public API.There is also no retention policy or archival: entries accumulate indefinitely.