A settings screen for cross-account notification management. Accounts with no saved preferences are shown seeded from the catalog defaults — because 'no row' means on, not off — so the operator sees what the customer is genuinely getting rather than a misleading blank.
Also called: too many emails · turn off notifications · notification settings for a client · stop the alerts
- 1Pick an account to open its full event matrix, event by event, with In-app and Email toggles.
- 2Three sweeps act on the whole account: all on, all off, email off.
- 3Each sweep confirms with copy that says exactly what the customer will and will not receive afterwards.
- 4Accounts using pure defaults are labelled 'Using defaults' rather than shown as blank.
- 5Writes go through a platform-gated route because the tenant-facing data path is locked to the caller's own account.
The page states the trap it avoids: 'notify.ts falls back to registry defaults when a row is absent, so "no row" means "on", not "off". Showing empty here would tell the owner a sub-account is silent when it is in fact emailing every event.'
- An account with no saved preferences looked silent while emailing every event.
- Adjusting a customer's notifications required entering their account.
- Turning email off meant unticking dozens of rows one at a time.
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 →