• Home
  • Integrations
  • SDKs
  • Guides
  • API docs
No results for ""


Other flag settings

Read time: 1 minute
Last edited: Jan 05, 2022


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.

Here is an image of the flag settings tab:

A flag's Settings tab.
A flag's Settings tab.

The fields in the Settings tab do the following things:

Field NameDescription
MaintainerThe flag maintainer is the account member who's 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.
NameThe feature flag's name. You can change it here.
DescriptionThe feature flag's description. You can change it here.
TagsTags 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.
(Checkbox) This is a permanent flagYou 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 all of your users. In addition, when someone attempts to remove a permanent flag, they receive a warning about the flag's permanent status.
(Checkbox) SDKs using Mobile keyYou must make feature flags available to mobile SDKs before front-end calls can use them. Make this flag available to mobile SDKs by default by checking this box.
(Checkbox) SDKs using Client-side IDYou must make feature flags available to the client-side SDK before front-end calls can use them. Make this flag available to the client-side SDK by default by checking this box.
Add custom propertyYou can use custom properties to connect individual flags to some LaunchDarkly integrations. Click this button and choose an integration from the dropdown.
Flag keys are permanent

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.

Sending detailed event information

Detailed events require Data Export, an Enterprise feature

Detailed events require Data Export, available to customers on an Enterprise plan. To learn more, read about our pricing. To upgrade your plan, contact Sales.

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. Unlike other flag settings on this page, you can adjust this setting for each environment in the project.

To learn more, read Data Export.