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
      • Approvals
      • Flag triggers
      • Required comments
      • Required confirmation
      • Scheduled flag changes
      • Workflows
    • 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
    • Feature previews
    • Billing and usage
    • Changelog
Sign inTry it free
LogoLogo
On this page
  • Overview
  • Requiring confirmation
ReleasesRelease management tools

Required confirmation

Was this page helpful?
Previous

Scheduled flag changes

Next
Built with
Required confirmation is available to customers on select plans

Required confirmation 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 how to use required confirmation for feature flag and segment changes.

Requiring members to confirm that they wish to make changes may help them from changing the wrong flag or segment inadvertently.

Required confirmation is only enforced from the user interface

When Require confirmation is enabled, members must enter the environment name or key when they make changes from the Flags list or Segments list in the LaunchDarkly user interface (UI). Confirmation is not required for changes made with the LaunchDarkly API.

When you require confirmation in an environment, members must enter the environment name or key when saving any changes to a flag:

The "Save changes" dialog.

The "Save changes" dialog.

Requiring confirmation

To require confirmation on changes in a new environment:

  1. Click the project dropdown. The project menu appears:

The project menu.

The project menu.
  1. Select Project settings.
  2. Select Environments. The Environments list appears.
  3. Click Add environment. The “Create an environment” panel appears.
  4. Give your environment a human-readable Name.
  5. Select the Require confirmation for flag and segment changes checkbox:

The "Create an environment" panel with the "Require confirmation" checkbox called out.

The "Create an environment" panel with the "Require confirmation" checkbox called out.
  1. Click Create environment.

To learn more, read Create environments and Edit environment settings.

To require confirmation in an existing environment:

  1. Click the project dropdown. The project menu appears:

The project menu.

The project menu.
  1. Select Project settings.
  2. Select Environments. The Environments list appears.
  3. Next to the environment you want to edit, click the overflow menu and choose Edit environment. The Edit environment panel appears.

The environment overflow menu, including the "Edit environment" option.

The environment overflow menu, including the "Edit environment" option.
  1. Select the Require confirmation for flag and segment changes checkbox.
  2. Click Save environment.

Confirmation of flag changes is now required for your environment.