Where a stage's behaviour comes from

Each stage shows the rung its rule came from — this stage, all stages of that role, org-wide, legacy or none — and editing an inheriting stage seeds the new rule from what it currently does.

What it is

A labelled source on every row plus a 'Reset to inherited' action, which deletes the stage's own rule rather than switching it off.

Also called: why isn't this stage notifying · inherited settings · reset to inherited · rule source

See it
Where a stage's behaviour comes from
Apr
May
Jun
Jul
Ronan Petsch — Equipment Storage
Framing
Marlin Hoover — Riding Arena
Concrete
Marlin Hoover — Riding Arena
Trim
Marlin Hoover — 40×64 Shop
Framing
Ronan Petsch — Barndominium
Concrete
Framing crewConcrete crewTrim crew
A stage row showing 'Org-wide' as its source with the Reset to inherited action beside it. StageNotificationsTab.tsx. Sample data — no customer information appears here.
How it works
  1. 1The effective rule is resolved server-side and returned with its source, recipients, channels and copy.
  2. 2Editing an inheriting stage copies the currently effective rule as the starting point.
  3. 3Reset deletes the row so the stage falls back to whatever it inherits.
Why we built it

The header states the design principle: 'Editing a stage that is inheriting SEEDS the new rule from what it currently does, so turning one thing off never silently changes five others. "Reset to inherited" deletes the rule, which is a different act from switching it off: off is a decision to stay silent, inherit is a decision not to decide.'

The problem
  • Edits silently rewriting unrelated stages
  • No distinction between off and inherit
Sound familiar?
What you get
Every stage says where its behaviour came from
A safe way back to the default

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 →