--- sourceDocument: Brazil Governance, Risk, and Compliance sourceDocumentLink: https://www.servicenow.com/docs/r/governance-risk-compliance Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Governance, Risk, and Compliance ft:clusterId : - grc bundleId : - grc workflow : - Technology --- # Email notifications in Operational Resilience # Email notifications in Operational Resilience {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Email notifications are sent by the Operational Resilience application at different points in the service impact analysis, importance and impact tolerance assessment, vulnerability, and scenario analysis lifecycle. ## Email notifications {#email-notifications-in-opres__section_email_notifications_opres} An admin can modify email notifications to change when to send it, who receives it, and what it contains. For more information, see [Create an email notification](https://www.servicenow.com/docs/access?context=t_CreateANotification&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US). The following tables describe the notifications, recipients, roles, and the associated conditions provisioned in the Operational Resilience application. Event-based notifications : Fire automatically off a registered system event when qualifying data changes.{#email-notifications-in-opres__table_event_based_notifications_opres__entry__2} | Notification and recipient | When sent | |-|-| | sn_oper_res.manager || | Email assigned_to Recipient: assigned_to (sn_oper_res_service_impact_analysis) | Service Impact Analysis is assigned | | Questionnaire assignment Recipient: assessor (sn_oper_res_importance_impact_tolerance_assessment) | State changes from Draft to Pending Response for legacy assessments with questionnaire template | | Adding participant Recipient: participant (sn_oper_res_m2m_analysis_participant) | Participant record is inserted or when re-notifying existing participants | | Vulnerability assignment Recipient: assigned_to (sn_oper_res_vulnerability) | assigned_to is set on vulnerability | | Vulnerability re-assignment Recipient: assigned_to (sn_oper_res_vulnerability) | assigned_to changes value | | Vulnerability approved/rejected Recipient: assigned_to (sn_oper_res_vulnerability) | State changes from Pending Approval to Approved, Treatment, or Assessment | | sn_oper_res.manager, sn_oper_res.admin | | | Assessment assignment Recipient: assigned_to (sn_oper_res_importance_impact_tolerance_assessment) | Importance and Impact Tolerance Assessment is first assigned | | Assessment re-assignment Recipient: assigned_to (sn_oper_res_importance_impact_tolerance_assessment) | assigned_to changes | | Assessment approved/rejected Recipient: assigned_to (sn_oper_res_importance_impact_tolerance_assessment) | State changes from Pending Approval to Approved or Analyze | | Assessment canceled Recipient: assigned_to, assessor, approver (sn_oper_res_importance_impact_tolerance_assessment) | State changes to Cancelled | | Smart Assessment assignment Recipient: assessor (sn_oper_res_importance_impact_tolerance_assessment) | Smart Assessment becomes ready (state is Pending Response and assessor changes or state changes from Draft) | | Assignment notification Recipient: assigned_to (sn_oper_res_scenario_analysis) | Scenario Analysis is first assigned | | Re-assigned notification Recipient: assigned_to (sn_oper_res_scenario_analysis) | assigned_to changes value and is not empty | | Approval/Reject notification Recipient: assigned_to (sn_oper_res_scenario_analysis) | State changes from Pending Plan Approval to Draft or Analyze | | Approval/Reject notification - Result Recipient: assigned_to (sn_oper_res_scenario_analysis) | State changes from Pending Result Approval to Approved or Analyze | | Canceled notification Recipient: assigned_to (sn_oper_res_scenario_analysis), participant (sn_oper_res_m2m_analysis_participant) | State changes to Cancelled | | Removing scenario event Recipient: participant or assigned_to (sn_oper_res_m2m_analysis_participant, sn_oper_res_scenario_analysis) | Participant is swapped, response task is cancelled or deleted, or scenario event link is deleted | | Sending response task Recipient: response task's participant (sn_oper_res_response_task) | Response task is inserted (typically when analysis state changes to Analyze) | | Receiving complete response task Recipient: assigned_to (sn_oper_res_scenario_analysis) | Response task state changes to Closed Complete | | sn_oper_res.manager, sn_oper_res.operational_resilience_business_user, sn_oper_res.admin || | Vulnerability canceled Recipient: assigned_to, opened_by, approvers, watch_list (sn_oper_res_vulnerability) | State changes to Cancelled | | Not gated by an Operational Resilience role anyone added to the case's watch list or set as analyst receives it. || | DRI Source Record Change - Email Notification Recipient: watch_list, analyst (sn_grc_inc_rptg_case_task) | Tracked field changes on an incident linked to a DRIR case (beginning with version 23.0.4). A banner also displays on the case. | [ ] {#email-notifications-in-opres__table_event_based_notifications_opres} Workflow-driven notifications : None. Operational Resilience has five Flow Designer flows for approvals (Scenario Analysis Plan Approval, Scenario Analysis Result Approval, Vulnerability approval, and Importance and Impact Tolerance Assessment Approval). All five use the built-in Ask For Approval action rather than an app-owned Send Email step. They rely on the platform's Approval Requested, Approved, and Rejected notifications instead. Ad-hoc notifications : Started manually by a user, not fired automatically by any record condition. : {#email-notifications-in-opres__table_adhoc_notifications_opres__entry__4} | Notification | Description | Recipient | Roles | |-|-|-|-| | Smart Assessment contributors added | Sent when contributors are manually added to a Smart Assessment in the UI. | Contributors added by the user | Governed by Smart Assessment Engine contributor-management access For Digital resilience incident reporting assessments, see [Roles installed with Digital resilience incident reporting](https://www.servicenow.com/docs/yTyU15gymTUOaFZGiLnPMQ "Certain roles are installed with the Digital resilience incident reporting functionality."). | | Smart Assessment reassignment | Sent when a contributor is manually reassigned in the Smart Assessment UI. | Newly assigned contributor | Governed by Smart Assessment Engine contributor-management access | [ ] {#email-notifications-in-opres__table_adhoc_notifications_opres} ## Example: DRI Source Record Change notification {#email-notifications-in-opres__section_dri_source_record_change_example} The following example shows a generated "DRI Source Record Change - Email Notification," sent after tracked fields changed on the incident linked to a DRIR case. Subject: DRIR Case DRI0001014: Source Record Updated Body: The source record linked to your DRIR case has been updated., followed by the case number, the source record number, who made the change and when, and each changed field with its old and new value. The email includes a link to view the case, but not a link to the source record itself. The underlying notification record shows the same subject, recipients (the case's watch list and analyst, listed as individual email addresses), and body content.