Who receives what
Mail is addressed by responsibility, not broadcast to everyone in the workspace.
A deployment started by a push is attributed to the pusher where their email matches a workspace member; otherwise it falls back to the application’s owner.
The switches
Deployment failures — a deployment you started did not finish. On by default. Successful deployments — the same, for the ones that worked. Off by default, because on an active application this is the noisiest mail Miget sends. Health alerts — crash loops, failing health checks, expiring certificates, and observability ingestion crossing its limit. Sent to workspace admins, since these usually need somebody with the access to act. State changes — an application, service, or add-on started, stopped, or failed. Covers workloads of every kind, not applications alone. Critical alerts — blocked or deleted applications, and billing. Always on and not switchable: these either cost money or stop your workloads, and neither is something to find out about late.What is not switchable
Access and billing mail is never optional: invitations, ownership transfers, access granted or revoked, subscription and payment changes, expiring API tokens, and resource lifecycle warnings such as inactivity or deletion for non-payment. Turning those off would let somebody lose a resource quietly.Next Steps
Webhooks
The same events as a signed POST to your own endpoint.
Slack
The same events, posted to a channel.