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
  • Integrations
    • Collaboration tools
    • Data Export
    • Edge tools
    • Environments as a service
    • Experimentation and metric integrations
    • Internal developer platforms
    • Monitoring tools
    • Segments integrations
    • Workflow management tools
      • Azure DevOps
      • Custom approvals
        • Creating your own approval application
        • Adding a custom approvals integration
        • Configuring environments to use a custom approval integration
      • Jira Cloud
      • ServiceNow approvals
      • Sleuth
      • Tray
      • Trello
      • Zapier
    • More integrations
    • Managing integrations
    • Using the LaunchDarkly integration framework
    • Building partner integrations
Sign inTry it free
LogoLogo
On this page
  • Overview
  • Configure a LaunchDarkly environment to use the custom approvals integration configuration
IntegrationsWorkflow management toolsCustom approvals

Configuring environments to use a custom approvals integration

Was this page helpful?
Previous

Jira Cloud

Next
Built with

Overview

This topic describes how to configure LaunchDarkly environments to use a custom approvals integration configuration for flag and experiment changes. This is the final step required in configuring a custom approvals integration.

Configure a LaunchDarkly environment to use the custom approvals integration configuration

By default, LaunchDarkly’s approvals request feature only creates approval requests in LaunchDarkly. You can change this behavior so that LaunchDarkly creates change requests in your approvals application.

Before you complete this configuration, you must create your own approval application and add a custom approvals integration configuration.

Then, to create change requests in your approvals application, you must update your chosen LaunchDarkly environment’s approval settings to reference your custom approvals integration configuration.

Here’s how:

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

The project menu.

The project menu.
  1. Select Project settings. The list of project settings appears.
  2. Click Approval settings.
  3. In the “Flag and experiment approvals” section, select an environment.
  4. Click Edit approval setting. The “Approval settings for [environment]” dialog appears.
  5. Change the Approval system from “LaunchDarkly” to your custom approvals integration configuration.
  6. (Optional) Select the Require approvals for this environment checkbox to require approval for flag and experiment targeting changes in this environment. If you select this, then you must also choose:
    • All flags and experiments: Select to require approval for all flag targeting and experiment changes.
    • Flags and experiments matching the following tags: Select to require approval only for flag targeting and experiment changes on flags and experiments with the listed tags. While tags are global across environments, this setting applies only to flags and experiments in the current environment.
    • Allow deleting scheduled changes without approval: Select to allow scheduled changes for a flag or experiment to be deleted without approval in this environment.
  7. Choose whether to Automatically apply flag and experiment changes in LaunchDarkly when associated external change requests are approved.
  8. Click Save changes.

After you have configured your chosen LaunchDarkly environments to use the custom approvals integration, members of your organization in LaunchDarkly can request approval for flag and experiment changes within LaunchDarkly. Requests will then be sent to your approvals application whenever the state of the approval request changes in LaunchDarkly.