---
sourceDocument: Xanadu ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/platform-administration

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Create and update a provider notification for all users

# Create and update a provider notification for all users {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Create a notification in the notification provider framework to send to both sys and non-sys users.

## Before you begin

Role required: notifications provider admin and admin

## Procedure

1. Navigate to AllSystem NotificationProviderNotifications.
2. Select New to create a notification.
3. On the form, fill in the fields.  
   {#noti-new-update-notification__table_lb2_gbs_lpb__entry__2}

   | Fields | Description |
   |-|-|
   | Name | Name of the notification. |
   | Application | Scope of the notification record. |
   | Category | Select the category to which this notification belongs. A category identifies and groups related notifications. This notification, if active and listed in the selected Category in the notification preferences for each user (Notifications tab in the System Settings window. |
   | Active | Option to activate the notification. |
   | Triggered By | Trigger used in the notification record. Note: The options in this field depend on the selected table. For example, if you select an incident table, the options are Events or Record Change. |
   | Table | The table name on which the notification is triggered. |
   | Inserted | Condition to trigger the notification. |
   | Updated | Condition to trigger the notification. |
   | Event | Event that triggers the notification. For example, to send a notification after an incident is closed or resolved, you would select the incident.inactive event. By default, this event is logged in the system each time an incident is resolved or closed. Note: You can select only an event that shares the same table as the notification. This field appears when you select Event in the Triggered By field. |
   | Conditions | Additional conditions to trigger the notification. |
   | Users | Names of the available sys users. |
   | Recipients in fields | Field in the currently selected table that contains the users who receive an email notification. Note: The Recipients in fields field under Recipients enables you to choose both sys and non-sys users to whom you can send notifications. |
   | Is the originating user included? | Option to include the originating user to be included in the notification. |
   | Event Parm1 contains recipient(s)? | Option to select if Parm 1 contains a list of comma-separated sys_ids. |
   | Event Parm2 contains recipient(s)? | Option to select if Parm 2 contains a list of comma-separated sys_ids. |
   | Resolve Parm1 recipients from table | Table that is used to resolve the sys_id of a Parm 1 recipient. Note: This field appears only when you select Event Parm 1. |
   | Resolve Parm2 recipients from table | Table that is used to resolve the sys_id of a Parm 2 recipient. Note: This field appears only when you select Event Parm 2. |
   | Advanced event condition | Option to select when the recipients are from more than 2 tables. These options are dynamic conditions. |
   [Table 1. Notification form]

   {#noti-new-update-notification__table_lb2_gbs_lpb}
4. Select Submit.
5. Open the recently created notification.
6. Update the form using any of the available related lists.  
   See [Create and add additional recipients](https://servicenow-prod.fluidtopics.net/QaWg2u~jelp4aRfH7XRTYw "Update the notifications form by adding additional recipients from the Additional Recipients related list to send notifications to.") for more information.  
   Note:  
   All the validation messages given by different providers are retained. Warning messages of one provider isn't overridden by warning messages of another provider.
* **[Create and add additional recipients](https://servicenow-prod.fluidtopics.net/QaWg2u~jelp4aRfH7XRTYw)**   
  Update the notifications form by adding additional recipients from the Additional Recipients related list to send notifications to.

*[\>]: and then