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
        • Requesting approvals
        • Reviewing approval requests
        • Deleting approval requests
        • Approval request settings
        • Configuring approvals for an environment
      • 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
  • Approval settings
ReleasesRelease management toolsApprovals

Approval request settings

Was this page helpful?
Previous

Configuring approvals for an environment

Next
Built with

Overview

This topic explains how to customize the settings for your approval requests.

Approval settings

Approvals for experiments are in beta

Approvals for experiments are in beta. If you want early access, request to opt-in to the beta feature.

You can customize how approval requests are managed and enforced by making changes in an environment’s Approval settings.

For each environment, you can specify:

  • whether approvals are required for changes to flags, AgentControl configs, experiments, or segments in the environment
  • whether requestors can approve their own requests
  • how many approvals are required before a requester can apply a change
  • whether consensus is required, that is, whether the requester can apply changes if any reviewers have declined a request
    • Members can approve and apply requests when they have the reviewApprovalRequest and applyApprovalRequest actions for flags and experiments, segments, or AgentControl configs. To learn more, read Roles.
  • Some flag changes, like turning targeting on or off or changing targeting rules, affect the flag only at the environment level. Other flag changes, like editing flag variations, affect the flag at the project level.
  • Similarly, AgentControl config changes can affect one or more environments in a project.
  • Segment changes affect only the environment in which the segment is defined.

If a change that affects an environment with approvals required is made, the change will trigger an approval request.

Enterprise customers can customize an environment’s approval settings in the “Edit environment” panel for that environment. To learn more, read Configuring approvals for an environment.

The following actions do not trigger an approval request:

  • Changing a flag’s name, maintainer, description, or tags
  • Creating, archiving, or deleting a flag
  • Changing an AgentControl config’s name, maintainer, description, or tags
  • Creating, archiving, or deleting an AgentControl config
  • Creating or deleting an experiment
  • Changing a segment’s name, description, or tags
  • Creating or deleting a segment

To prevent members from making these kinds of changes, you can configure and assign custom roles that deny these actions. To learn how, read Roles.