Credential Risk Detection, AI Phishing Alerts, and Credential Risk Alerts are available to organizations with Credential Protection.

If you have Credential Protection and are deploying the Dashlane browser extension, you can deploy the Credential Protection features at the same time:

• Credential Risk Detection
• AI Phishing Alerts
• Credential Risk Alerts

This deployment is consolidated into a single policy-driven registry update. The XML configuration templates downloaded from your Dashlane Admin Console contain all necessary parameters, including the policy configurations and the registry keys that silently deploy the browser extensions.

This eliminates the need to manually download and import browser administrative templates (ADMX/ADML files) or configure manual force-install GPO settings.

Although Credential Protection features are most beneficial when rolled out to your entire organization, you can start with a smaller group (or just yourself) during setup and extend it to more employees anytime. To add more employees, update the groups included in your policy deployment.

Add employees to the policy

Process overview

Estimated time to complete: 10 minutes

Prerequisites

Make sure you have the appropriate access needed to set up Credential Protection features:

• Admin access to a Dashlane account with Credential Protection
• Admin access to Group Policy Management (GPO) on a domain-joined Windows Server.
• Permissions to deploy policies to target devices.

Set up Credential Protection features on Windows using Group Policy (GPO)

One-step deployment

In the Dashlane Admin Console, start the setup:

1. Log in to the Dashlane browser extension and open the Admin Console
2. Under Integrations, select Deployment.

3. On the Deployment page, select Start setup.

   

4. On the Setup page, select Try Beta to see the policy deployment guide.

   

5. Select the GPO option and the browsers you're deploying to. Ensure your selection is accurate before downloading the XML files.

   

6. Select Download. Your device automatically downloads all XML files. After the file downloads, open Group Policy Management.

   This download contains both your organization's configuration keys (e.g., mass deployment tokens, username mapping) and the silent browser extension deployment keys (client_deploy/silent_deploy).

Configure the GPO Registry Preferences:

1. On a domain-joined server, open Group Policy Management, right-click, and select Run as administrator. You're going to create a new Policy Object.

   

2. Right-click on Group Policy Object and select New.

   

3. You can name this new GPO Dashlane Credential Protection Policy and select OK.

   

4. Right-click on the policy you created and select Edit.

   

5. Go to User Configuration, Preferences, Windows Settings, Registry.

   

6. Notice: XML order matters.

   To ensure a fully silent deployment and prevent immediate, unwanted login prompts for end-users, the registry keys must be applied in a strict order. The extension deployment registry keys must be parsed last.

   Arrange and copy/paste your downloaded XML files in the following sequence:

   1. First (Configuration Keys): Copy and paste the XML files related to configuration parameters first (e.g., Username and MassDeployment keys, silent deploy switch).
   2. Last (Extension Deployment Keys): Copy and paste the Dashlane extension deployment XMLS (Edge and Chrome if applicable)

   By placing the deployment keys last, you ensure the browser downloads and initializes the Dashlane extension only after all required security configurations and licensing policies are established on the device.

7. To import:

   Select all the .xml templates you downloaded, press Ctrl + C to copy them, and Ctrl + V to paste them in the empty Registry window.

8. Select Yes when asked if you want to import the pasted document.

   

9. Close the Group Policy Management Editor.

   

10. Back in the Group Policy Management window, right-click your OU (organizational unit) from the "Group Policy Management" folder and select Link an Existing GPO.

    

11. Select the new policy you created and OK.

    

12. Right-click on the policy created in the Domains folder and select Enforced.

    

After performing these steps, the deployment might take up to eight hours, but it's usually faster.

To ensure Risk Detection's proactive threat monitoring doesn't alert or disrupt employees, you must wait for the policy to take effect in your MDM before deploying the Dashlane browser extension to enrolled devices and activating the feature.

Check that the policy was applied:

Using a device that was part of the group the script was deployed to, go to Registry Editor and select the following folders in order.

Chrome:

HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome\3rdparty\extensions\fdjamakpfbbddfjaooikfcpapjohcfmg\policy

Edge:

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge\3rdparty\extensions\gehmmocbbkpblljhkekmfhjpfbkclbph\policy

In the extensions, you'll see a folder named using the Dashlane browser extension ID. Under that folder, the policy folder contains the actual values of the Credential Protection policy.

Once you have verified the policy is active on target machines, the browsers will silently fetch and install the Dashlane extension in the background without any visible prompts or actions required from your employees.

You can then go back to the Dashlane Admin Console and to Policy deployment and select Mark as done to confirm the policy setup.

Under Available security tools, toggle on the features you want to activate:

• Risk Detection
• Credential Risk Alerts
• AI Phishing Alerts

All threat logs, intercepted phishing attempts, and risk indicators will begin populating in your Admin Console’s Activity Log, Risk Detection, and Phishing Alerts dashboards.

Remove Credential Protection

To remove the extensions via GPO, you'll need to remove the Force Install Edge/Chrome Dashlane extensions files and replace them with these XMLs, which block the Chrome and Edge Dashlane extensions.

Create an XML file to remove the Chrome extension

<Registry clsid="{9CD4B2F4-923D-47F5-A062-E897DD1DAD50}"
 name="Block Dashlane Chrome"
 status="Block Dashlane Chrome"
 image="7"
 changed="2026-04-28 12:00:00"
 uid="{22222222-2222-2222-2222-222222222222}">
    <Properties
        action="U"
        hive="HKEY_LOCAL_MACHINE"
        key="SOFTWARE\Policies\Google\Chrome\ExtensionInstallBlocklist"
        name="1"
        type="REG_SZ"
        value="fdjamakpfbbddfjaooikfcpapjohcfmg"/>
</Registry>

Create an XML file to remove the Edge extension

<Registry clsid="{9CD4B2F4-923D-47F5-A062-E897DD1DAD50}"
 name="Block Dashlane Edge"
 status="Block Dashlane Edge"
 image="7"
 changed="2026-04-28 12:00:00"
 uid="{11111111-1111-1111-1111-111111111111}">
    <Properties
        action="U"
        hive="HKEY_LOCAL_MACHINE"
        key="SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallBlocklist"
        name="1"
        type="REG_SZ"
        value="gehmmocbbkpblljhkekmfhjpfbkclbph"/>
</Registry>