Notifications — who hears about what

An event-by-role grid deciding which roles get in-app, email or text for every event in the system, split into internal team alerts and external customer messages.

What it is

One row per event type, one toggle per role and channel, grouped into collapsible categories such as Sales Pipeline, Estimates & Orders, Invoicing & Payments, Contracts & Legal and Project Management. An audience switch filters to internal, external or all. Customer-facing messages have their own granular email and text switches, held apart so a builder can want one, the other, or both.

Also called: notification settings · who gets alerted · team alerts · customer emails

See it
Notifications — who hears about what
Area
Platform & Admin
Group
Notifications
System
Notifications
Solves
3 named problems
01Saving upserts a preferences row keyed on the organisation and event type; the same rows drive server-side recipient resolution.
02Categories collapse, with an accordion mode that keeps one category open at a time or opens them all.
03Turning things off clears only the channel flags — role subscriptions are left intact so switching back on restores the routing rather than a generic default.
The Notifications grid: collapsible category with event rows and per-role channel toggles, audience filter above. NotificationsTab.tsx. Sample data — no customer information appears here.
How it works
  1. 1Saving upserts a preferences row keyed on the organisation and event type; the same rows drive server-side recipient resolution.
  2. 2Categories collapse, with an accordion mode that keeps one category open at a time or opens them all.
  3. 3Turning things off clears only the channel flags — role subscriptions are left intact so switching back on restores the routing rather than a generic default.
  4. 4Project-level assignees are configured on the project itself, not here, because they are not organisation-wide.
Why we built it

The internal/external split is 'the distinction must be visible and filterable' — and the category grouping came from the same pass ('see the different categories and have all of them'). The comment also notes that notifications ARE automations in people's minds, which is why the automations tab is folded in underneath. The separate text switch is migration 224.

The problem
  • Notification routing was implicit and unconfigurable.
  • Internal alerts and customer-facing messages were indistinguishable.
  • Turning notifications off destroyed the routing configuration.
Sound familiar?
What you get
Each event notifies exactly the roles that need it, on the channels they read.
Customer-facing messages are visibly separate from internal noise.
Switching notifications back on restores the setup you had.
What's inside

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 →