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
      • 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
  • About organization access settings
  • Enable domain matching
  • Enable matched seat provisioning
Your accountAccount security

Organization access settings

Was this page helpful?
Previous

Organization announcements

Next
Built with

Overview

This topic explains how to enable and disable organization access settings in LaunchDarkly.

You must have a LaunchDarkly Admin organization role or Admin base role to manage organization access settings. You can disable organization access settings at any time.

About organization access settings

You can configure organization access to allow members of your organization to find and join your LaunchDarkly accounts.

Organization access settings include the following options:

  • Enable domain matching
  • Enable matched seat provisioning

Enable domain matching

Domain matching allows new members to discover your account and request access if their verified email domain matches your organization owner’s email domain. You can disable domain matching at any time.

To enable domain matching:

  1. Click the gear icon in the left sidenav to view Organization settings.
  2. Click Security and scroll to the “Organization access settings” section.
  3. Check “Enable domain matching.”

Organization access settings with domain matching enabled.

Organization access settings with domain matching enabled.

Domain matching is now enabled. New members whose verified email domains match the Owner’s email domain can discover and request access to your LaunchDarkly account.

The "Select an organization" screen with domain matched accounts found.

The "Select an organization" screen with domain matched accounts found.

When a new member requests access to your LaunchDarkly account, the account Owner and Admins receive the request in an email, and the pending request is available for approval on the Members page. Owners and Admins can approve access requests. To learn more, read Accept pending requests.

Enable matched seat provisioning

Matched seat provisioning allows new members with verified email domains that match your organization owner’s domain to join your account automatically, if there are available seats. To enable matched seat provisioning you must also enable domain matching. You can disable matched seat provisioning at any time.

To enable matched seat provisioning:

  1. Click the gear icon in the left sidenav to view Organization settings.
  2. Click Security and scroll to the “Organization access settings” section.
  3. Check “Enable matched seat provisioning.”

Organization access settings with matched seat provisioning enabled.

Organization access settings with matched seat provisioning enabled.

Matched seat provisioning is now enabled, and new members whose verified email domains match the Owner’s email domain can automatically join your LaunchDarkly account if there are available seats.

LaunchDarkly assigns the Reader base role by default to new members who automatically join your account. To learn more, read Organization roles.

Accounts with SSO enabled do not support domain matching and matched seat provisioning

SSO requires members to log in through their identity provider. New members will be able to discover, but not join, accounts with SSO enabled.