> ## Documentation Index
> Fetch the complete documentation index at: https://launchdarkly.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Release flags
This topic explains how you can use release flags to progressively roll out functionality. Release flags are temporary flags that initially do not serve the new functionality, then are used to progressively roll out the functionality until they reach 100%.
## About release flags
Release flags, sometimes called rollout flags, are temporary boolean flags with two variations: "Available" (true) and "Unavailable" (false).
In the most common use case, you wrap a release flag around code for a new or improved feature, and use the flag to release the new feature to your customers in increments. Release flags are temporary. After you verify the new code is stable and roll out the feature to 100% of your customers, you should delete the flag.
**Using a release flag does not initiate a rollout**
Using a flag created with the **Release** template does not automatically configure a rollout or any targeting behavior. To use the flag to progressively roll out a feature, you must manually configure those rules. To learn more, read [Progressive rollouts](/docs/home/releases/progressive-rollouts).
## Create release flags
To create a release flag:
1. Click **Create** and choose **Flag**. The "Create flag" dialog appears.
2. Enter a unique, human-readable **Name**. A suggested key auto-populates from the name you enter, but you can customize it if you wish.
3. (Optional) Click **Edit key** to update the flag key. You'll use this key to reference the flag in your code.
4. (Optional) Enter a **Description** of the flag. A brief, human-readable description helps your account members understand what the flag is for.
5. (Optional) Click **Custom** and select **Release**.
6. (Optional) Change the [default on](/docs/home/flags/default-rule) and [default off](/docs/home/flags/off-variation) variations if needed.
7. (Optional) Click on your member name to change the flag maintainer.
8. (Optional) Click the **tag** icon to add one or more [tags](/docs/home/account/tags).
9. (Optional) Click the **views** icon to add the flag to a [view](/docs/home/account/views).
10. (Optional) Click **All SDKs** to make the flag [unavailable to client-side or mobile SDKs](/docs/home/flags/flag-settings). Flags are available to all SDKs by default.
11. (Optional) Click **Prerequisite** to add a [prerequisite flag](/docs/home/flags/prereqs).
12. Click **Create flag**.
The flag **Targeting** tab appears.
After you create a flag, you can make further changes to it as needed, such as to [update flag targeting](/docs/home/flags/target)
To learn more, read [Creating new flags](/docs/home/flags/new).
Because release or rollout flags are used to release a new feature in increments, they typically do not use complex targeting rules. Instead, they serve a percentage rollout in their default rule. To learn more, read [Percentage rollouts](/docs/home/releases/percentage-rollouts).
## Modify the release flag template
To modify your release flag template:
1. Click the project dropdown. The project menu appears:
2. Select **Project settings**.
3. Select **Flags**. The **Flags** settings list appears.
4. In the "Flag templates" section, click the **pencil** icon next to "Release."
5. Choose **Yes** or **No** to mark all release flags as temporary or permanent. Release flags are usually temporary.
6. In the "Variations" section, edit the flag variation **Names**.
7. In the "Default variations" section, choose which default variations to serve when the flag is toggled **On** or **Off**.
8. In the "Tags" section, type to add tags to each new flag by default.
9. Click **Save**.
Verify that the updated default template settings are correct by navigating to the **Flags** list and creating a new release flag.