Notifications send emails to the right people when something happens in ServiceNow. This guide walks you through setting up recipients so your emails reach exactly who they should without duplicates or missing people.
What manual email routing looks like
Before notifications, teams handled updates manually — copying people on emails, maintaining distribution lists that went stale, or worse, forgetting to notify the right stakeholders when critical records changed. The people who suffered were end users waiting for updates, managers missing escalations, and IT staff playing email tag to figure out who owns what. Notifications replace that manual coordination by automatically sending structured emails when ServiceNow records change state.
How recipient configuration works
A notification's recipient configuration has three layers: static recipients (specific users, groups, or roles you pick), field-based recipients (pulled from the record itself like assigned_to or opened_by), and exclusions (to remove duplicates). Most notifications start with field-based recipients — send to whoever owns the record. Then you layer on static recipients for stakeholders who always need to know. The Exclude field prevents the same person from getting multiple copies when they appear in several recipient categories.
Production-quality recipient targeting
Basic notifications work with assigned_to and maybe a group. Production notifications get more surgical: watch lists for people following specific records, role-based targeting for escalations, and careful exclusion rules to prevent email fatigue. The difference between amateur and professional notification design is precision — sending exactly the right information to exactly the right people, not blasting everyone who might care.
Before you start
- •notification_admin or admin role
- •Existing notification record to configure
Sourdough: ServiceNow Monitoring and Analytics
A Chrome extension for ServiceNow Admins and Developers with essential tools, analytics, graphs and monitoring features.
Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.
Step by step
Open the notification recipient section
Navigate to System Notification > Email > Notifications and open your notification record. Scroll to the 'Who will receive' section. You'll see tabs for Users, Groups, and Roles, plus fields for Recipients, Exclude, and checkboxes for advanced options. This section controls every email address that gets a copy.
The recipient tabs are additive — people in Users AND Groups AND Roles all get the email unless you exclude them.
Configure field-based recipients
In the Recipients field, enter field names from your table that contain user references — typically assigned_to, opened_by, caller_id, or watch_list. Separate multiple fields with commas. ServiceNow pulls the actual users from these fields when the notification fires. For incident notifications, start with 'assigned_to,opened_by' to cover the owner and requester.
Use watch_list to include people who explicitly subscribed to updates on that record.
Add static user recipients
Click the Users tab and use the reference picker to add specific users who always need this notification. These are stakeholders who care regardless of who owns the record — maybe a manager, a service owner, or a coordinator. Don't add users here if they're already covered by the Recipients field or they'll get duplicates.
Add group recipients
Click the Groups tab and select groups whose members should receive the notification. Common choices are assignment groups, management groups, or specialized teams like security or compliance. Every active member of selected groups gets the email. Use this for broad stakeholder notification, not operational updates.
Configure role-based recipients
Click the Roles tab and select roles if you need to notify everyone with specific permissions regardless of group membership. This is typically used for executive notifications or compliance alerts where you need to reach all users with admin, itil, or custom roles. Role-based targeting casts a wide net — use sparingly.
Set exclusions and event creator handling
In the Exclude field, enter user reference fields for people who shouldn't get the email — commonly 'sys_updated_by' to exclude whoever just modified the record. Check 'Send to event creator' if the person who triggered the notification should receive it regardless of other settings. Save the notification record.
Test recipient resolution
Find a record that would trigger your notification and note who should receive emails based on your configuration. Create a test event or modify the record to fire the notification. Check System Logs > Email to see which addresses received the notification and verify it matches your expectations.
Best practices
Always use the Exclude field to remove sys_updated_by from operational notifications — people don't need emails about changes they just made.
Favor field-based recipients over static ones for operational notifications — assigned_to scales better than hardcoded user lists that go stale.
Use watch_list for notifications where people opt in to updates rather than getting them automatically.
Test notifications with records that have overlapping recipients (same person in multiple groups) to verify your exclusion logic works.
Avoid role-based recipients for high-volume notifications — roles like admin or itil can include hundreds of users who don't need operational updates.
Test Your Knowledge
Quick 3-question quiz — see how your ServiceNow skills stack up.
A list view on a table with millions of records is slow. Best fix?
Select an answer to continue