---
sourceDocument: Australia Impact
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/impact

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Configure notifications in IO

# Configure notifications in IO {#ariaid-title1}

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

Configure notifications and alerts to monitor your Instance Observer instance and receive alerts when specified conditions are met.

## Before you begin

Role required: admin

## About this task

Use this procedure to set up self-serve alerts that notify you when specific conditions occur on your Instance Observer instance. By configuring notification rules and alert criteria, you can monitor instance health
proactively and ensure that the right people receive alerts through their preferred channels. The configuration process takes approximately 10-15 minutes.

## Procedure

1. Navigate to AllImpactPlatform HealthMonitor.
2. Log in to Instance Observer and navigate to AlertsConfiguration Notification.  
   This tab displays how many notification rules you have and also allows you to create notification rules. These rules notify you when an alert is triggered, determine who receives alerts, and through which communication channels.
3. Select Create Rule to create a notification rule.
4. On the form, fill in the fields.  
   {#io-self-serve-alerts-vid-tut__table_zlm_fvk_vjc__entry__2}

   | Field | Description |
   |-|-|
   | Name | Descriptive name for the notification rule. For example, Database Performance Alerts or Critical Instance Issues. |
   | Description | Description explaining when this notification rule triggers and who should receive the alerts. |
   | Notification Type | Notification channel for the notification type. * Advanced customers can receive Email notification only. * Total customers can receive Email, SMS, ServiceNow, and third-party notifications. {#io-self-serve-alerts-vid-tut__ul_dtl_rvk_vjc} Your available options depend on your impact tier. For more information, see Impact Benefits page in the Impact Portal. |
   | All provisioned users | Option for all users who have access to Instance Observer to be notified when the alert triggers. |
   | ServiceNow Otto for SAM | Option to be notified ifServiceNow Otto for SAM is affiliated with your account. |
   | Add customer recipients | Option to enter custom email addresses for email notification. |
   | SMS | SMS to All provisioned users and Specific Users. If you select specific users, you can add their telephone numbers. |
   | ServiceNow | Option to utilize the ServiceNow implementation webhook to initiate a workflow on a specific instance. |
   | Webhook | Option to integrate Instance Observer with a third-party monitoring tool. |
   [Table 1. Configure Notification Rule form]

   {#io-self-serve-alerts-vid-tut__table_zlm_fvk_vjc}You can add multiple notification alerts which can be set as enabled default, or turned off entirely.  
   Note:  
   You must configure a notification first otherwise you won't be able to create an alert. For alerts must be tied to a notification.

## What to do next

[Set notifications for configured key alerts](https://servicenow-prod.fluidtopics.net/ZZj9Gh09se0NF_YM_IlWIQ "Follow these steps to configure Key Alerts on an instance where critical alerts have not yet been configured.")

*[\>]: and then