When you have multiple programs run by different staff members, you don't want every shift signup to spam the entire team.
How routing works
When creating or editing a shift, the Notify these admins on signup field accepts a list of staff users. Only those users receive the notification when a volunteer signs up for that shift.
Common patterns
- Per-program coordinators — Wise Institute shifts route to Sheila; QLI shifts route to Josiah; food pantry shifts route to the food pantry coordinator.
- Multi-coordinator programs — list multiple users; everyone gets notified.
- Backup coordinators — list a primary plus a backup who covers when the primary is on PTO.
Default behavior
If the notification list is empty, the shift owner gets notified (whoever created the shift). This preserves the simple-default behavior for orgs that don't need fancy routing.
Why this matters
This shipped in BRV-1281 specifically because Wise (a real customer) needed it: their previous platform either notified everyone (spam) or no one (missed signups). Per-shift routing solves the middle case.