Test before you send: the Developer settings
Turning workforce notifications on for the first time, or changing an email template, is the kind of change you'd rather see once before everyone else does. Settings → Developer → Developer Settings is where you do that. Its own subtitle puts it well: organisation-wide testing toggles, and they affect everyone.
The whole Developer section is for the technical tier. If it isn't in your settings menu, you don't have technical setup rights, and an administrator who does has to make these changes.
Email override
A switch and an address. While it's on, every outbound system email goes to that one address instead of its real recipient — not a copy, a redirect. Nobody else receives anything.
That's the point when you're testing, and the hazard when you forget. Real alerts that would have reached real people during the window are gone; they aren't held and re-sent when you turn it off. Keep the window to minutes, and turn it off before you walk away.
Turn it off and emails go to their real recipients again, or to the deploy-time override address if one was set for your environment.
Automated alerts
A badge reading Active or Silenced, and buttons to silence for 1 hour, 4 hours, 24 hours or indefinitely. Resume alerts now ends it early.
Read the scope carefully, because it's narrower than "notifications":
| Silenced | Not silenced |
|---|---|
| Credential status alerts — email, Slack and Teams | Sign-up and password-reset emails |
| Scheduled verification-run alerts — Slack and Teams | Fetch requests and credential checks |
| Your own outbound webhooks |
Anything a person triggers still sends. Silencing is for the background noise, not for going quiet.
Notification webhooks
The Microsoft Teams and Slack incoming-webhook URLs that org-wide alerts post to, and which alert types go to each. These are the same channels described in Set up notifications.
Trying workforce notifications safely
Turning on Notify workers about their expiring credentials reaches your whole workforce, and on an organisation with a few hundred credentials already past their expiry date that is a lot of mail at once. The sequence worth following:
- Turn the email override on, pointed at your own address.
- Turn the workforce notification on and save.
- Wait for the first run and read what arrives. You're looking at volume and wording, not at any one message.
- Turn the workforce notification back off if it isn't what you wanted.
- Turn the email override off.
Worker emails have their own grace window — they begin an hour after you save — so you can also cancel in that hour without the override. The override is what lets you see them first.
The override and the silence both stay on until somebody turns them off, and neither announces itself anywhere except this page. An override left on over a weekend is a weekend of alerts nobody received.
Related
- Set up notifications — who gets alerted, about what, and when
- Customise email templates — the wording these emails use