> 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/list-seats-usage.md).

# List Seats Usage

Get a list of tenant members (seats), including assigned policies and seat-denied invitees.

To remove a specific member returned from this call use the [Remove Member](/reference/remote-access-and-apis/api-examples/remove-member.md) API call.

#### Endpoint

GET `/api/rbac/seatsUsage`

#### 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                                      |
| `X-Tenant-UUID` | Yes      | Tenant UUID (from the app URL `tenantUUID=…`, or Settings → Access) |

#### Response

**Response Schema**

```json
[
  {
    "email": "string",
    "lastLogin": "string",
    "isActive": true,
    "firstLogin": "string",
    "roleType": "string",
    "policyUUIDs": ["string"],
    "policyNames": ["string"],
    "ssoDriven": false
  }
]
```

Field Descriptions

<table data-header-hidden data-search="false"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td>Field</td><td>Type</td><td>Description</td></tr><tr><td><code>email</code></td><td>string</td><td>Member email</td></tr><tr><td><code>lastLogin</code></td><td>string | null</td><td>ISO 8601 last login / last seen time</td></tr><tr><td><code>firstLogin</code></td><td>string | null</td><td>ISO 8601 first login time</td></tr><tr><td><code>isActive</code></td><td>boolean</td><td><code>true</code> for active members; <code>false</code> for seat-blocked invitees</td></tr><tr><td><code>roleType</code></td><td>string</td><td>Effective role: <code>admin</code>, <code>write</code>, or <code>read</code></td></tr><tr><td><code>policyUUIDs</code></td><td>array</td><td>Assigned policy UUIDs</td></tr><tr><td><code>policyNames</code></td><td>array</td><td>Assigned policy names (same order as UUIDs)</td></tr><tr><td><code>ssoDriven</code></td><td>boolean</td><td>Whether policies are driven by SSO</td></tr></tbody></table>

#### Examples

**Basic Request**

```bash
curl -L \
  --request GET \
  --url 'https://api.groundcover.com/api/rbac/seatsUsage' \
  --header 'Authorization: Bearer <YOUR_API_KEY>' \
  --header 'X-Tenant-UUID: <YOUR_TENANT_UUID>'
```

**Response Example**

```json
[
  {
    "email": "user@example.com",
    "lastLogin": "2026-09-28T13:45:56.447898Z",
    "isActive": true,
    "firstLogin": "2023-10-02T13:38:33.543846Z",
    "roleType": "admin",
    "policyUUIDs": ["6180b868-315b-4540-852f-3e0e942f5de3"],
    "policyNames": ["groundcover Admin"],
    "ssoDriven": false
  },
  {
    "email": "editor@example.com",
    "lastLogin": "2026-09-27T13:00:47.934825Z",
    "isActive": true,
    "firstLogin": "2024-06-06T11:31:49.856862Z",
    "roleType": "write",
    "policyUUIDs": ["cb7d55ac-10bb-42ec-84cc-1a00f460cf2d"],
    "policyNames": ["groundcover Editor"],
    "ssoDriven": false
  }
]
```


---

# 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/list-seats-usage.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.