Notifications

Notifications are what the product tells you when you are not looking at it. Most of them are routine; four exist because they report something that happened with nobody watching.

The four that matter

NoticeSent whenWho gets it
Campaign completedA send finished, with its countsOwners and administrators
Scheduled send refusedA scheduled campaign could not go out — the reason is named, including how many units were missingOwners and administrators
Sending pausedThe email provider suspended your organizationOwners and administrators
Domain purgedA domain declared but never verified was removedOwners and administrators
The second one is the one to know about. A campaign you scheduled for Tuesday morning is checked at its departure time; if it is refused, it goes back to draft, its schedule is cleared, and this notice is what tells you — otherwise you would find out from a reader asking where the newsletter went. See why a send is refused.
A member never receives these. Sending notices go to owners and administrators, because they are the ones who can act on them. If nobody in your organization holds one of those roles for a given inbox, nobody is told.

The rest

Account and billing events — invitations, payment outcomes, subscription changes, security alerts, password and email changes — arrive the same way, addressed to the person concerned rather than to the organization.

What it implies elsewhere

Notifications are a record, not a monitor. They tell you what already happened; the sending settings screen tells you what is currently wrong, before you commit to a send. When in doubt about whether something will go out, look there rather than waiting to be told.