---
title: "vNudge Overview"
slug: "vnotificationhub-overview"
updated: 2026-09-06T13:23:59Z
published: 2026-09-06T13:23:59Z
canonical: "docs.powerworker.com/vnotificationhub-overview"
---

> ## 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.

# vNudge Overview

Notification Hub us a **centralised notification service** for Dataverse and Power Platform.

Notification Hub routes delivery across **Email, Teams and In-App channels**, gives every user control over how they’re notified and gives administrators a live picture of whether the system itself is healthy.

![](https://cdn.document360.io/7abff6c0-4eeb-4bb0-a6a4-8718bf640435/Images/Documentation/NotificationHub.png)

### Key Features of Notification Hub

- **One Entry Point -** call the Send Notification action from a plug-in, a flow or the Web API and NotificationHub takes care of delivery, retries and status tracking
- **User controlled delivery -** every recipient can choose their preferred channel, a fallback order, an alternate email address, and whether they want to be notified at all.
- **Built-in observability -** a monitoring dashboard shows delivery health and the health of NotificationHub’s components.

## Glossary

| Term | Meaning |
| --- | --- |
| **Notification** | One message travelling through the system: a recipient, a channel, a subject/body and a status. |
| **Channel** | The delivery method for a notification: Email, Teams or In-App |
| **Component** | One of the seven first-party NotificationHub processes that can independently succeed or fail on a given run: Router, Email Adapter, Teams Adapter, In-app Adapter, Send Notifications API, Rule Activation, Rule Evaluator |
| **Component Status** | A single, current-state row per Component (last outcome, last success/failure timestamps, last failure message), overwritten on every run- not a history. |
| **Notification Rule** | An administrator-defined subscription: “when *this* happens on *this* entity, notify *these* people” |
| **Trigger Type** | What causes a rule to fire: **Change** (a watched attribute is updated) or **Create** (a new record is created). |
| **Channel Priority** | A user’s own fallback order between channels (e.g. Teams, Email), used when no explicit channel is specified and the first channel fails. |
| **License** | The organisation-wide Velrada product entitlement for Notification Hub |
| **Blocked (notification status)** | Terminal status applied when a notification would otherwise be dispatched but the organisation’s License is invalid. Distinct from Failed - never retried and counted separately form genuine delivery failures. |