> 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/ab-test/ab-override.md).

# Override

> 👍 The Override tab is supported in both the Production Environment and the Development Environment.

## Overview

The Override feature is a feature that configures a user to be exposed to a specific test group. You can configure it in the `Override` tab on the A/B Test detail page.

## Override use cases

During an A/B Test in the Production Environment, it can be used to force-assign a specific user to a specific group. However, the most useful way to use it is for QA (Quality Assurance) purposes before starting an A/B Test in the Production Environment.

Typical use cases are as follows:

1. Verify that the UI, features, logic, etc. subject to the A/B Test have been correctly applied for each test group.
2. Validate that other features within the service unrelated to the A/B Test are working without issues.

> 🚧 For QA purposes, set traffic allocation to 0 in the Production Environment.
>
> If traffic allocation in the Production Environment is set to a value greater than 0%, users who are not Override targets may be assigned to Variation B, even in the Development Environment.
>
> This is because the traffic allocation value in the Production Environment is also applied to the Development Environment, and when a traffic allocation value exists, the Treatment may be exposed to users who are not Override targets according to Hackle's variation distribution logic.
>
> Therefore, to prevent users who are not Override targets from being exposed to the Treatment, traffic allocation must be set to 0.

## How to configure Override

The Override feature settings in the Development Environment and Production Environment are not compatible with each other. That is, even for the same A/B Test, they must be configured independently for each environment.\
Environment information can be checked in the header area of the Dashboard.

### 1. Enter a user identifier value

Once you decide which test group to assign the user to, enter the **`user identifier value`** in the input field for that test group and press **`Enter`**.

![How to delete a user](/files/pwWbd4aQcRjObWqz4lB9)

* To delete a user who has already been force-assigned, click the **`x`** button to the right of the **`user identifier value`**.
* To delete all users registered in a test group, click the **`x`** button to the right of the input field for that test group.

### 2. Save

Changes are saved only when you click the `Save` button in the upper right of the Override tab.

### 3. Verify

After completing the integration with the Hackle platform, run the A/B Test subject using the identifier of the user saved in each group and verify that the intended content appears for each test group.

> 🚧 Check the A/B Test status.
>
> Override can be verified only when the test is in **Draft** or **Running** status.\
> It cannot be verified when the test is in Completed or Archived status.


---

# 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/ab-test/ab-override.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.