{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":16818,"path":"governance-risk-compliance/email-notifications-in-bcm.md","title":"Email notifications in Business Continuity Management","bundle":null,"doc_type":null,"release":"australia","body":"\n# Email notifications in Business Continuity Management\n\nEmail notifications are sent by the Business Continuity Management \\(BCM\\) application at different points in the Business Impact Analysis, planning, exercise, and crisis management lifecycle.\n\n## Email notifications\n\nAn 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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/t_CreateANotification.md).\n\nThe following tables describe the notifications, recipients, roles, and the associated conditions provisioned in the BCM application.\n\n-   **Event-based notifications**\n\n    Trigger automatically off a registered system event when qualifying data changes.\n\n<table id=\"table_event_based_notifications_bcm\"><thead><tr><th>\n\nPurpose\n\n</th><th>\n\nTriggering conditions\n\n</th><th>\n\nRecipient and roles\n\n</th></tr></thead><tbody><tr><td colspan=\"3\">\n\nNotify BIA Updated\n\n</td></tr><tr><td>\n\nNotifies plan stakeholders of BIA changes.\n\n</td><td>\n\nA Business Impact Analysis record is updated.The system finds every plan that uses that BIA as a primary-scope asset and triggers once per matching plan.\n\n</td><td>\n\nRecipient: plan\\_owner \\(sn\\_bcp\\_plan\\)Roles: sn\\_bcp.plan\\_manager \\(can set or change plan\\_owner\\), sn\\_bcp.plan\\_admin \\(can also write plan\\_owner while the plan is in Draft, Review, or Returned state\\)\n\n</td></tr><tr><td colspan=\"3\">\n\nBIA Dependency Update Notification\n\n</td></tr><tr><td>\n\nNotifies reviewers of BIA dependency changes.\n\n</td><td>\n\nTriggers from the same BIA-update chain, routed through the shared DependencyUpdateContextBase helper.Condition: The matching sn\\_bia\\_dependency\\_update\\_config record has Send notification enabled.\n\n</td><td>\n\nRecipient: User or group fields listed in the User fields property of the matching sn\\_bia\\_dependency\\_update\\_config record, resolved per snapshot.Roles depend on which field the config points to. Plan owner: sn\\_bcp.plan\\_manager, sn\\_bcp.plan\\_admin. sn\\_bia\\_analysis.bcm\\_lead: sn\\_bia.bia\\_manager or sn\\_bia.bia\\_planner \\(BIA in Draft\\), sn\\_bia.bia\\_admin \\(BIA in Draft or Review\\).\n\n</td></tr><tr><td colspan=\"3\">\n\nBCP Dependency Update Notification\n\n</td></tr><tr><td>\n\nNotifies reviewers of plan dependency changes.\n\n</td><td>\n\nSame mechanism as the BIA Dependency Update Notification.Condition: The matching sn\\_bcp\\_dependency\\_update\\_config record has Send notification enabled, triggered on the plan rather than the BIA.\n\n</td><td>\n\nRecipient: User or group fields listed in the matching sn\\_bcp\\_dependency\\_update\\_config record's User fields property, resolved like the BIA Dependency Update Notification.Roles depend on which field the config points to. sn\\_bcp\\_plan.plan\\_owner: sn\\_bcp.plan\\_manager, sn\\_bcp.plan\\_admin. sn\\_bcp\\_plan.bcm\\_lead: sn\\_bcp.plan\\_contributor or sn\\_bcp.plan\\_manager \\(plan in Draft\\), sn\\_bcp.plan\\_admin \\(plan in Draft or Review\\).\n\n</td></tr></tbody>\n</table>-   **Workflow-driven notifications**\n\n    Trigger directly from a record update condition or a Flow Designer state change, with no separate event registration involved.\n\n<table id=\"table_workflow_driven_notifications_bcm\"><thead><tr><th>\n\nNotification\n\n</th><th>\n\nPurpose and triggering conditions\n\n</th><th>\n\nRecipient and roles\n\n</th></tr></thead><tbody><tr><td>\n\nNotification for subscribed alert\n\n</td><td>\n\nNotifies people watching a crisis or threat alert that it changed.Triggered when an alert record is updated while it has one or more people on its watch list.\n\n</td><td>\n\nRecipient: watch\\_list \\(sn\\_fam\\_alert\\)Roles: None. watch\\_list carries no field-level ACL; any user with access to the alert record can add themselves or others as a watcher.\n\n</td></tr><tr><td>\n\nSend action email when an event task fails\n\n</td><td>\n\nInforms the task owner that their recovery event task failed.Triggered when an Event Task's state field changes to value 9 while it has an assigned owner.\n\nFlow Designer trigger condition: `state CHANGES TO assigned_to IS NOT EMPTY` on sn\\_recovery\\_event\\_task.\n\n</td><td>\n\nRecipient: assigned\\_to \\(sn\\_recovery\\_event\\_task\\)Roles: sn\\_recovery.event\\_user \\(write access while the task is open or pending\\), sn\\_recovery.event\\_manager \\(write access whenever the user can edit the parent record\\)\n\n</td></tr></tbody>\n</table>-   **Ad-hoc notifications**\n\n    Started manually by a user, not triggered automatically by any record condition.\n\n<table id=\"table_adhoc_notifications_bcm\"><thead><tr><th>\n\nNotification\n\n</th><th>\n\nPurpose\n\n</th><th>\n\nTriggering conditions\n\n</th><th>\n\nRecipient and roles\n\n</th></tr></thead><tbody><tr><td>\n\nBCM Crisis Map Notification \\(\"Notify Stakeholders\"\\)\n\n</td><td>\n\nSends an alert notification to stakeholders during a crisis.\n\n</td><td>\n\nA user manually runs the Notify Stakeholders action on a Crisis Map alert \\(sn\\_fam\\_alert\\).There is no automatic condition on this action.\n\n</td><td>\n\nRecipient: Not a stored field. Recipients are computed at send time: either the specific users the sender picks, or contacts pulled from whichever resource records are marked as impacted.Roles: None. There is no role restriction on who can trigger the action; recipients are computed dynamically rather than role-gated.\n\n</td></tr></tbody>\n</table>\n**Parent Topic:**[BCM reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/bcm-reference.md)\n\n"}}