Project-level flag settings
Project-level flag settings
Project-level flag settings
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:

The following sections describe the available project-level flag settings.
To make all of a project’s flags available to client-side or mobile SDKs by default:
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.
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:

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.
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:
This section lets you customize the default template settings for custom flags. Here’s how:
Verify that the updated default template settings are correct by navigating to the flags list and creating a new flag of this template type.
This section lets you customize the default template settings for release flags. Here’s how:
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.
This section lets you customize the default template settings for kill switch flags. Here’s how:
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.
This section lets you customize the default template settings for experiment flags. Here’s how:
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.
This section lets you customize the default template settings for migration flags. Here’s how:
Verify that the updated default template settings are correct by navigating to the flags list and creating a new flag of this template type.
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.