--- title: Configuring flows in DaVinci description: After you configure PingOne, perform additional configuration in PingOne DaVinci to enable all features and make the flows available to end users. component: pingone-solutions page_id: pingone-solutions:frontline-workers:getting-started/frontline-configuring-flows-in-davinci canonical_url: https://docs.pingidentity.com/pingone-solutions/frontline-workers/getting-started/frontline-configuring-flows-in-davinci.html llms_txt: https://docs.pingidentity.com/pingone-solutions/llms.txt docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md revdate: 2026-08-14 section_ids: steps: Steps choose-from: Choose from: result: Result: result-2: Result: choose-from-2: Choose from: --- # Configuring flows in DaVinci After you configure PingOne, perform additional configuration in PingOne DaVinci to enable all features and make the flows available to end users. ## Steps 1. Import the solution into your initial environment: 1. In your production DaVinci environment, click **Flows**. 2. Click **Add Flow > Import from JSON**. 3. Select the JSON file containing the flows. 4. Click **Import**. 2. Configure DaVinci applications that invoke the **Frontline Worker - Registration, Authentication and Account Recovery with ID Verification and Recognize - Main Flow** and **Frontline Worker - Remote User Registration**. Learn more in [Creating an application](https://docs.pingidentity.com/davinci/applications/davinci_creating_an_application.html) and [Configuring a flow policy](https://docs.pingidentity.com/davinci/applications/davinci_configuring_a_flow_policy.html) in the DaVinci documentation. 1. On the **Applications** tab, click **Add Application**. 2. In the **Name** field, enter a name for the application. 3. Click **Create**. 4. On the **Applications** tab, find the application that you created and click **Edit**. 5. On the **Flow Policy** tab, click **Add Flow Policy**. 6. In the **Name** field, enter a name for the flow policy. 7. Select **PingOne Flow Policy** if you plan to invoke the flow using a PingOne redirect. 8. In the **Flows** section, select the **Frontline Worker - Registration, Authentication and Account Recovery with ID Verification and Recognize - Main Flow**. 9. In the **Version** section, select one or more versions of the flow to use. 10. Click **Create Flow Policy**. 11. In the **Distribution** field, set the weight for the selected flow to `100`. 12. Click **Save Flow Policy**. 13. Click **Apply**. 14. Repeat steps a - m for the **Frontline Worker - Remote User Registration**. 3. Enter or verify the values for each company variable that's used in the Verified Frontline Workers flow pack solution. These variables determine whether some processes and subflows are included or excluded. 1. Click the **Variables** tab. 2. Locate a variable and click the **Pencil** icon. 3. In the **Value** field, verify that the value is correct or enter a new value for the variable. 4. Click **Update**. 5. Repeat steps b - d for each remaining variable. > **Collapse: Company variables** > > | Variable | Description | > | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | > | `frontline_companyName` | The name of your company as it should be displayed in user-facing text. | > | `frontline_remoteRegistrationRetryLimit` | The maximum number of times a user can retry remote registration if retries are enabled. | > | `frontline_isRetryRemoteRegistrationEnabled` | A Boolean that indicates whether a user can retry remote registration. | > | `frontline_superviserAuthnRetryLimit` | The maximum number of times a user can attempt to authenticate as a supervisor. | > | `frontline_workerAuthnRetryLimit` | The maximum number of times a user can attempt to authenticate as a worker. | > | `frontline_threatDetectionRequired` | A Boolean that indicates whether threat detection through PingOne Protect is required. | > | `frontline_supportEmail` | An email address user should use for support. This can be included in email templates. | > | `frontline_envDomain` | The PingOne regional domain for this environment. This is userd to construct the correct PingOne endpoints. Valid values for each region are:- North America (excluding Canada) (NA): **pingone.com** > > - Canada (CA): **pingone.ca** > > - European Union (EU): **pingone.eu** > > - Australia (AU): **pingone.com.au** > > - Singapore (SG): **pingone.sg** > > - Asia-Pacific (AP): **pingone.asia** | > | `frontline_helpdeskEmail` | The destination email for support requests. | 4. Verify the configuration of the following connectors in your environment: | Connector | Description | Connector documentation | | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------- | | PingOne | Enables DaVinci to view and update PingOne user information. | [PingOne connector](https://docs.pingidentity.com/connectors/p1_connector.html) | | PingOne Notifications | Enables DaVinci flows to send users general communications using SMS, email, and voice message with PingOne's notifications feature. | [PingOne Notifications connector](https://docs.pingidentity.com/connectors/p1_notifications_connector.html) | | OIDC and OAuth IdP | Enables users to authenticate with an Identity Provider (IdP). | [OIDC and OAuth IdP connector](https://docs.pingidentity.com/connectors/oidc_oauth_idp_connector.html) | 1. On the **Connectors** tab, find the connector that you want to verify and go to **…​ > Edit**. 2. Verify that the **Environment ID**, **Client ID**, and **Region** field values match your PingOne values. 3. (Optional) Copy the **Client Secret** from your PingOne environment to the **Client Secret** field. 4. For the PingOne Authorize connector, verify that the **Endpoint** matches the one found in PingOne in the **Authorization > Decision Endpoints** section. 5. If you made changes to the values, click **Apply**. 6. Repeat the previous steps for each remaining connector. 5. Configure the **Frontline Worker - Registration, Authentication and Account Recovery with ID Verification and Recognize - Main Flow**: 1. Click **Flows**. 2. Select the **Frontline Worker - Registration, Authentication and Account Recovery with ID Verification and Recognize - Main Flow** and go to **…​ > Edit**. 3. Click the **Initialize Or Set Flow Variables** node and set values for the following variables: > **Collapse: Variables** > > | Variable | Description | > | ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | > | `protectRiskEvalId` | The ID of the PingOne risk policy you created in the previous procedure. | > | `p1OnSiteRegistrationVerifyPolicyId` | The ID of the PingOne Verify policy you created for the **Frontline Worker - Registration, Authentication and Account Recovery with ID Verification and Recognize - Main Flow** in the previous procedure. | > | `supervisorsPopulationId` | The supervisors population ID. | > | `workersPopulationId` | The workers' population ID. | > | `workerAppClientId` | The client ID for the worker app. | > | `workerAppClientSecret` | The client secret for the worker app. | > | `onboardingWorkersPopulationId` | The currently onboarding workers' population ID. | > | `remoteInviteNotificationTemplateName` | The name of the notification template to use for remote invites. | > | `remoteInviteFlowLink` | The flow policy link for the Frontline Worker - Remote User Registration to use for remote invites. | > | `inviteLinkTTL (in seconds)` | The amount of time for which an invite should be active before it times out. | > | `p1AgreementId` | The ID of the agreement to use if your environment requires user agreement. | > | `helpdeskRequestNotificationTemplateName` | The name of the notification template to use for help desk requests. | 4. Click **Save**. 6. Configure the **Frontline Worker - Remote User Registration**: 1. Click **Flows**. 2. Select the **Frontline Worker - Remote User Registration** and go to **…​ > Edit**. 3. Click the **Initialize Or Set Flow Variables** node and set values for the following variables: > **Collapse: Variables** > > | Variable | Description | > | --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | > | `welcomeNotificationTemplateName` | The name to display for the welcome notification. | > | `p1VerifyPolicyId` | The ID of the PingOne Verify policy you created for the **Frontline Worker - Remote User Registration** in the previous procedure. | > | `workersPopulationId` | The workers' population ID. | > | `p1AgreementId` | The ID of the agreement to use if your environment requires user agreement. | 4. Click **Save**. 7. Verify that the PingOne flow setting is correct for your environment. ### Choose from: * If you want to launch the Verified Frontline Workers flow pack solution using a redirect, the flow must be configured as a PingOne flow. * If you want to launch the Verified Frontline Workers flow pack solution using the widget, the flow must not be configured as a PingOne flow. 1. Click **Flows**. 2. Click the **Frontline Worker - Registration, Authentication and Account Recovery with ID Verification and Recognize - Main Flow**. 3. Go to **[icon: ellipsis-v, set=fa]> Flow Settings**. 4. If you plan to launch the flow through a redirect, click the **PingOne Flow** toggle. 5. If you made changes to the flow settings, click **Save**, close the flow settings pane, and click **Deploy**. 8. If you're using a test environment, move the flows to your production environment: 1. In your testing environment, click **Flows**. 2. Click the **Frontline Worker - Registration, Authentication and Account Recovery with ID Verification and Recognize - Main Flow** flow. 3. Go to **[icon: ellipsis-v, set=fa]> Download Flow JSON**. ### Result: The **Export Flow** panel opens. 4. Click **Yes**. ### Result: The flow and its subflows are downloaded locally. 5. Sign on to your production environment and click **Flows**. 6. Click **Add Flow > Import from JSON**. 7. Select the JSON file containing the flows. 8. Click **Import**. 9. Repeat steps a-h for the **Frontline Worker - Remote User Registration**. 10. Repeat the previous steps in your production environment. 9. Invoke the flow or flows using the widget or a redirect. ### Choose from: * If you want to launch the flow in a separate window using a PingOne redirect, use the procedure in [Launching a PingOne flow with a redirect](https://docs.pingidentity.com/davinci/integrating_flows_into_applications/davinci_launch_flow_redirect.html) in the DaVinci documentation. The Frontline Worker - Registration, Authentication and Account Recovery with ID Verification and Recognize - Main Flow flow can be launched with a redirect. * If you want to launch the flow in a widget within the user's current window, use the procedure in [Launching a flow with the widget](https://docs.pingidentity.com/davinci/integrating_flows_into_applications/davinci_launching_a_flow_with_the_widget.html) in the DaVinci documentation. The **Frontline Worker - Registration, Authentication and Account Recovery with ID Verification and Recognize - Main Flow** can be launched with the widget.