Sign in
← AI PulseSep 10, 2026

Wire · news · Single-source brief

Claude API Reference Details RBAC Group Management

Anthropic's Claude API reference outlines endpoints for managing Role-Based Access Control (RBAC) Groups within a Claude Enterprise tenant, distinguishing between directly created and SCIM-provisioned groups.

By Illumora Editorial

Source · Sep 10, 2026, 5:35 PM · On Illumora · Sep 10, 2026, 5:38 PM

Media from the primary source — shown here so you can stay on Illumora.

Rewritten from one allowlisted primary — not independent enterprise reporting. Lanes →

Brief drafted by Illumora’s editorial model from the linked primary source. Ops desk reviews flagged pieces. How we write →

Read the source →Anthropic Docs (prompting) — RBAC Groups - Claude API Reference
Save

The Claude API Reference provides details on managing RBAC Groups within a Claude Enterprise tenant. These API endpoints allow for programmatic interaction with group functionalities, including creation, modification, and user management.

Key Points

  • The API enables listing existing RBAC Groups within a Claude Enterprise tenant.
  • New RBAC Groups can be created via the API, and these groups are assigned a source type of "direct."
  • RBAC Group names can be updated through the API, but groups provisioned by an identity provider (source type "scim") cannot be modified if SCIM provisioning is active.
  • RBAC Groups can be deleted, though "scim" source type groups cannot be deleted via the API if SCIM provisioning is active.
  • Users can be added to or removed from RBAC Groups, but membership changes for "scim" source type groups are restricted when SCIM provisioning is active.
  • The API indicates that the object type for RBAC Groups is consistently "rbac_group."
  • Role attachment to RBAC Groups is managed in admin settings and is read-only through this API.

Context

According to the Anthropic Docs, the API reference specifies how RBAC Groups are managed, differentiating between groups created directly within the organization's admin settings or via the API ("direct") and those provisioned by an identity provider ("scim"). This distinction affects which group attributes and memberships can be modified or deleted via the API.

Why It Matters

Builders using Claude Enterprise can integrate group management into their automated workflows, but they must account for the limitations imposed by SCIM provisioning. Understanding these distinctions is crucial for maintaining consistent access control policies and avoiding conflicts between API-driven changes and identity provider synchronization.

What To Do

  • Review the Claude API Reference for specific endpoint details on RBAC Group management.
  • Note the source type when interacting with RBAC Groups, especially when attempting to modify or delete them.
  • Test group creation and user assignment via the API in a controlled environment.
  • Compare API capabilities with the organization's identity provider setup to understand modification constraints for "scim" groups.