Notification recipients (platform admin)
In brief: Manage who receives platform alerts (credit-report requests, system events) on WhatsApp + email.
Manage who receives Certivus platform-level alerts (credit-report requests today; system events as they're wired) and on which channel (WhatsApp, email).
Where you do it
/admin/notification-recipients — visible only to platform admins.
Add a recipient
- Click Add recipient.
- Pick a channel (WhatsApp or Email).
- Enter the recipient:
- WhatsApp: E.164 format with country code, no spaces.
Example:
+447376533434. The form validates the shape. - Email: standard email format.
- WhatsApp: E.164 format with country code, no spaces.
Example:
- Optional label so you can tell people apart in the list (e.g. "Mehmood mobile", "Ops VA", "Backup admin").
- Pick categories — at least one. Each category is a kind of alert (currently just "Credit report request"; more added over time).
- Leave Enabled on. Save.
The recipient starts receiving alerts immediately — no template re-approval needed (the WhatsApp template was approved once during Phase 62 setup).
Edit, mute, or remove
- Edit any field via the pencil icon — same dialog.
- Mute without deleting via the per-row Enabled switch.
- Remove entirely via the trash icon; confirm in the dialog.
History is not preserved on delete — if you need a paper trail for who used to be on the list, mute instead of delete.
Recipients don't have to be admin users
You can add an external staff number/email (VA, ops contractor) without creating a Certivus admin account for them. The recipients table is free-form — no FK to user accounts.
Privacy note: outgoing alerts mention firm name + company name. Don't add a recipient who shouldn't see that information.
What happens if no one is configured
If the table is empty for a (category, channel) combination, the notifier falls back to:
- WhatsApp: sends to the
WHATSAPP_ADMIN_NOTIFICATION_NUMBERSupabase secret (set during Phase 62 bootstrap). - Email: blasts every user with
user_roles.role = 'admin'(the Phase 62 behaviour).
So you can never end up with zero alerts after enabling Phase 63. The fallback is only consulted when the table has zero matching rows.
Adding a new category
Wire a new event (e.g. SAR filed) → call the notifier with a new
category key → add the category definition to
src/lib/notifications/notificationCategories.ts. The admin UI's
category checklist auto-picks it up.
Related
- Credit reports (firm-facing)
- WhatsApp template management — admin Settings → Templates tab
Didn't find what you needed?
Contact support