Beta › Organization › RBAC Roles › Permissions
List RBAC Role Permissions
GET /v1/organizations/rbac_roles/\{role_id\}/permissions
List the permissions an RBAC Role grants.
The RBAC Roles API is available to Claude Enterprise organizations only.
Path parameters
role_id: stringID of the RBAC Role.
Query parameters
limit: optional numberNumber of items to return per page.
Defaults to
20. Ranges from1to1000.default: 20, maximum: 1000, minimum: 1
page: optional stringOptionally set to the
next_pagetoken from the previous response.
Returns
data: array of BetaRBACRolePermissiontype: "rbac_role_permission"Object type.
For RBAC Role Permissions, this is always
"rbac_role_permission".default: rbac_role_permission
action: stringAction the permission grants on the resource.
The vocabulary follows the resource: an
organizationgrant carries a product-feature entitlement (for examplechat), an admin-panel permission entitlement (permission_*), or a blanket capability-access mode —capability_access_allgrants every product-feature entitlement, andcapability_access_all_gagrants the generally-available subset as it stands at permission-check time; neither mode grants model-access entitlements. A consumer enumerating a role's per-feature grants should treat a blanket row as granting every product-feature entitlement it covers, or it will under-report the role's effective access. Aconnector_toolgrant carries a tool-access action (useoralways_allow); aconnector_scopegrant carries the scope actiongrant(the role may receive the named OAuth scope when tokens are minted for the connector);connectorandall_connectorsgrants carry a tool-access action, the scope action, or an authentication-method action (interactiveormanaged).resource: object or object or object or 2 moreWhat the permission applies to.
A tagged union:
typenames the kind of resource and determines which identifier fields are present.Organization objecttype: "organization"Kind of resource the permission applies to.
default: organization
organization_id: stringUUID of the organization the permission applies to.
ConnectorTool objecttype: "connector_tool"Kind of resource the permission applies to.
default: connector_tool
connector_id: stringID of the connector the permission applies to.
tool_name: stringPublished name of the connector tool the permission applies to.
When the published name contains characters outside
[a-zA-Z0-9_-](or collides with a reserved form), it is server-encoded into a stable\{prefix\}_\{32-hex\}form — a shortened readable prefix of the name plus a hash — from which the published name is not recoverable.
ConnectorScope objecttype: "connector_scope"Kind of resource the permission applies to.
default: connector_scope
connector_id: stringID of the connector the permission applies to.
scope: stringOAuth scope the permission names — the role may receive this scope when tokens are minted for the connector.
Subject to the same encoding rule as
tool_name: a scope containing characters outside[a-zA-Z0-9_-](or colliding with a reserved form) appears server-encoded in a stable\{prefix\}_\{32-hex\}form. OAuth scopes routinely contain:and/, so most appear encoded.
Connector objecttype: "connector"Kind of resource the permission applies to.
default: connector
connector_id: stringID of the connector the permission applies to.
AllConnectors objecttype: "all_connectors"Kind of resource the permission applies to.
default: all_connectors
has_more: booleanIndicates whether there are more results beyond this page.
next_page: string or nullOpaque cursor for the next page. Pass as the
pageparameter on the next request.
Example
curl https://api.anthropic.com/v1/organizations/rbac_roles/$ROLE_ID/permissions \
-H 'anthropic-version: 2023-06-01' \
-H 'anthropic-beta: ce-user-management-2026-07-13' \
-H "X-Api-Key: $ANTHROPIC_API_KEY"Response (200)
{
"data": [
{
"action": "use",
"resource": {
"organization_id": "3c4f5e6d-7a8b-49c0-9d1e-2f3a4b5c6d7e",
"type": "organization"
},
"type": "rbac_role_permission"
}
],
"has_more": true,
"next_page": "eyJjdXJzb3IiOiAicmJhY19yb2xlXzAxIn0"
}