Notification settings
This screen controls how Routy reaches you: which events you hear about, and on which channel. It has two layers, and they answer different questions.
- Your own notifications — what you receive. Everyone has this.
- Account-wide routing — what the account receives, and where its Slack alerts go. Only an account admin sees it.
A change here takes effect on the next notification. Nothing is sent to confirm the change itself.
Email notifications
The switch above the list is a single opt-out covering all notification email. Turn it off and Routy stops emailing you about anything in the list below, including notification types that are added to Routy after you set it.
That last part is why the switch exists. The per-type Email toggles cannot express it: a type nobody has touched falls back to its own default, and some types default to on, so a new type can start emailing you even though you had switched off every type that existed when you last looked.
Two things the switch does not do:
- It does not stop security and account email. Password resets, email address confirmations and similar messages are sent whatever this is set to, because losing them would lock you out of your own account. Those types show a padlock in the list and have no Email toggle.
- It does not erase your per-type choices. They are kept exactly as they were, shown greyed out while the switch is off, and come back into effect the moment you switch it on again. Switching off and on is safe.
In-app alerts, browser push and Slack are unaffected. If you want to stop hearing about something entirely rather than just by email, switch it off per type instead.
If you switched email off and still get email
Check which kind of message it is. Security and account email is expected — see above. Anything else is worth reporting.
Your own notifications
One row per notification type, grouped by the area it comes from. Each row has a toggle per channel:
Some cells show a dash instead of a toggle. That means the notification type cannot be delivered on that channel at all — not that it is switched off.
A row marked Customized is one you have changed from its default. The undo button at the end of the row puts it back to the default and the badge disappears.
Rows with a padlock always send and cannot be switched off.
My email address is not confirmed
A warning appears at the top of the screen when it isn't. Until you confirm your address, email notifications will not reach you however these toggles are set — nothing bounces and no error is shown anywhere. Confirm your address from your profile and they start arriving.
Push notifications are not working
Push needs permission from this browser, and the permission is per browser and per device — granting it on your laptop does nothing for your phone. The Push section at the top of the screen shows the current permission state and whether this browser supports it at all.
If you previously blocked notifications for Routy, the browser will not ask again; you have to clear it in the browser's own site settings.
Account-wide routing
Visible to account admins only. This is the account's own notification routing, separate from your personal choices — it decides where notifications about the account go, including to Slack.
Slack is here rather than in your own notifications because Slack delivery uses one webhook owned by the account. There is no personal Slack setting.
Slack
Paste an incoming webhook URL from Slack, test it, then save. The test posts a real message to the channel, so you will see it in Slack if the URL is right.
The URL is stored masked — reopening the screen shows a placeholder rather than the original value. Saving without changing it keeps the stored URL.
Turning Slack off stops Slack delivery for the account without discarding the webhook URL.
When to escalate to engineering
Most notification problems are one of the causes above. Worth reporting:
- You receive email after switching the email master switch off, and the message is not a password reset or address confirmation.
- A notification type you expect is missing from the list entirely.
- The Slack test succeeds but real notifications never arrive in the channel.
- A toggle springs back to its previous position after you set it, which means the save failed.
Include the notification type's name as it appears in the list, and roughly when you expected the notification.