> For the complete documentation index, see [llms.txt](https://docs.hackle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackle.io/en/feature-flag/ff-sdp-editing.md).

# (In Progress) Feature Flag Detail Screen

This document introduces what you can see on the Feature Flag detail screen.

## Accessing the Detail Screen

You can access the detail screen of a specific Feature Flag after creating a new Feature Flag, or by clicking on a specific Feature Flag in the Feature Flag list.

## Detail Screen Layout

The Feature Flag detail screen shows the following content:

Feature Flags can only be used with SDK version 2.0.0 or higher. If you are using a lower SDK version, you must update.

![Default content visible after creating a Feature Flag](/files/MDurIpCcBQDuCCtGWBjx)

1. **Update**\
   Feature Flags can only be used when the SDK version is at least 2.0.0. If you are using a lower SDK version, you must update. Clicking this button navigates to a page with update instructions.
2. **Feature Key**\
   When using Feature Flag-related methods in the SDK, the Feature Key is required as a parameter. The number displayed next to the Feature Key text is the Feature Key value — in this screenshot, it is 1.\
   Please share this key value and the [SDK](/en/development-guide/sdk.md) guide document with the developer in charge.
3. **Feature Flag Information**\
   The Feature Flag name and description entered during creation are displayed.
4. **Feature Flag Status**\
   You can set the Feature Flag status to on or off.
5. **Feature Flag Monitoring**\
   You can view trends in event data generated by the Feature Flag.\
   In the Set Events modal, you can select up to 5 events to monitor through this Feature Flag.

![Monitoring - Set Events](/files/n37Zi2LkC8cEf2jXyUiK)

6. **Tab Menu**\
   Menus for the Feature Flag are provided as tabs. By default, the Feature Flag Settings tab is selected as shown above.\
   (Feature Flag Settings, Real-time Exposure Status, Jira Integration, Change History)

### Feature Flag Settings Tab

You can configure Feature Flag states such as Individual Targeting and User Targeting.

![](/files/08yGmprwoWLGRyjaDnBK)

1. **Individual Targeting**\
   A feature that force-assigns specific users to always have the Feature Flag in an off or on state.\
   Configured using User Identifiers. Useful when you only want specific internal people to test.\
   Click the **`Register`** button on the right to open a dialog for configuring Individual Targeting targets.

![A case where no users are always-off, and five User Identifiers have been configured to always-on](/files/zQ8SAB5DFurSXL5SFMPc)

2. **User Targeting**\
   For users not subject to Individual Targeting, you can apply Feature Flag state values to users with specific properties.

Also, you configure what percentage of the remaining users not subject to User Targeting will encounter the feature corresponding to the Feature Flag on state.\
The traffic ratio can be freely adjusted between 0 and 100. You can increase it and then lower it. For example, it is possible to set it to 80 and then adjust to 50, or to set it to 25 and then adjust to 50.\
After setting the traffic ratio, click the **`Save`** button on the right to apply it.

For more details, refer to the [User Targeting](/en/feature-flag/create-and-configure/ff-targeting.md) document.

![](/files/zZmZsJioSFF6FvHFyQUj)

### Real-time Exposure Status Tab

You can see the number of users who encountered the Feature Flag on or off state within the last 30 minutes, along with information about those users (time, User Identifier value, status). The **`Update`** button becomes active every 30 seconds, so you can click it to refresh for the latest state.

![Real-time Exposure Status example](/files/c7JQpoRuuWsmdhYfMZ8t)

### Jira Integration Tab

You can manage Jira tickets linked to the Feature Flag within the Dashboard by integrating with Jira.

For more details, refer to the [Jira Integration](/en/external-link/jira-integration.md) document.

![Feature Flag with Jira ticket integrated](/files/SujkzaAzyieom4juyRSt)

### Change History Tab

Changes to the Feature Flag are recorded in chronological order.\
You can check the history of items created and edited by other collaborators through the Change History.

![](/files/WbuCi3KFP4iu7jKdzH71)

Click "View Details" to see the details of the content before and after the modification.

![Change History — View Details](/files/23XvIRwwNTv9aEutKGLM)

## Feature Flag Additional Features

Click the **`・・・`** button in the upper right corner of the detail screen to see the additional features available for the Feature Flag.

![](/files/XxwHfgVBqpKZOmnYEZJV)

### Edit Feature Flag Name

You can edit the Feature Flag name freely. Don't forget to click the **`Save`** button in the lower right corner after editing for changes to take effect.

![](/files/pughsWRZuV3Q8WD2yhaX)

### Duplicate Feature Flag

Creates a copy of the Feature Flag.\
The result of copying can be seen in the Feature Flag list, with "(Copy)" appended to the name. For example, if you copy a Feature Flag named "Search Algorithm Improvement," the copy will be named "Search Algorithm Improvement (Copy)."

### Archive Feature Flag

You can archive the Feature Flag if it is no longer needed.\
Since an archived Feature Flag cannot be used again, please decide carefully.

{% hint style="danger" %}
Before archiving, make sure to remove code related to the Feature Flag!

If left in place, you may encounter unintended errors.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.hackle.io/en/feature-flag/ff-sdp-editing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.