Use Dashlane Confidential SSO and SCIM Provisioning to integrate with your IdP – Dashlane

SSO and SCIM are only available to organizations with Password Management or Credential Protection.

You can integrate Dashlane with your Identity Provider (IdP) using the Dashlane Confidential SSO and Confidential SCIM Provisioning configurations.

More about integrating Dashlane with your IdP

Set up Confidential SSO and Provisioning

For full setup instructions, select your IdP:

Although Dashlane may work with other cloud and on-prem SAML 2.0 IdPs that we don't mention in this article, we recommend confirming with our Support team first. You can contact our Support team directly through the Dashlane Admin Console.

Contact Support through the Admin Console

Want to learn more?
Check out our white paper on password management and secure single sign-on

Common questions about Dashlane Confidential SSO and Provisioning

What are Dashlane Confidential SSO and SCIM Provisioning?

When you integrate Dashlane with your Identity Provider, you have two configuration options:

Dashlane Confidential
Self-hosted

Your choice depends on how you want to set up your encryption service, which is an added layer of security that we require for SSO and SCIM.

What's an encryption service?
More about the difference between Confidential and self-hosted

How does Confidential work? Is it secure?

Dashlane Confidential SSO and SCIM Provisioning protect the privacy of your plan members and reduce the number of attack surfaces to protect customers from theft, data breaches, or cyberattacks.

Confidential uses secure enclaves to process sensitive data in the cloud via a technique called confidential computing. The contents of the enclave, including the data being processed and the methods used to handle it, are secure in a secluded, isolated environment, significantly reducing the attack surface and mitigating the risk of unauthorized access when members access Dashlane or use it with their other applications. This system further protects and securely processes highly sensitive data.

Can I switch to self-hosted after I set up Confidential?

No, you can’t switch to self-hosted after you set up Confidential SSO. Before setting up Confidential SSO, make sure it meets your organization's needs.

More about the difference between self-hosted and Confidential

Important: Self-hosted SSO is no longer available for setup after October 2025. Please consider using the Confidential SSO instead. If you have already set up Self-hosted, you can keep that setup.
More about Dashlane Confidential SSO and SCIM Provisioning

Can I verify more than one email domain for my SSO setup?

Yes, you can verify as many domains as you own in the Domain Management page.

Domain verification for professional plans

Can I manage multiple Dashlane domains under one Identity Provider?

Yes. The option to have a unique Entity ID and have multiple domains in one IdP was introduced with extension version 6.2551 in January 2026. If you set up Confidential SSO after this version, your SSO setup already supports this Identity partitioning. If you set up Confidential SSO before this version was released, you can migrate your setup to support the Identity partitioning feature. While this migration is optional, it is recommended for organizations requiring more complex identity configurations.

Follow these simple steps:

Log in to the Admin Console
In the Integrations section of the left menu, select Single sign-on and then Edit.
You'll see the option to migrate your SSO setup.
Select Migrate and then Confirm & migrate to new ID to generate a new unique Entity ID.
Copy this value and navigate to your IdP, such as Okta, Entra ID (Azure), Google Workspace, or PingID, to locate your Dashlane application. Replace the existing Entity ID with the new string and save your changes to restore access.