LaunchDarkly Developer Documentation

Get started in under 30 minutes.
LaunchDarkly provides feature flags as a service for Java · Python · Ruby · Go · Node.js · PHP · .NET. Control feature launches -- who sees what and when -- without multiple code deploys. Easy dashboard for phased rollouts, targeting and segmenting.
Need more help? write us at

Get Started    Documentation

Other flag settings


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.

A flag's settings tab.

A flag's settings tab.

The fields in the Settings tab do the following things:

Field name


The flag maintainer is the team 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.


The feature flag's name. You can change it here.


The feature flag's description. You can change it here.


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.

To learn more, read Custom Roles.

Make this flag available to the client-side SDK

You must make feature flags available to the client-side SDK before they can be used in variation calls on the front-end. If you request a feature flag that is not available, you'll receive the default value for that flag.

If you want flags marked as available to the client-side SDK by default, you can check the "Make new flags available to the client-side (JavaScript) SDK by default" in Project settings. Click the Edit button just above the project table to edit this project specific setting.

To learn more, read JavaScript SDK Reference.

This is a permanent flag

You can mark flags permanent if they're intended to exist in your codebase long-term (e.g. a flag that's used to enable a site-wide maintenance mode).

We will not prompt you to remove permanent flags, even if one variation has been rolled out to all of your users.

Flag keys can't be changed

In addition to the descriptors, every flag has a unique key which you set during flag creation. The key cannot be edited after the flag is created.

Sending detailed event information

Detailed events require Data Export

This setting is only visible to customers using Data Export.

Data Export is only available to customers on our enterprise plans. If you're interested in learning more about our enterprise plans, contact

Flag evaluation events are summarized by default to minimize data use.

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.

The "Send detailed event information for this flag" field.

The "Send detailed event information for this flag" field.

Other flag settings

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.