Configuring Notification Email

Key Takeaways

  • Use Test Address to redirect tenant template notifications during nonproduction testing.

  • Production template notifications ordinarily follow Intended Recipients and their triggering process.

  • Verify From separately from Reply-To and from the recipient routing for workflows or health alerts.

  • Treat an explicit external address as a data disclosure decision and prove delivery to the authorized destination.

Last updated: November 2026

Identify which process sends the message

SailPoint uses notification templates for events such as user registration, access work, certification and system health. Some processes have their own notification toggles. The documented Pending Task Daily Digest is an example that must be enabled. The template editor can modify the message subject and body using supported Apache Velocity values and conditionals. Reply-To determines where replies go. The triggering process supplies much of the data and helps determine whom the system intends to notify. Diagnose the trigger, the routing selection, and the receiving mailbox as separate stages.

Select the configuration that matches the communication path. In template settings, Intended Recipients uses the system recipients for that notification. Test Address redirects template notifications to the specified test address, and changing that address creates an audit event. A global test address in a live tenant redirects expected notifications until Intended Recipients is restored. This can affect approvals, registration or other business communication during the change. Check which setting the tenant actually uses when several types of notifications suddenly arrive in one inbox.

NeedAppropriate control and test
Keep staging messages away from real business usersSet Test Address and trigger a representative template notification for a synthetic identity
Render a changed templateUse its built-in test email for the layout and global variables, then exercise a real event on test data
Route infrastructure health alertsSelect qualifying components and approved recipients in System Notifications
Send a message as part of a workflow branchCheck the Send Email action's recipients, sender, runtime variables and branch result
Change how the organization appears as senderSelect a verified From address for the tenant or relevant brand and verify receiving policy
Direct replies to a monitored queueSet the applicable Reply-To and test a reply from an authorized mailbox

The template's built-in test can show global values. Process variables can be null and conditional sections can be omitted in that test. Trigger a real notice with approved synthetic data to exercise the relevant variables and conditional text. Use separately configured routing tests for other actions such as notifications sent through an external HTTP integration. Confirm that the test addresses and receiving destinations are controlled for each action selected, including those in a workflow test that actually execute.

Select a sender and trace delivery

The notification template From address is set globally for the tenant, or by brand if applicable. SailPoint documents Amazon Simple Email Service (SES) as its email provider. A sender address must be verified before use. Coordinate with mail and Domain Name System (DNS) administrators when using an organizational domain. DomainKeys Identified Mail (DKIM) domain verification can satisfy the documented DKIM path for Domain-based Message Authentication, Reporting and Conformance (DMARC). Sender Policy Framework (SPF) by itself is a different check. For the DMARC path using SPF alignment, SailPoint documents a verified custom MAIL FROM domain that matches the organization's email domain. Verify the actual received authentication results and quarantine records rather than assuming that a branded From address guarantees delivery.

A workflow's Send Email action has its own list of recipient addresses and can use a verified specified From address or the Branding setting by default. The System Notifications settings can explicitly send health alerts to email addresses with no SailPoint account association. Use approved destination addresses and scope what information is sent, especially for external recipients. For example, route a contractor-operated monitoring inbox only the necessary operational alerts, using a sanitized staging test first. Use the enterprise mail or workflow controls required by the organization for allowed destinations. Check To, From and Reply-To independently in the received message. A verified sender address establishes a sending configuration, while the authorized recipients remain a separate decision.

Work a missing message

If staging produces a test email but the notification triggered by a lifecycle event is missing, first inspect the event and process toggle, then the runtime identity data and redirect setting. Verify whether the event initiated the right template. At the mailbox, distinguish delivery failure from missing conditional content. If the actual message arrives but lacks the expected branch text, inspect the variable on the event and the template condition rather than replacing the mail sender. Retain the event time and test receipt together so the observation can be repeated.

See SailPoint's template settings and testing, sender authentication, health notification routing, and workflow actions.

Test Your Knowledge

A staging tenant contains work emails for real employees. The engineer needs to exercise process-generated template messages using one authorized test mailbox. What should they configure?

A

Set the template Reply-To to the test mailbox and leave recipient routing unchanged.

B

Change the brand From address to the test mailbox.

C

Run the template layout test as proof that all process routes are redirected.

D

Select Test Address under Email Templates settings and run a controlled event.

Test Your Knowledge

A template preview arrived, but its conditional text based on a lifecycle event is missing. What demonstrates whether that branch renders with live process input?

A

Reset the organization’s DKIM settings and rerun the same email preview.

B

Trigger the configured event with synthetic identity data and inspect the message delivered to the test address.

C

Use the mailbox reply to render the process fields before the event occurs.

D

Check whether the test address change created an audit event and assume the text is correct.

Sections you finish are checked off in the contents.