Notification Manager

Configure, for every notification type your workspace uses, exactly which users, roles, and external contacts get alerted — and on which channels. This is the admin control panel behind the alerts; it decides who's eligible to receive something, not any one person's personal preferences.

Who can use it — Anyone with "manage tenant notifications" permission. This is a distinct, admin-level permission — separate from the "manage my notifications" permission that lets any user manage their own inbox. See Roles & Permissions for how access is set.

Where to find it — Administration → Notification Manager in the sidebar.

How to use it

The page is a table of Notification Policies — one row per notification type (e.g. Critical Safety Alerts, Fleet Defect Alerts, Workforce Qualification Alerts) — grouped by Category (Fleet, HR, Safety & Compliance, Billing, Day Works, and others). Each row shows:

Name and Key (the Key column is hidden by default — toggle it on from the column picker if you need the technical identifier).
Active Channels — a badge showing what will actually fire right now for this policy: SMS, Email, In-App, or Muted if nothing is configured to receive it at all.

Two actions sit on every row:

Manage — opens a slide-over to set who receives this policy's alerts (covered below).
Test — sends a real test notification through the pipeline so you can confirm delivery.

Assigning recipients

Click Manage on a policy to open its slide-over, with three sections:

Internal Team — add individual workspace users. Search by name, then tick Email and/or SMS as the channels for that person. In-app delivery isn't a checkbox here — a targeted user still gets the in-app notification regardless.
Roles — add a role (e.g. Site Supervisor, Project Manager) so every current member of that role receives the alert. Same Email/SMS channel checkboxes per role. A role with no members attached to your tenant doesn't count as coverage even if it's listed.
External Contacts — add vendors or other third parties who aren't workspace users. Search existing contacts or create a new one on the fly (Name, Company Name, Email, Phone) without leaving the form.

Every recipient row — internal, role, or external — carries the same two channel checkboxes: Email and SMS. A helper note on the Internal Team section is a reminder worth heeding workspace-wide: SMS messages consume credits from your monthly quota — assign SMS only to critical notification types.

Click Save Changes to apply. Every change here is written to the audit log (who changed what, before/after), so subscriber changes are traceable.

SMS is admin-assigned, not personal

This is the key difference from the personal notifications page: SMS is never a self-service toggle. A user cannot turn SMS on for themselves from My Notifications — it only ever appears there as "assigned by your workspace admin." You assign SMS recipients here, per notification type, per person/role/contact. Because SMS draws down your tenant's SMS credit balance, keep it tight — reserve it for genuinely urgent, Tier-1-style alerts rather than routine updates. See SMS Usage to check remaining credits.

Email, by contrast, is a shared control: you can assign it here for any recipient, and a user can also independently enable Email for themselves for policies covering their own permissions on their My Notifications Settings tab. In-app delivery is always on for anyone targeted or subscribed — nobody can be muted from the in-app inbox for something addressed to them.

Testing a notification

Use Test on a policy row to send a real notification through the same pipeline as production:

Pick a Scenario — each policy can have more than one underlying alias (e.g. Service Due Soon vs Service Overdue under Plant Service & Checklist Alerts), and the scenario determines which one fires.
Pick a Channel — the options offered depend on what that scenario allows (In-App, Email, SMS, Push).
Optionally override the Message text.
Send Test queues it immediately, exactly as it would fire in real use — useful for confirming a new recipient or channel actually receives something before you rely on it.

At the top of the page, a banner watches your Tier-1 policies — the safety- and compliance-critical alerts (things like Critical Safety Alerts and Site Inspection Overdue). If any Tier-1 policy has zero active recipients, it's flagged here with a red banner and a one-click Manage button straight into that policy's slide-over. When every Tier-1 policy has at least one recipient, the banner collapses to a quiet green confirmation. Don't ignore this — a Tier-1 alert with no recipients means a safety or compliance event fires and reaches nobody.

Spam Radar

At the bottom of the page, a stacked bar chart shows this week's delivery volume per policy, broken down by channel (In-App, Email, SMS, Push). Use it to spot noisy policies or heavy SMS usage at a glance — SMS bars are highlighted in amber since that's the channel that costs credits. If nothing has been delivered this week, the chart is replaced with a simple empty-state message.

Connected pages

My Notifications — where individual users read their alerts and manage their own Email preference. SMS and in-app can't be self-managed there; SMS assignment lives here, and in-app is always on for anyone this page targets.
Broadcasts — manager-composed messages that arrive as notifications; a separate feature from the policy-driven alerts configured here.
SMS Usage — check your tenant's SMS credit balance before assigning more SMS recipients.

Tips & common mistakes

A policy shows "Muted" — nobody is set to receive it and it isn't a targeted alias with baseline in-app delivery. Open Manage and add at least one recipient, or check the Blind Spot banner if it's a Tier-1 policy.
Don't over-assign SMS. Every SMS recipient on every notification type draws from the same monthly credit pool — check SMS Usage and keep SMS to the alerts that genuinely need an instant text.
Adding a role doesn't guarantee coverage. If the role currently has no members in your tenant, it won't count as an active channel until someone holds that role.
Use Test before trusting a change. After adding or changing a recipient, send a Test on the relevant scenario/channel to confirm it actually lands, rather than waiting for the real event.
This isn't the same page as My Notifications. If a user says they're not getting an alert, check here first for whether they (or their role) are even a recipient — then check their personal Email toggle on My Notifications if Email specifically is the issue.