Other flag settings
Read time: 3 minutes
Last edited: Feb 27, 2023
This topic explains how to make other changes to your feature flags in the flag's Settings tab.
A feature flag's Settings tab lets you change flag settings, including the name and description of the flag. Some settings apply only to the currently selected environment, while others apply across all environments. You can also clone or archive a flag from this tab.
Settings for the current environment
Both data export settings and flag triggers are specific to the current environment.
Here is an image of the settings for the current environment on the flag's Settings tab:
Sending detailed event information
LaunchDarkly summarizes flag evaluation events by default to minimize data use, and limits events transmission to 100 MBps.
If you use Data Export, you can enable it to send detailed event data for a given flag. You can adjust this setting for each environment in the project.
To learn more, read Data Export.
Changing flag targeting remotely
Flag triggers let you make changes to flag targeting remotely from a third-party application, such as an APM tool. You can use triggers to turn flag targeting on or off. You can enable flag triggers for each environment in the project.
To learn more, read Flag triggers.
Settings for all environments
The majority of flag settings apply to all environments.
Here is an image of the settings for all environments on the flag's Settings tab:
The flag maintainer is the account member who is primarily responsible for the flag. By default, the maintainer is set to the member who created the flag, but you can assign any member of your team as the maintainer for a particular flag.
Enterprise customers using Teams can assign a team as the flag's maintainer. This offers the additional benefit of shared accountability and also ensures that if one member leaves the team, the flag still has other maintainers.
You can update the flag's maintainer on the flag's Settings tab. You can also update the maintainer by clicking the pencil icon from the header of any of the flag's tabs:
You can change the flag's name and description here.
In addition to the descriptors, every flag has a unique key which you set during flag creation. Be thoughtful when you create a new flag key. You cannot change it after you save the flag.
Tags are labels that help you categorize flags. They're especially helpful for managing flag permissions with custom roles. For example, you can tag flags with
marketing flags or
devOps tags, and then use these tags to determine who has read or write access for the flag.
You can mark flags permanent if they're intended to exist in your codebase long-term, for example, a flag that enables a site-wide maintenance mode. LaunchDarkly does not prompt you to remove permanent flags, even if one variation has been rolled out to your entire user base. In addition, when someone attempts to remove a permanent flag, they receive a warning about the flag's permanent status.
Client-side SDK availability
If you're using a client-side or mobile SDK, you must expose your feature flags in order for the client-side or mobile SDKs to evaluate them. To learn more, read Making flags available to client-side and mobile SDKs.
You can use custom properties to connect individual flags to some LaunchDarkly integrations. To learn more, read Custom properties.
Cloning a flag
You can create new flags by cloning existing flags. When you clone a flag, LaunchDarkly makes a new flag and copies the original flag's targeting configuration for all environments. To learn more, read Cloning flags.
Archiving a flag
You can archive a flag if you want to retire it from LaunchDarkly without deleting it. Archived flags are archived across all environments. To learn more, read Archiving flags.