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
  • About approvals
  • Working with approvals
ReleasesRelease management tools

Approvals

Was this page helpful?
Previous

Requesting approvals

Next
Built with

Overview

This topic introduces LaunchDarkly’s approvals feature. It explains what approvals are and how to configure them.

About approvals

When an account member plans a change to a feature flag, AgentControl config, experiment, or segment, they have the option to request approval for that change from a member or team in their LaunchDarkly project. Approvals let more people have input on planned changes. These review-style approvals mimic common code review workflows, such as pull request (PR) reviews in GitHub.

Anyone with the reviewApprovalRequest permission can approve a change, regardless of whether or not their review has been requested. The LaunchDarkly Project Admin, Maintainer, Developer, and Contributor project roles, as well as the Writer, Admin, and Owner base roles, all include this ability. Account members and team members who the requester chooses receive an email notifying them that their review has been requested, and, if applicable, a notification in the LaunchDarkly Slack or Teams app.

Working with approvals

Requiring approvals is available to customers on select plans

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

You can request approval on changes to a flag’s targeting or variations, to an AgentControl config’s targeting or variations, or to a segment’s targeting, any time after you create it. To learn more, read Requesting approvals. Enterprise customers can require approval requests for specific environments. To learn more, read Configuring approvals for an environment.

If someone requests your approval on a flag, AgentControl config, experiment, or segment change, the request appears in the Approvals dashboard, in your email, and in your in-app inbox. Depending on the approval request, it also appears in the following places:

  • For flags, the approval request appears in the flag’s “Pending changes” panel and, if you use the LaunchDarkly Slack or Microsoft Teams app, in a Slack or Teams notification.
  • For configs, the approval request appears in the AgentControl configs’s “Pending changes” panel and, if you use the LaunchDarkly Slack app, in a Slack notification.
  • For experiments, the experiment’s “Pending changes” panel and, if you use the LaunchDarkly Slack app, in a Slack notification.
  • For segments, the approval request appears in the segment’s details page and, if you use the LaunchDarkly Slack app, in a Slack notification.
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.

To learn more, read Reviewing approval requests.

AgentControl config and segment approvals do not appear in Microsoft Teams

If someone requests your approval on a flag change and you use the LaunchDarkly Slack or Microsoft Teams app, you will receive a Slack or Teams notification. AgentControl config and segment approvals are also sent through Slack, but are not sent through Microsoft Teams.

To learn how to customize approval request settings, read Approval request settings.