MegaManager notifies you in two places at once: the Inbox in the dashboard, and email.

What raises a notification

Event	Severity
Site went down	critical
Site came back up	informational
Site disconnected	critical
Backup completed	informational
Backup failed	warning
Updates available	informational
New comment on a site you manage	informational
Team invitation	informational

Choosing what you receive

Preferences exist globally, under Settings → Notifications, and per site on the site's Settings tab. The per-site setting wins where both apply, which is how you can keep a noisy staging site quiet without muting the rest.

Each type can be turned off independently. Critical alerts are the ones worth leaving on.

Email frequency

Email can be immediate or batched. Batching collects the period's events into one message, which is usually the right choice for informational types and the wrong one for critical alerts.

Every notification email carries an unsubscribe link that turns off that type for that site.

Site disconnected

Worth calling out, because it is the notification that tells you something is wrong with the monitoring itself rather than with the site. It fires when someone disconnects the plugin from the WordPress side, when a manual sync fails to reach the site, and when the site stops answering us.

That last one deserves a word on how it is decided, because silence alone does not count. The connector reports in every five minutes using WordPress cron, and WordPress cron only runs when somebody visits the site — so a site with no traffic overnight stops reporting while being perfectly healthy. When a site has been quiet for half an hour MegaManager therefore calls it directly and lets the answer decide. A site that answers is left alone entirely; only one that fails to answer is marked disconnected, and the notification says what went wrong — unreachable, or answering but refusing our credentials.