> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/reference/remote-access-and-apis/api-examples/remove-member.md).

# Remove Member

Remove a member from a tenant. This deletes their tenant role and clears their policies for that tenant. If the email is only on the seat-denied list, it is cleared from that list instead.

You cannot remove yourself.\
\
To get a list of all tenant members, you can use the [List Seats Usage](/reference/remote-access-and-apis/api-examples/list-seats-usage.md) API call

#### Endpoint

POST `/api/rbac/member/remove`

#### Authentication

This endpoint requires API Key authentication via the Authorization header. The caller must have the **admin** role on the tenant.

#### Headers

| Header          | Required | Description                                                         |
| --------------- | -------- | ------------------------------------------------------------------- |
| `Authorization` | Yes      | Bearer token with your API key                                      |
| `Content-Type`  | Yes      | Must be `application/json`                                          |
| `X-Tenant-UUID` | Yes      | Tenant UUID (from the app URL `tenantUUID=…`, or Settings → Access) |

#### Request Body

```json
{
  "email": "string"
}
```

Parameters

| Parameter | Type   | Required | Description                   |
| --------- | ------ | -------- | ----------------------------- |
| `email`   | string | Yes      | Email of the member to remove |

#### Response

On success the response body is empty (`200`).

| Status | Meaning                                               |
| ------ | ----------------------------------------------------- |
| `200`  | Member removed (or cleared from the seat-denied list) |
| `400`  | Bad request, or caller tried to remove themselves     |
| `403`  | Caller is not an admin                                |
| `404`  | Member not found in this tenant                       |

Removal is scoped to `X-Tenant-UUID`. The user may still belong to other tenants.

#### Examples

**Basic Request**

```bash
curl -L \
  --request POST \
  --url 'https://api.groundcover.com/api/rbac/member/remove' \
  --header 'Authorization: Bearer <YOUR_API_KEY>' \
  --header 'Content-Type: application/json' \
  --header 'X-Tenant-UUID: <YOUR_TENANT_UUID>' \
  --data-raw '{"email":"user@example.com"}'
```


---

# 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.groundcover.com/reference/remote-access-and-apis/api-examples/remove-member.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.