Who gets told — roles, named people, and project assignees

Recipients come from three sources — the roles subscribed to that event, individually named people, and anyone assigned to the project — and assignment is itself an opt-in.

What it is

Role routing is the org grid: for each event, which of admin / sales / project manager / crew lead / worker hears it. Explicit user ids cover the admin's one-off picks. Project assignees are added automatically for project-scoped events regardless of the role toggles, because being assigned to the job is the subscription.

Also called: notification routing · who is subscribed · notify the PM · assignees always get told

See it
Who gets told — roles, named people, and project assignees
Area
Platform & Admin
Group
Notifications
System
Notifications
Solves
2 named problems
01notifyEvent unions role matches, explicit user ids and project_assignments rows for the payload's project.
02Events addressed to one named person (lead assigned, crew acceptance, task assigned, task reminder) carry an empty default role list and are targeted directly through notifyUsers instead.
03The agency's own account resolves its roster from the platform staff list rather than org members.
The event × role matrix with one row's role checkboxes and channel switches highlighted. NotificationsTab.tsx. Sample data — no customer information appears here.
How it works
  1. 1notifyEvent unions role matches, explicit user ids and project_assignments rows for the payload's project.
  2. 2Events addressed to one named person (lead assigned, crew acceptance, task assigned, task reminder) carry an empty default role list and are targeted directly through notifyUsers instead.
  3. 3The agency's own account resolves its roster from the platform staff list rather than org members.
Why we built it

The Settings tip states the design in the builder's words: 'per-project assignees still get pinged for project_started, project_stage_completed, and project_completed even when no role checkbox is on for that event — your assignment is itself the opt-in.' Direct addressing for person-shaped events is annotated in the registry: 'a task assignment is addressed to one named person, so notifyUsers targets them directly and the role list stays empty.'

The problem
  • Role-only routing missing the person actually on the job
  • No way to loop in one individual
Sound familiar?
What you get
Assignment to a job carries its own notifications
Per-event, per-role control plus individual picks

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →