The account-level on switch

A single switch above the matrix deciding whether this system may contact the account or its customers at all — off for every account until someone turns it on.

What it is

Distinct from the master switch below it, which sweeps per-event rows. This one is the account's consent, recorded as the moment it happened.

Also called: enable notifications for my company · notifications are off · start sending

See it
The account-level on switch
Area
Platform & Admin
Group
Notifications
System
Notifications
Solves
1 named problem
01The banner reads its state from a dedicated settings route and posts the change back.
02On failure it leaves the previous state visible 'rather than lying'.
03The dispatcher checks the stored timestamp on every send.
The account banner with its switch and the 'enabled on…' date. NotificationsTab.tsx. Sample data — no customer information appears here.
How it works
  1. 1The banner reads its state from a dedicated settings route and posts the change back.
  2. 2On failure it leaves the previous state visible 'rather than lying'.
  3. 3The dispatcher checks the stored timestamp on every send.
Why we built it

Migration 149's reasoning, restated in the component: 'this one decides whether this system may contact the tenant or their customers at all. Off is the default for every account, so nobody is subscribed to anything by arriving.' A timestamp rather than a boolean because 'has this tenant ever opted in is a fact about a moment, and the moment is the interesting part when someone later asks why an email did or didn't go out.'

The problem
  • Consent that could not be evidenced after the fact
Sound familiar?
What you get
Explicit, dated consent
One switch that governs everything outbound

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 →