> For the complete documentation index, see [llms.txt](https://docs.omics.ai/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omics.ai/products/command-line-interface/reference/workbench/namespaces-members-add.md).

# namespaces members add

Add a member to a namespace

## Synopsis

```shell
omics workbench namespaces members add
  (--email EMAIL | --id USER_ID)
  --role ROLE
  [--namespace NAMESPACE_ID]
```

## Description

Add a user to a namespace with a specified role. The user must already be registered in Workbench. Identify the user by either their email address or user ID.

If the user is already a member of the namespace with the same role, the existing membership is returned. If the user is already a member with a different role, a conflict error is returned.

## Examples

### Add a member by email

```shell
omics workbench namespaces members add --email user@example.com --role ADMIN
```

### Add a member by user ID

```shell
omics workbench namespaces members add --id bcd869ca-8a06-4426-a94d-43f9d91e937d --role ADMIN
```

### Add a member to a specific namespace

```shell
omics workbench namespaces members add \
  --email user@example.com \
  --role ADMIN \
  --namespace bcd869ca-8a06-4426-a94d-43f9d91e937d
```

## Flags:

### `--email`=`EMAIL`

The email address of the user to add. Mutually exclusive with `--id`.

### `--id`=`USER_ID`

The user ID (UUID) of the user to add. Mutually exclusive with `--email`.

### `--role`=`ROLE`

**Required.** The role to assign to the member (e.g. `ADMIN`).

### `--namespace`, `-n`=`NAMESPACE_ID`

The namespace ID. Defaults to the active namespace. The namespace ID can be retrieved from the [namespaces list](/products/command-line-interface/reference/workbench/namespaces-list.md) command.


---

# 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.omics.ai/products/command-line-interface/reference/workbench/namespaces-members-add.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.