Skip to main content

Set Up Notifications

You shouldn't have to go looking for problems. Notifications tell you the moment a credential is expiring, a status changes, or a worker turns up on a ban register — so the right people can act without checking the Compliance Overview manually.

What you'll end up with

Alerts reaching the right people through the right channels — your own inbox, your team's Microsoft Teams or Slack channel, and optionally the workers themselves.

Step 1: Open Notifications​

In the left menu, click Settings, then under Manage click Notifications.

The Notifications page under Settings → Manage

Step 2: Set your personal alert level​

At the top, Your Notification Preferences controls which alerts you personally receive — these apply to your account only. Choose an Alert level:

  • All alerts — Expiring, Expiring Soon, Expired, Revoked, and Suspended
  • Critical only — the high-signal ones: Expired, Revoked, and Suspended (the default)
  • Custom — tick exactly which alert types you want

The personal Your Notification Preferences card with the alert level selector

Everyone can set their own preferences here. The remaining sections are admin-only and set the behaviour for the whole organisation.

Step 3: Choose who in the workforce gets notified​

Under Workforce notifications, decide whether Oho emails your people directly:

  • Notify workers about their expiring credentials — emails each worker at the address on their profile as their credentials approach expiry.
  • Also notify the worker's manager — copies the manager, with a From: choice of how early to start.

The Workforce notifications toggles

Worker emails reach your own people

Turning on worker emails contacts your workers directly — they don't need an Oho login and can't opt out individually, so make sure your organisation has told them to expect these. Oho gives you a grace window: emails begin one hour after you save, so you can turn it back off before then to cancel.

Step 4: Set the expiry timing​

Under Expiry timing, set how far in advance a credential is flagged — Expiring (default 30 days) and Expiring Soon (default 7 days). You can add per-credential-type overrides so, say, a First Aid certificate warns earlier than a card that renews quickly.

The expiry timing lead-time settings

Step 5: Add a delivery channel​

Under Notification channels, choose where org-wide alerts are delivered — any combination of:

  • Email — a catch-all address (e.g. alerts@yourorg.com) used when no personal preference applies.
  • Microsoft Teams — paste the channel's Incoming Webhook URL; the page includes step-by-step instructions for getting one.
  • Slack — paste the channel's Incoming Webhook URL, again with instructions on the page.

For Teams and Slack you can also choose which alert types post to that channel.

The Notification channels section with Email, Teams, and Slack

Step 6: Save​

Click Save to apply your changes.

Checking what was sent

The Delivery log tab on the same page shows recent notifications and where they went — useful when someone says they didn't get an alert.

Change how the emails read

This page controls when alerts send and to whom. To change how the emails themselves look and read — wording, branding, and dynamic details — an Admin can customise the email templates.

What's next​