Notifications

Security and release notifications are what the Solo plan adds. Scheduled checks and fanning out to a team are what Team adds. Privacy changes come with Enterprise’s privacy history.

The point of all of it

The events worth hearing about come from the secrets pane, reconciliation and the connection. Inviting your team is who else can receive them.

Somebody finding out before a customer does.

What is worth being told about

A secret past the rotation cadence its registry entry declares. That is a health key a capability publishes, and it is a count — not a list of which ones, because the list is a map of where to push.

A rotation that came back unrecorded. Rolled at the issuer, successor never stored — critical, and the one outcome that means somebody must go to a console now.

A connection whose ping fails. Surfaced as needs reconnecting, never as a silent dead link.

A pending migration. A deploy will refuse rather than ship a Worker whose code expects a column that is not there.

Deliveries that have not projected. The reconciliation list, oldest first.

Email jobs sitting undispatched — a configuration fact rather than a transient one.

Release news

Security releases are their own switch, and size is one ladder: none, major releases, minor and major, or every release. Asking for patches asks for minors and majors too, so you are never told about a fix and not about the breaking change it followed.

A project can be set apart. Each one follows your account’s answers until you give it its own, from the project’s record or from Notifications. Use account settings returns it to the default. What the organization enforces still wins over both.

As it lands, or in a weekly digest. Each release reaches you as it lands unless you turn the digest on. Then ordinary releases wait for one mail at nine on Monday morning in your time zone, or the organization’s, or UTC, grouped by project with each release’s note. A week with nothing sends nothing.

Security never waits. A security release is sent as it lands whatever you chose, and the digest lists it as already sent.

Nothing goes to an address that is not verified.

Scheduled checks

Once an hour, against every production connection rather than only when somebody opens a browser. Four conditions: failed renewals, webhook drift, a reconcile that stopped or is failing, and a tester streak at risk. Each is mailed once per occurrence, at a threshold you set. Alerts is the pane, and says what each one looks for.

Each alert is a switch here like any other: Failed renewals, Webhook drift, Reconcile stopped or failing, Tester streak at risk, and Alerts not evaluating for a check that cannot read what it needs. All five are on by default. An organization may also add up to ten confirmed addresses outside the team, such as an on-call alias, and they receive the alerts too.

The reads are ordinary control-plane calls — signed, single-scope, single-use, sixty seconds, under the subject system — and every one is a row in your own audit trail, including the ones that found nothing wrong.

Privacy changes, on Enterprise

Three more switches come with the privacy history: Privacy changes, when a field on a watched environment gains or loses a marker, changes class or loses encryption, removals first; Privacy inventory unreadable, when a watched environment has failed to read for three checks in a row, and when it reads again; and Privacy posture report, the periodic report an admin turns on. All three are on by default, and go to the confirmed extra addresses too. Each change is mailed as it is indexed, or in one digest a day, as the privacy pane is set.

Fanning out to a team

One person on Solo. A team on Team.

With a shared record of who acted on what, because every administrative action carries the dashboard user’s own subject alongside the connection id.

What a notification never contains

No secret value. None exists in any response — the types have no field for one.

No proxied response body. Never logged, never cached, and not put in a notification either.

No customer personal data. A count and a code, not a name and an address.

Notifications the kit sends on your behalf are a different thing

Those go through your own email capability, on your own domain, with your own suppression list and bounce handling.

Nothing here mails your users.

Turning things off

Per notification kind, and release news per project and per cadence as above. And the CLI’s own update notifier is separate again — pithy doctor --disable-notifier, or the environment variable.

ESC