Choose who gets notifications

View as Markdown Open in ChatGPT Open in Claude

Notification routing lives at Settings → Notifications. It decides who in your organization is told when something needs attention: a verification waiting on a decision, a verification an applicant left unfinished, or webhook deliveries that stopped.

Each notification has its own card, and each card saves on its own. Changing one does not touch the others.

This page is about what your organization sends. To change what reaches you personally, use the “Your notifications” card on Settings → Profile. See Manage your profile.

What you can be notified about

Notification	Sent when	Who gets it before you configure anything
Verification needs review	A verification is parked for a person on your team to decide.	Owners and admins
Verification left unfinished	An applicant starts a verification and does not finish it before most of its time is up.	Nobody
Webhook deliveries turned off	The platform stops delivering to one of your webhook endpoints because it kept returning errors.	Owners and admins

The last column is the default. It applies until an owner or admin saves that card, and a card nobody has opened is not the same as a notification that is switched off: unless the last column says Nobody, that notification is already going out.

Where the last column says Nobody, nothing is sent until you pick an audience and save. The card says so as well: “Nobody is being notified yet. Choose who should get this, then save.”

Route a notification

Open Settings → Notifications.
Use Send this notification to turn the notification on or off for the whole organization. Turning it off keeps your audience and delivery choices for when you turn it back on. Webhook deliveries turned off is the exception: it carries a Cannot be turned off badge and no such switch, because it is how you learn deliveries stopped without having to go looking. On that card, go straight to step 3 and choose who gets it.
Under Who gets it, pick one:
- Everyone in the organization: every member, whatever their role.
- Owners and admins: members whose Owner or Admin role covers the whole organization. A role limited to one location is not included.
- Specific people: only the teammates you tick in the list that appears.
Check How it is delivered, and pick at least one method.
- Email goes to each person’s account address. It needs no setup on their side.
- Push notification sends a short notice to a teammate’s browser. It reaches them only on a browser where they have turned on notifications for the console, so a teammate who has not turned them on hears nothing from this method.
- Keep Email selected alongside Push notification unless you know everyone in the audience has browser notifications turned on. A push-only card is silent for anyone who does not.
Click Save on that card.

Only Owner and Admin can change notification routing. Other roles see a notice instead of the cards, and the server refuses the change as well, so the notice is guidance rather than the boundary. To get routing changed, ask an owner or admin, or ask an owner to update your role on Settings → Organization → Team Members. See Manage access.

Named recipients are checked against your current team

When you pick Specific people, you are saving a list of team members. That list is matched against your organization’s current membership every time the notification goes out.

So a name that goes stale is inert, not a leak: once someone is removed from the organization, they stop receiving the notification, even though their entry is still saved on the card.

The card does not hide the stale entry, because you are the one who can clear it. It shows “Some people on this list are no longer in this organization. Remove them, then save.” with a Remove button next to each one. Until you do, that card refuses to save again, so clear the leftovers first and then make your change.

You can name up to 200 people on one notification. If you need more than that, switch to Everyone in the organization or Owners and admins instead.

Your own switches are a different page

Two pages control notifications, and they answer different questions.

	Settings → Notifications	Settings → Profile
Decides	who in the organization gets a notification at all	what reaches you personally
Who can use it	Owners and admins	every member, including Viewers
Scope	the whole organization	your own account

If you are looking for a switch that stops a notification reaching your own inbox, it is on Settings → Profile, not here. If a teammate asks to stop receiving something, point them there rather than removing them from the audience, so the rest of the organization keeps its coverage.

On Settings → Profile each notification has its own switches, except the ones below, which stay on for everyone they are routed to:

Webhook deliveries turned off: it is how the platform tells you that deliveries stopped without anyone having to go looking. There is no per-person switch for it, so the way to change who is told is the audience on this page.

Troubleshooting

A teammate is not getting a notification you routed to them. Check these in order: Send this notification is on for that card (the always-on notification has no such switch), the audience covers them (a role limited to one location is not covered by Owners and admins), and they have not switched that notification off for themselves on Settings → Profile.
Email arrives but the push notification does not. Push reaches a person only on a browser where they have turned on notifications for the console, and only while that browser keeps the permission. Ask them to turn browser notifications back on, and keep Email selected on the card so nothing is missed in the meantime.
“Choose at least one person to notify, or pick a different audience.” You picked Specific people without ticking anyone. Tick at least one teammate, or choose a different audience, then save again.
“Choose who should get this notification, then save again.” The card has no audience yet. Pick one under Who gets it and save.
“This organization has no other team members yet.” There is nobody to pick for Specific people. Invite a teammate from Settings → Organization → Team Members, or choose Everyone in the organization or Owners and admins.
A notice that the picker is showing only the first of your team members. Your organization has more members than the list loads. Pick Everyone in the organization or Owners and admins to reach everyone, rather than assuming the visible names are the whole team.
“Someone else changed these settings a moment ago.” Another owner or admin saved the same card while you were editing it. Reload the page to see the current values, then make your change again.
“Could not load your saved notification settings.” The cards are showing platform defaults rather than what you saved. Reload the page, and save only once the values on screen are the ones you expect.

Manage your profile: your own notification switches
Manage access: roles, invites, and removing members
Replay and troubleshoot webhook deliveries: what to do after deliveries are turned off