# Users ## List organization users ### Path Parameters ### Query Parameters ### Header Parameters ### Returns ### Example #### Response ## Domain Types ### User List Response
The whole hunk
155 lines, first recorded
/
lines
The first capture of this source. The page was already there, and this is what it said.
---
title: Users
url: https://platform.claude.com/docs/en/api/compliance/organizations/users
---
# Users
## List organization users
**get** `/v1/compliance/organizations/{org_uuid}/users`
List current user members of an organization.
### Path Parameters
- `org_uuid: string`
The organization UUID
### Query Parameters
- `limit: optional number`
Maximum results (default: 500, max: 1000)
- `page: optional string`
Opaque pagination token from a previous response's `next_page` field. Pass this to retrieve the next page of results. Clients should treat this value as an opaque string and not attempt to parse or interpret its contents, as the format may change without notice.
### Header Parameters
- `"x-api-key": optional string`
### Returns
- `data: array of object { id, created_at, email, 2 more }`
List of current organization members sorted by organization join date ascending
- `id: string`
User identifier (tagged ID)
- `created_at: string`
User account creation timestamp
- `email: string`
User's current email address
- `full_name: string`
User's current full name
- `organization_role: "admin" or "billing" or "claude_code_user" or 6 more`
User's built-in role within the organization. This is distinct from any custom RBAC roles that may also be assigned.
- `"admin"`
- `"billing"`
- `"claude_code_user"`
- `"developer"`
- `"managed"`
- `"membership_admin"`
- `"owner"`
- `"primary_owner"`
- `"user"`
- `has_more: boolean`
Whether more records exist beyond the current result set
- `next_page: string or null`
Token to retrieve the next page. Use this as the 'page' parameter in your next request
### Example
```http
curl https://api.anthropic.com/v1/compliance/organizations/$ORG_UUID/users \
-H "Authorization: Bearer $ANTHROPIC_COMPLIANCE_API_KEY"
```
#### Response
```json
{
"data": [
{
"id": "user_01WCz1FkmYMm4gnmykNKUu3Q",
"created_at": "2025-03-12T18:22:41.123456Z",
"email": "[email protected]",
"full_name": "Jane Doe",
"organization_role": "admin"
}
],
"has_more": true,
"next_page": "cGFnZV90b2tlbl9leGFtcGxlXzE3MzQ1Njc4OTA="
}
```
## Domain Types
### User List Response
- `UserListResponse object { id, created_at, email, 2 more }`
User member information for compliance responses.
- `id: string`
User identifier (tagged ID)
- `created_at: string`
User account creation timestamp
- `email: string`
User's current email address
- `full_name: string`
User's current full name
- `organization_role: "admin" or "billing" or "claude_code_user" or 6 more`
User's built-in role within the organization. This is distinct from any custom RBAC roles that may also be assigned.
- `"admin"`
- `"billing"`
- `"claude_code_user"`
- `"developer"`
- `"managed"`
- `"membership_admin"`
- `"owner"`
- `"primary_owner"`
- `"user"`