Offboard a worker

Someone has left. What you do next depends on what you want to stop — the checking, or the record — and Oho keeps those two things separate on purpose.

You want to…	Do this	Reversible
Stop re-checking them, keep the record where you can see it	Set them Inactive	Yes, by you
Remove them from lists, searches and dashboards	Delete the worker	Yes, by Oho support
Record that their employment ended	Let the HR feed do it	n/a

The common case is the first one. Reach for deletion only when you genuinely don't want the person in the workspace any more.

Employment status versus monitoring

A worker carries two different states, and confusing them is the usual source of "why is this person still being checked?".

Employment status — Active, On Leave, Terminated and so on — is a fact about their job. It comes from your HR system through a connector, or from a spreadsheet import. It describes the employment. On its own, it does not stop Oho checking them.

Monitoring — shown as Active or Inactive on the worker's profile — is an Oho control that decides whether Oho keeps re-checking their credentials. This is the one that stops the checking.

A worker whose HR record says Terminated but whose monitoring is still Active will go on being scanned against the registers. If your HR feed doesn't drive the monitoring toggle for you, ending someone's employment is two steps, not one.

Pause monitoring for one worker

On the worker's profile, switch them to Inactive. A banner appears on the profile so nobody mistakes the absence of recent results for a clean bill of health.

What that does:

• Scheduled verification skips them entirely — every one of their credentials, regardless of each credential's own settings.
• Their last-known results are frozen. Nothing is deleted; the credentials show what they showed when you paused.
• They drop out of compliance triage. Their credentials stop being counted in dashboards and attention queues.

Switching them back to Active resumes scanning. You don't have to re-enable anything credential-by-credential — the per-credential settings were never touched.

A paused worker is not a compliant worker

Pausing freezes the picture, it doesn't improve it. A credential that was already expired, superseded, or in a problem state when you paused it does not count as held — so a paused worker with a lapsed clearance still reports as non-compliant, rather than vanishing into an apparent all-clear. That's deliberate: pausing is for people you've stopped checking, not a way to make a problem disappear.

When to use it: leavers you want to keep visible, long leave, contractors between engagements, anyone you've stopped screening but still need on file.

Delete a worker

Deleting removes the worker from lists, searches and dashboards. It's behind the ⋮ menu on the worker's profile rather than beside the everyday controls, and it asks you to type delete to confirm.

Before you do, know what it means:

• The data is kept. Credentials, verification history and review items stay in the system for audit. Nothing is erased.
• The worker is hidden everywhere — every list and every search — until restored.
• Open fetch requests are cancelled. Their links stop working immediately, and restoring the worker does not bring them back. You'd need to send fresh ones.
• You can't restore them yourself. Restoring a deleted worker is an Oho support action — contact support@weareoho.com.

Add a reason when you delete. It's optional, and it's the thing that tells a reviewer in a year's time why the record went.

Deleting is not erasure

A deleted worker is hidden, not destroyed — that's what makes the audit trail worth having. If you need data genuinely removed, for example to satisfy a privacy request, that's a different process: see Data retention & privacy.

Offboarding over the API

DELETE /workers/{workerId} performs the same soft delete — the record and its history are preserved and the worker is excluded from list results. To see deleted workers, pass includeDeleted=true; a deleted worker carries "deleted": true.

To pause monitoring instead, patch the worker's monitoring flag rather than deleting:

curl -sS -X PATCH "$OHO_BASE/workers/$WORKER_ID" \
  -H "Authorization: Bearer $OHO_TOKEN" \
  -H "Content-Type: application/merge-patch+json" \
  -d '{"isActive": false}'

PUT resets monitoring

PUT /workers/{workerId} replaces the record wholesale — fields you leave out are cleared, and an omitted isActive reverts to the default, which is active. A PUT that forgets isActive will quietly put a paused worker back into scanning. Use PATCH unless you mean to replace everything.

See API Reference: Workers for the full shape.

What's next

• Data retention & privacy — what's kept, and for how long
• Audit trail — where the deletion and its reason are recorded
• Workers — the record itself
• How monitoring works — what you're pausing