# Flags page

The **Flags** page is an overview of all the flags you have created on your Flagship account, with an overview of how many live, paused and draft use cases use this flag. All the flags you create in this page will be available in the flag section of your use cases.

## 📖 Definition

A **flag** is a variable you want to act on with a specific value (Boolean, integer, string, object, array).\
Each flag displays the number of live, paused, draft features and code-based references in which it is used.

## ⚙️ Configuration

To create a flag, apply the following steps:

1. Click *Create new flag*.
2. Enter the flag name and description.
3. Select the flag type among the following: Text, Boolean, Numbers, Object, Array.
4. (Optional) Enter the predefined values of the flag.
5. Click *Create*:\
   The created flag appears in a new line.

| <p>⭐ Good to know</p><p>We recommend using a clear name and description for your flag to avoid issues with the flag spelling or type when using it in future use cases.</p> |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

Once a flag has been created, it will be displayed in the flag list along with the other, previously created flags.\\

| <p>🚩 Heads up</p><p>If you are editing a flag name or type that is already used in one or several use cases, <strong>this could break your app/website.</strong> For this reason, we don’t recommend editing a flag that is already used in a use case.</p> |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |

And get the following information at first sight:

* the flag name;
* the flag type;
* the creation date;
* the flag category
* the default and predefined values
* the number of live, paused and draft use cases in which the flag is being used.

And on click on the line:

* the predefined values set up earlier;
* the name and status of the use cases in which the flag is being used;
* the flag location in the use case;
* the information on whether the flag is present in the code or not and how many occurrences there are (if you have correctly set up the codebase analyzer).

To find out the exact location of your flag, you can click on the repository link to be redirected to your versioning tool.\
To be able to retrieve your flags more easily, you can filter them by creation date and type using the *Filter* button.

![Flags\_filters.png](/files/5ehxJZchBnKpcjzGcZDP)

## 🤓Use case

The flags page can be useful to:

* Make sure the flag you are using in your use case will be the same as the one in your code (with the list of pre-filled flags).

![Flags\_standard.png](/files/3ADuob8i8OdopSvlNhO1)

* Let the developers integrate the Codebase Analyser to always have the latest flags implemented in the code and pushed live.

![Codebase\_analyzer.png](/files/Mu2rua3ABZWx8ytBF2kt)

* Know how many features a flag is used in, and the name and status of these features from the *Usage* section.

![Usage.png](/files/4Y3NCJYqrbJAPVoiPYjZ)

* Know whether a flag is used in your code and where from the *Codebase references* tab.

**Need additional information?**

Submit your request at <product.feedback@abtasty.com>

Always happy to help!


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.abtasty.com/flagship-deprecated/navigating-the-interface/flags-page.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.