For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Sign inTry it free
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
  • Get started
    • Overview
    • Onboarding
    • Get started
    • Launch Insights
    • LaunchDarkly architecture
    • LaunchDarkly vocabulary
  • AgentControl
    • AgentControl
    • Manage AgentControl
  • Feature flags
    • Create flags
    • Target with flags
    • Flag templates
    • Manage flags
    • Code references
    • Contexts
    • Segments
  • Releases
    • Releasing features with LaunchDarkly
    • Release policies
    • Percentage rollouts
    • Progressive rollouts
    • Guarded rollouts
    • Feature monitoring
    • Release pipelines
    • Engineering insights
    • Release management tools
    • Applications and app versions
    • Change history
    • Restoring previous flag versions
  • Observability
    • Observability
    • Session replay
    • Error monitoring
    • Logs
    • Traces
    • Observability metrics
    • Product analytics events
    • LLM observability
    • Alerts
    • Dashboards
    • Service map
    • Vega for auto-remediation
    • Observability MCP server
    • Search specification
    • Observability settings
    • Observability integrations
  • Experimentation
    • Experimentation
    • Experiment metric types
    • Experiment configuration
    • Managing experiments
    • Analyzing experiments
    • Multi-armed bandits
    • Holdouts
  • Metrics and events
    • Metrics in LaunchDarkly
    • Creating metrics
    • Metric groups
    • Events
    • Autogenerated metrics
  • Warehouse native
    • Warehouse native metrics
    • Setting up external warehouses
    • Creating experiments using warehouse native metrics
  • Infrastructure
    • Connect apps and services to LaunchDarkly
    • LaunchDarkly in China and Pakistan
    • LaunchDarkly in the European Union (EU)
    • LaunchDarkly in federal environments
    • Public IP list
  • Your account
    • Projects
    • Views
    • Environments
    • Tags
    • Teams
    • Members
    • Roles
    • Account security
      • Single sign-on
        • Configure SAML SSO
        • Enable SCIM provisioning
        • Enable SSO
        • Disable SSO
        • Change SSO providers
        • Google OAuth
        • GitHub OAuth
      • API access tokens
      • Multi-factor authentication
      • Domain verification
      • IP allowlist
      • Managing sessions
      • Organization access settings
      • Organization announcements
      • Support options
      • Resetting your password
    • Feature previews
    • Billing and usage
    • Changelog
Sign inTry it free
LogoLogo
On this page
  • Overview
  • Enable SSO in LaunchDarkly
  • Supported external identity providers
  • Default initial role
Your accountAccount security

Single sign-on

Was this page helpful?
Previous

Configure SAML SSO

Next
Built with
Single sign-on is available to customers on select plans

Single sign-on is only available to customers on select plans. To learn more, read about our pricing. To upgrade your plan, contact Sales.

Overview

This topic explains what Single Sign-On (SSO) features are available in LaunchDarkly.

SSO allows your team to authenticate with LaunchDarkly using the same identity provider (IdP) you use for your other internal and external services. LaunchDarkly implements SSO with the SAML 2.0 protocol. You can use SSO with your IdP to manage access rights in LaunchDarkly. You can use SSO to manage both member login and member roles, or you can use SSO to manage member login only, and continue to manage member roles within LaunchDarkly.

As a customer on an Enterprise or Guardian plan, after you enable SSO, System for Cross-domain Identity Management (SCIM) becomes available. SCIM facilitates user provisioning, which means your IdP can use it to create, update, and deactivate members in LaunchDarkly. Administrators can optionally turn on and configure team sync with SCIM, which lets admins sync groups in their IdP with LaunchDarkly teams.

Enable SSO in LaunchDarkly

To configure SSO in your LaunchDarkly account:

  1. Enable SAML SSO in your account. Configure LaunchDarkly to use your IdP when account members request access. To learn how to do this, read Configure SAML SSO.
  2. (Enterprise and Guardian - Optional) Configure SCIM to enable the automation of user and group provisioning. To learn how to do this, read Enable SCIM provisioning.

Supported external identity providers

We provide support for the following IdPs:

Identity provider

SAML SSO integration: member and team provisioning

SCIM integration (Enterprise only)

Team sync with SCIM (Enterprise only)

ADFS

Entra ID

GitHub OAuth

Google Workspace

Google OAuth

Okta

OneLogin

Some customers use the following identity providers. Although we do not offer support for these providers, we can share some configuration guidance based on what has been successful for other customers:

  • PingIdentity
  • Centrify
  • SecureAuth
  • DuoMobile

You can only use one identity provider per LaunchDarkly account.

Default initial role

During account member provisioning, LaunchDarkly sets the default initial role for new members to a role that you specify.

To set a default initial role:

  1. Click the gear icon in the left sidenav to view Organization settings.
  2. Click Security.
  3. Under “SSO Management,” click Configure SAML. The SAML configuration panel appears.
  4. Under “Default initial role,” select the default Role for new members.
  5. Click Save.

The "Default initial role" section of the SAML configuration panel.

The "Default initial role" section of the SAML configuration panel.

LaunchDarkly sets the default initial role for new members to the initial Role specified here, unless you have specified a different role in your IdP.

We recommend setting the default initial role to No access. The No access base role can help you mitigate risk, for instance if you have private projects that should be hidden from most members.

Developer and Foundation customers can only set the default role to the Reader base role.

To learn more about roles and their permissions, read Roles. For an in-depth guide on how to use custom roles with IdPs, read Creating roles.