Skip to main content
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 SDKsSDKs 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. Select a Casing convention in the “Flag key conventions” section. 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 keysThe 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 the pencil icon on the flag template you wish to modify and follow the section for that flag template:

​
Default 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

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 a team maintainer for new flags

By default, the account member who creates a flag becomes its maintainer. To keep flag ownership with a group instead of an individual, you can require that a team is set as the maintainer for every new flag in the project. Requiring a team maintainer keeps flag upkeep from depending on a single member who might change teams or leave your organization. To change this setting, you need a role with the updateTeamMaintainerRequirements project action. To learn more, read Project actions. To require a team maintainer for new flags:
  1. Open the Flag settings list for your project.
  2. In the “Team maintainer requirement” section, turn on Require new flags to have a team as their maintainer.
When this setting is on, the flag creation dialog suggests only teams as maintainers, not individual members. Anyone who creates a flag in the project must select a team as the maintainer before they can save the flag.

​
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.