The Settings tab for each feature flag allows you to modify flag settings including the name and description of the flag.
The 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. You can assign any member of your team as the maintainer for a particular flag
Tags are labels that help you categorize flags. This is especially helpful for managing flag permissions using 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.
Feature flags must be marked 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.
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.
Requires Data Export
This setting is only visible to customers using Data Export.
Flag evaluation events are summarized by default to minimize the transfer of duplicate data. Customers using Data Export can enable this setting to send detailed event data for a given flag. Note that unlike other flag settings on this page, you can adjust this setting for each environment in the project.