The audit trail
The point of a compliance record isn't what it says today. It's being able to show what it said on the day you made a decision — and that you acted on what you knew at the time. Oho keeps that history for you, on every record, without anyone having to remember to write it down.
Where to find it
Every record with a history has an Activity Log tab: "All changes made to this record are captured below." It's there on workers, applicants and candidates; on credentials, verified credentials, qualifications, exemptions, declarations and bans; and on the source records the connectors bring in.
Entries are newest-first, and each one carries what changed, who changed it, and when.
What gets recorded
| Kind of change | Examples |
|---|---|
| Record lifecycle | Created, modified, deleted, reinstated |
| Credential changes | A credential added, removed, or its details edited |
| Verification activity | A check started, a check completed, the outcome it returned |
| Review decisions | A Review & Decide item resolved — and how |
| Attachments | A document uploaded or removed |
| Requests | A fetch or capture request sent and answered |
| Ownership and tags | Tags applied or removed, owners changed |
| Documentation | Notes and descriptions edited |
Actions Oho takes on its own are recorded the same way as ones a person takes — a scheduled re-check that changes a status leaves an entry, attributed to the system rather than to a user.
The part that matters for an audit
Three properties do the work:
It records the decision, not just the outcome. Where a person had to decide — confirming a ban match, overriding a downgrade, dismissing a flag — the log captures who decided, what they decided, and the note they left. This is why the Review & Decide queue nags you for a reason: the note is what an auditor reads.
It records what you knew and when. A credential's history shows each check Oho ran and what came back. If a clearance was valid in March and revoked in July, the record shows both, with dates — rather than only the current answer.
Removing a record doesn't remove its history. Deleting a worker hides them from lists and searches; the credentials, verification history and review items stay in the system. A leaver's file is still there when you need it.
How far back
History is kept for the life of the record. Oho does not age entries out of an Activity Log after a set period, and deleting a record doesn't truncate the history it accumulated.
The Activity Log is read in the app, per record. There's no "download this record's history" button, and no tenant-wide activity export. What you can export is the current compliance picture — see Download Report for a PDF or CSV snapshot. If you need bulk history for an audit, contact support@weareoho.com.
Getting change history programmatically
Some history is reachable over the API, though not as one "audit log" endpoint:
- Compliance check run history —
GET /compliance-checks/{id}/runsreturns per-worker evaluation outcomes over a time range. - Webhooks — subscribe to changes as they happen and keep your own record. If you need a durable audit stream in your own systems, this is the supported route.
/openapi/timeline/v1 is deprecated. It carries Deprecation and Sunset headers, stops working
after 30 September 2027, and answers 410 Gone from then on. Prefer webhooks for anything you
intend to keep running.
Related
- Review & Decide — where decisions are made and recorded
- How monitoring works — what produces the ongoing history
- Data retention & privacy — what's kept, where, and how it's removed
- Offboard a worker — what deleting does and doesn't remove
- Roles and access — who can see the history