--- title: "Post-Deployment Configuration" slug: "getting-started-1" updated: 2026-11-16T07:08:42Z published: 2026-11-16T07:08:42Z canonical: "docs.powerworker.com/getting-started-1" --- > ## 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. # Post-Deployment Configuration ## Configure Connection References Configure each vNudge connection reference with the appropriate licensed service account or shared credential. | Connection | Purpose | | --- | --- | | **Dataverse** | Provides access to vNudge notification and configuration data in Dataverse. | | **Office 365 Outlook** | Supports Email notification delivery. | | **Microsoft Teams** | Supports Microsoft Teams notification delivery. | Configure the following connection references: `velnotif_shareddataverse_NotificationHub` `velnotif_sharedoffice365_NotificationHub` `velnotif_sharedmicrosoftteams_NotificationHub` > [!WARNING] > **Important** > > Ensure that the account associated with each connection reference is valid, appropriately licensed, and has the permissions required for its purpose. ## Enable vNudge Flows Confirm that the following flows are deployed and enabled: - **Notification Router** - **Email Adapter** - **Teams Adapter** - **In-App Adapter** - **Notification Component Status Writer** child flow The Notification Router processes pending notifications and routes them to the appropriate delivery adapter. The Notification Component Status Writer supports the component-health information displayed on the Monitoring dashboard. ## Assign Security Roles vNudge includes three security roles for different user and application requirements. | Role | Description | | --- | --- | | vNudge - User | For users who receive notifications, view their own notifications, and manage their own Notification Preferences. | | vNudge - Sender | For sending applications, service accounts, and plug-in service accounts. Does not provide access to the model-driven application. | | vNudge - Admin | For IT and platform administrators who manage Notification Rules and monitor vNudge. | Security roles are additive and should be assigned according to the user's responsibilities. ## Configure Application Access Ensure that the vNudge model-driven application is shared with: - **Notification Hub - User** - **Notification Hub - Admin** Table privileges alone do not make the model-driven application available to users. The account used by the Notification Router’s Dataverse connection reference must have the **Notification Hub - Sender** role or higher. After changing security roles or application sharing, start a new sign-in session and confirm that User and Admin personas can open the application.