FAQ
What does the audit log capture?
Every sensitive action — sending invites, approving leave, signing documents, finalising pay runs, calibration overrides — is logged with who, what, when and from where.
2 min readLast updated 25 May 2026
What gets logged
Blankitt HR keeps an audit trail of every sensitive action. That includes:
| Area | Examples |
|---|---|
| Employees | Inviting someone, terminating someone |
| Leave | Requests, approvals, rejections, cancellations |
| Documents | Uploads, deletions |
| Signatures | Envelope created, sent, signed, voided |
| Performance | Cycle opened, feedback submitted |
| Calibration | Session opened, review locked, review overridden |
| Payroll | Pay run created, calculated, finalised, voided |
| Tax codes, student loans, salary sacrifice | Added, ended |
Each entry records:
- Who did it (the user)
- What they did (the action)
- What it affected (the employee, pay run, envelope, etc.)
- When (timestamp)
- IP address and browser used
What's NOT logged
- Reading pages (which would be too noisy to be useful)
- Actions taken by automated processes (scheduled tasks, queue consumers) — those go to a separate operational log
How to view it
A dedicated audit-log viewer is coming as part of an upcoming polish slice. For now, if you need to find out who did what:
- For recent activity, the relevant event timeline appears on the page (e.g. a signature envelope shows its full chronology on the detail page)
- For older or cross-area queries, email support@blankitt.com and we'll run the search for you
Why it matters
Common reasons you'll want to read the audit log:
- Investigating an unexpected change ("who changed Jane's salary last Thursday?")
- GDPR data-access requests — showing what was looked at and by whom
- Disciplinary process — confirming who edited an employee record
- HMRC enquiry — demonstrating who authorised a particular pay run
Retention
Audit events are kept indefinitely by default. If you need a shorter retention period for compliance reasons, contact support.