Security and release notifications are what the Solo plan adds. Scheduled checks and fanning out to a team are what Team adds.
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.
Scheduled checks
Run against your Workers on a schedule rather than only when somebody opens a browser.
They are ordinary control-plane calls — signed, single-scope, single-use, sixty seconds — and every one is a row in your own audit trail, including the ones that found nothing wrong.
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 the CLI’s own update notifier is separate again — pithy doctor --disable-notifier, or the environment variable.