> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/server-side/command-line-interface/ab-tasty-cli-reference-v1xx/feature-experimentation/feature-experimentation-user.md).

# user

## abtasty-cli feature-experimentation user create

#### NAME

`abtasty-cli feature-experimentation user create` - Create a user with right

#### SYNOPSIS

`abtasty-cli feature-experimentation user create [-d DATA_RAW | --data-raw = DATA_RAW]`

#### DESCRIPTION

Create a user with right in your account

#### EXAMPLES

```shell
abtasty-cli feature-experimentation user create -d DATA_RAW
```

```shell
abtasty-cli feature-experimentation user create -d "[{\"email\":\"example@flagship.io\",\"role\":\"VIEWER\"}]"
```

#### REQUIRED FLAGS

`--data-raw = _DATA_RAW_`

The raw data contains all the info to create your user with right, check the [Remote Control API documentation](https://docs.abtasty.com/server-side/remote-control-api.md) for more details

***

## abtasty-cli feature-experimentation user list

#### NAME

`abtasty-cli feature-experimentation user list` - List all users

#### SYNOPSIS

`abtasty-cli feature-experimentation user list [--output-format = OUTPUT_FORMAT [table|json|json-pretty]]`

#### DESCRIPTION

List all users in your account

#### EXAMPLES

```shell
abtasty-cli feature-experimentation user list
```

#### FLAGS

`--output-format = _OUTPUT_FORMAT_`

The output format for printing command output resources. The default is table. The supported formats are: json-pretty, table, json.

***

## flagship user edit

#### NAME

`abtasty-cli feature-experimentation user edit` - Edit a user with right

#### SYNOPSIS

`abtasty-cli feature-experimentation user edit [-d DATA_RAW | --data-raw = DATA_RAW]`

#### DESCRIPTION

Edit a user with right in your account

#### EXAMPLES

```shell
abtasty-cli feature-experimentation user edit -d DATA_RAW
```

#### REQUIRED FLAGS

`--data-raw = _DATA_RAW_`

The raw data contains all the info to edit your user with right, check the [Remote Control API documentation](https://docs.abtasty.com/server-side/remote-control-api.md) for more details

***

## abtasty-cli feature-experimentation user delete

#### NAME

`abtasty-cli feature-experimentation user delete` - Delete a user

#### SYNOPSIS

`abtasty-cli feature-experimentation user delete [-e EMAIL | --email = EMAIL]`

#### DESCRIPTION

Delete a user in your account

#### EXAMPLES

```shell
abtasty-cli feature-experimentation user delete -e EMAIL
```

#### REQUIRED FLAGS

`--email = _EMAIL_`

The email you want to delete


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.abtasty.com/server-side/command-line-interface/ab-tasty-cli-reference-v1xx/feature-experimentation/feature-experimentation-user.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
