Notifications

The dashboard can tell your team when something important happens to a project. Right now it notifies on:

• Deploys — when one finishes, and when one fails.
• Health checks — when a service that was healthy starts failing or becomes unreachable (only on the transition, so a service that stays down doesn't notify every minute).

Notifications go out over two channels:

• Browser push — a notification on the desktop or phone, even when the dashboard tab is closed.
• Email — sent to each member's account email.

Both channels are opt-in. Nothing is sent until an administrator configures the channel, and each person can turn channels on or off for themselves.

Who gets notified

Everyone in the organization that owns the project. Each member can opt out of either channel from Account settings → Notifications, so people who don't want the noise don't get it. Browser push is per-device (each browser you enable it in subscribes separately); email is per-account.

Enabling email

Email is sent over SMTP, which every major provider accepts — SendGrid, Mailgun, Mailjet, Postmark, Amazon SES and others. Point the dashboard at your provider's SMTP host and email turns on. Set these environment variables on the dashboard host:

SMTP_HOST=smtp.sendgrid.net
SMTP_PORT=587
SMTP_USER=apikey
SMTP_PASS=<your API key or SMTP password>
SMTP_FROM=Managed <[email protected]>
SMTP_TLS=starttls          # starttls (default), ssl, or none

Or, equivalently, a single URL:

SMTP_URL=smtp://apikey:<key>@smtp.sendgrid.net:587
SMTP_FROM=Managed <[email protected]>

SMTP_FROM is required — without a From address, email stays off. To switch providers later, change the host and credentials; nothing else changes.

Enabling browser push

Browser push uses the Web Push standard, which needs a one-time VAPID key pair that identifies your dashboard to the browsers' push services. Generate one with:

managed notify generate-vapid

It prints three lines. Set them as environment variables on the dashboard host:

VAPID_PUBLIC_KEY=...
VAPID_PRIVATE_KEY=...
VAPID_SUBJECT=mailto:[email protected]

Keep the same pair for the life of the deployment — regenerating it invalidates everyone's existing subscriptions. Once the public key is present, an Enable browser notifications toggle appears in each user's account settings; turning it on asks the browser for permission and subscribes that device.

Deep links

APP_ORIGIN sets the base URL used for the "Open dashboard" link inside each notification, e.g.:

APP_ORIGIN=https://managed.yourdomain.com

How it works

The dashboard owns the browser subscriptions and each person's preferences. When a deploy finishes, it resolves who should hear about it, then hands the event to the managed binary's notification library (managed notify send), which renders the message and sends it over whichever channels are configured. Expired push subscriptions are detected and cleaned up automatically. A delivery is recorded per person and channel, so a retried deploy never notifies the same person twice.

Turning it off

Unset the channel's environment variables to disable it globally, or use Account settings → Notifications to opt out for yourself.