The matrix that drives recipient resolution. Categories collapse, and a single/multiple accordion mode mirrors the sales pipeline's behaviour. Saving upserts one preference row per event. A rejected save rolls the toggle back and says why, loudly.
Also called: notification settings · who gets emailed · turn off notifications · alert preferences
- 1Rows come from the shared event catalogue so the tenant and platform screens can never describe different things.
- 2Each row saves independently; sweeps write every row in one request.
- 3A failed save restores the previous value and shows the error in the same banner the sweeps use.
- 4Task automations are embedded at the bottom of the same screen.
Categories are “see the different categories and have all of the notifications in each of the respective categories”, and 'headers are toggleable'. Automations were folded in here for the same reason: 'notifications ARE automations in people's minds'. The rollback is bug: 'toggles looked saved, then reverted on refresh… A rejected save must never masquerade as saved.'
- Silent save failures presenting as success
- An unnavigable flat list of events
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 →