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
      • The Flags list
      • Comparing and copying flag settings
      • Viewing flags across environments
      • Deprecating flags
      • Archiving flags
      • Deleting flags
      • Flag prerequisites
      • The off variation
      • The default rule
      • Flag statuses and lifecycle stages
      • Flag lifecycle settings
      • Project-level flag settings
      • Vega for flag cleanup
    • 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
    • Feature previews
    • Billing and usage
    • Changelog
Sign inTry it free
LogoLogo
On this page
  • Overview
  • Client-side availability
  • Flag key conventions
  • Flag templates
  • Custom flag template settings
  • Release flag template settings
  • Kill switch flag template settings
  • Experiment flag template settings
  • Migration flag template settings
  • Require flags to be linked to a view
Feature flagsManage flags

Project-level flag settings

Was this page helpful?
Previous

Vega for flag cleanup

Next
Built with

Overview

This topic describes project-level flag settings and how to update them.

When you set or update the Flag settings for a project, the changes apply to any new flags created in the project after the settings update. No existing flags are updated.

To access the project-level flag settings:

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

The project menu.

The project menu.
  1. Select Project settings.
  2. Select Flag settings. The Flag settings list appears.

The following sections describe the available project-level flag settings.

Client-side availability

To make all of a project’s flags available to client-side or mobile SDKs by default:

  1. Open the Flag settings screen for your project.
  2. In the “Client-side availability” section, check SDKs using Mobile Key or SDKs using Client-side ID.
  3. Click Save.
Security implications of making flags available to mobile SDKs

SDKs for mobile devices use mobile SDK keys, which are readily available to mobile apps. A leaked mobile SDK key allows the holder to circumvent JavaScript’s Secure Mode. This can give the holder access to the value of every flag for any context, even without knowing the SDK key that hashes the context key in Secure Mode.

To learn more, read Choosing an SDK type.

Flag key conventions

If you would like to standardize how members of your organization define feature flag keys, you can specify a convention in the project settings and LaunchDarkly will enforce your convention for all new flags. This includes flags that you create or import through the LaunchDarkly user interface, as well as flags that you create using the REST API.

To enforce naming conventions for flag keys:

  1. Open the Flag settings list for your project.
  2. In the “Flag key conventions” section, select a Casing convention. Review the example to confirm the convention you’ve selected:

The Flag key conventions section, with "camelCase" selected.

The Flag key conventions section, with "camelCase" selected.
  1. (Optional) Check Add prefix and enter a Prefix that all flag keys should use.
  2. Select Save.
Automatically generated flag keys

The key in the Key field is automatically generated from the flag name. The system adds a dash between letters and numbers. For example, a flag named example-flag-v1 generates the suggested key example-flag-v-1.

This behavior is intentional for consistency and readability but is only a suggestion, not a requirement. You could manually update the generated key to example-flag-v1 if you wished.

Flag templates

LaunchDarkly projects have groups of default settings, called “templates,” for each type of flag. When you create a flag from a template, that template’s default settings appear as pre-set configuration options.

You can modify default flag templates. LaunchDarkly applies those default settings to new flags of the same template type within the project. Updated default settings only apply to flags created after you modified the default settings. If you change a flag template’s default settings, LaunchDarkly does not retroactively apply the new defaults to existing flags.

To modify a flag template:

  1. Open the Flag settings list for your project.
  2. In the “Flag templates” section, click pencil icon on the flag template you wish to modify and follow the section for that flag template:
  • Custom flag template settings
  • Release flag template settings
  • Kill switch flag template settings
  • Experiment flag template settings
  • Migration flag template settings

Custom flag template settings

This section lets you customize the default template settings for custom flags. Here’s how:

  1. In the “Flag templates” section, click Edit.
  2. Choose Yes or No to mark all flags of this template type as temporary or permanent.
  3. In the “Variations” section, edit the flag variation Names.
  4. In the “Default variations” section, choose which default variations to serve when the flag is toggled On or Off.
  5. In the “Tags” section, type to add tags to each new flag by default.
  6. Click Save.

Verify that the updated default template settings are correct by navigating to the flags list and creating a new flag of this template type.

Release flag template settings

This section lets you customize the default template settings for release flags. Here’s how:

  1. In the “Flag templates” section, click Edit.
  2. Choose Yes or No to mark all flags of this template type as temporary or permanent. Release flags are usually temporary.
  3. In the “Variations” section, edit the flag variation Names.
  4. In the “Default variations” section, choose which default variations to serve when the flag is toggled On or Off.
  5. In the “Tags” section, type to add tags to each new flag by default.
  6. Click Save.

Verify that the updated default template settings are correct by navigating to the Feature flags list and creating a new flag of this template type.

Kill switch flag template settings

This section lets you customize the default template settings for kill switch flags. Here’s how:

  1. In the “Flag templates” section, click Edit.
  2. Choose Yes or No to mark all flags of this template type as temporary or permanent. Kill switch flags are usually permanent.
  3. In the “Variations” section, edit the flag variation Names.
  4. In the “Default variations” section, choose which default variations to serve when the flag is toggled On or Off.
  5. In the “Tags” section, type to add tags to each new flag by default.
  6. Click Save.

Verify that the updated default template settings are correct by navigating to the Feature flags list and creating a new flag of this template type.

Experiment flag template settings

This section lets you customize the default template settings for experiment flags. Here’s how:

  1. In the “Flag templates” section, click Edit.
  2. In the “Tags” section, type to add tags to each new flag by default.
  3. Click Save.

Verify that the updated default template settings are correct by navigating to the Feature flags list and creating a new flag of this template type.

Migration flag template settings

Migration flags are not available in LaunchDarkly's European Union (EU) instance
To learn more, read LaunchDarkly in the European Union (EU).

This section lets you customize the default template settings for migration flags. Here’s how:

  1. In the “Flag templates” section, click Edit.
  2. In the “Tags” section, type to add tags to each new flag by default.
  3. Click Save.

Verify that the updated default template settings are correct by navigating to the flags list and creating a new flag of this template type.

Require flags to be linked to a view

If you use views to organize flags and restrict access, you can require that new flags are linked to a view. Configure this setting in Project settings under Views, Settings.

To learn how to require flags or segments to be linked to a view, read Require resources to be linked to a view.