---
sourceDocument: Australia Governance, Risk, and Compliance
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/governance-risk-compliance

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Setup steps for emergency notification

# Setup steps for emergency notification {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Setting up the Emergency Notification feature requires you, as a BCM admin, to configure
certain pre-requisite data. The setup steps help you to establish a consistent connection with
Everbridge and a successful notification delivery workflow on the Everbridge side.  
These configurations are required to be set up for different users to use the Crisis Management workspace for sending an emergency notification and monitoring the notification workflow:

* To create a connection and authenticate your credentials with Everbridge, see [Create connection and authenticate credential with Everbridge](https://servicenow-prod.fluidtopics.net/tu3t_EhdmR~_0YlRxbA5dQ "As a first step, establish a connection and authenticate your login credentials with an Everbridge instance to send out a notification using a delivery channel. This connection not only helps you to send but also receive communications.").
* To get the delivery details of the contacts from Everbridge and use them to send notification, see [Import delivery channels from Everbridge](https://servicenow-prod.fluidtopics.net/g0SBa_yMTXSkKOICAK5CUg "After setting up the connection and credentials with Everbridge, you must import the delivery channels from Everbridge. Sending notifications is made easier through these delivery channels.").
* To get the details about the type of contacts from Everbridge, see [Import record types from Everbridge](https://servicenow-prod.fluidtopics.net/sqPhYjjJ1A7Hdk~VQrplpQ "Import the record types for your organization ID from Everbridge and use them to create contacts.").
* To pre-configure a notification template to send an email or SMS to your contacts, see [Define a template for emergency notification](https://servicenow-prod.fluidtopics.net/S2qzx2bSo3KDLgWCglkqhA "Create a template with pre-defined information that you can use to send notification quickly to your users in an emergency.").
* To create contacts for sending the notification, see [Create contacts for emergency notifications](https://servicenow-prod.fluidtopics.net/KcOneHvC6doOsmX1rDi8Kg "Use the ServiceNow users list to create contacts manually and synchronize the contacts with Everbridge to send emergency notifications.").
* To set up rules in filtering the contacts from the user table, see [Create contact import rules](https://servicenow-prod.fluidtopics.net/PxYgaPxsEAT0q5z3lylkag "Create a contact import rule to apply on the User table and filter out users as contacts for emergency notifications.").
* To create a group of contacts, see [Create a notification contact group](https://servicenow-prod.fluidtopics.net/T~v3htCXKvGnFB8DHVWBxA "Create a notification contact group using the ServiceNow AI Platform groups. Use the group members as contacts for emergency notification. Synchronize the group members as contacts with Everbridge and track the non-synchronized members as exceptions.").
{#setting-up-everbridge-emergency-notification__ul_cgp_tbh_spb}

Here is a flow diagram that shows how the different setup steps are connected for the
integration:  
Figure 1. Emergency notification setup flow