--- title: "Create and Manage Notification Rules" slug: "create-and-manage-notification-rules" updated: 2026-11-16T07:10:28Z published: 2026-11-16T07:10:28Z canonical: "docs.powerworker.com/create-and-manage-notification-rules" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.powerworker.com/llms.txt > Use this file to discover all available pages before exploring further. # Create and Manage Notification Rules Notification Rules allow administrators to automatically create notifications when defined events occur in Dataverse. A Notification Rule defines **what to monitor, when the rule should run, who should receive the notification, and what information the notification should contain**. ## Prerequisites You require the **vNudge - Admin** security role to create and manage Notification Rules. ## Create a Notification Rule 1. Open the vNudge application. 2. Navigate to **Notification Rules**. 3. Create a new Notification Rule. New rules are created with a status of **Draft**. ![](https://cdn.document360.io/7abff6c0-4eeb-4bb0-a6a4-8718bf640435/Images/Documentation/image(879).png) 4. Under **Entity & watched fields**, select the **Target Entity** that you want the rule to monitor. 5. Select the required **Watched Attributes**. Watched Attributes identify the fields that vNudge monitors for the Notification Rule. 6. Under **Trigger & channel**, select a **Trigger Type**. | Trigger Type | Description | | --- | --- | | **Create** | Evaluates the rule when a new record is created. | | **Change** | Evaluates the rule when a watched attribute changes. | > [!WARNING] > **Important** > > For a **Change** rule, select at least one Watched Attribute. The rule is evaluated when one or more of the selected attributes changes. 1. Select a **Delivery Channel** if notifications generated by the rule must use a specific delivery channel. Select **Use recipient preference** if the recipient's active Notification Preference should determine how the notification is delivered. If the recipient does not have an active Notification Preference and no specific delivery channel is provided, vNudge uses **Email**. 2. Under **Conditions**, add any conditions required to further control when the rule generates notifications. Conditions use **AND** logic. When multiple conditions are configured, all conditions must be satisfied for the rule to proceed. 3. Under **Recipients**, add one or more recipients. | Recipient Type | Description | | --- | --- | | **Static** | Sends the notification to a specific Dataverse system user. | | **Lookup** | Determines the recipient using information from the record that triggered the rule. | Use a **Static** recipient when the same user should always receive the notification. Use a **Lookup** recipient when the recipient depends on the record that triggered the rule. For example, the recipient could be the owner of the record. Lookup recipient paths can contain up to **two lookup hops** and must ultimately resolve to a Dataverse system user. > [!WARNING] > **Important** > > Notification recipients must be Dataverse system users. If none of the configured Lookup recipients resolves to a system user, vNudge skips the rule and no notification is created. 1. Under **Message**, enter the notification **Subject Template** and **Body Template**. Notification content can include supported values from: Use the token insertion functionality in the Rule Editor to add supported values to the Subject or Body. - The Dataverse record that triggered the rule. - The resolved recipient's user record. 2. Save the Notification Rule. 3. Review the rule configuration. 4. When the rule is ready to use, **activate the rule**. A rule that has not successfully activated is not monitoring its configured Dataverse event.