Skip to main content

Notifications

Hear about a credential expiring, a status changing, or a worker appearing on a ban register — without anyone opening the dashboard to look.

Who it's for: Compliance admins and the managers who act on flagged workers

Availability: Available

What you get​

  • Alerts when a credential is expiring, expired, revoked, or suspended, and when a worker turns up on a ban register
  • A personal alert level per user — all alerts, critical only, or exactly the types you pick
  • Delivery to a catch-all email address, a Microsoft Teams channel, or a Slack channel, in any combination
  • Optional emails to the workers themselves, and to their manager, as their credentials approach expiry
  • Lead times you set — including per-credential-type overrides, so a certificate that renews slowly warns earlier

Turn it on​

→ Set up notifications — set your alert level, choose who in the workforce is emailed, set the expiry lead times, and add a delivery channel.

How it works​

A change in a check's outcome is what raises an alert, so notifications sit on top of the ongoing re-checking loop rather than beside it. Expiring and Expiring Soon are lead times you choose, so a credential is flagged before it lapses rather than after. Personal preferences apply to your own account; the workforce, timing, and channel settings are admin-level and apply to the whole organisation.

→ Get notified when issues arise — where alerts sit in the end-to-end journey → Ban Checks — one of the things that raises an alert → Roles & access — what someone can see, and therefore be told about

For developers

For system-to-system updates, subscribe to the events themselves rather than parsing alert emails — deliveries are signed, retried, and replayable.

→ Webhooks & event delivery → REST API & webhooks

Good to know​

  • Emailing your workers directly contacts people who have no Oho login and can't opt out individually. Oho gives you a grace window — emails begin one hour after you save, so you can turn it back off before then.
  • The Delivery log tab on the same page shows recent notifications and where they went, which is where to look when someone says they didn't get an alert.
  • This page controls when alerts send and to whom. To change how the emails read and look, see Customise email templates.
  • Teams and Slack delivery uses that channel's Incoming Webhook URL; the setup page includes the steps for getting one.
  • When an alert means you need a detail only the worker has, send a fetch request.