Answer: Structure groups by job function and use case rather than org hierarchy, starting with 4–6 groups (splitting only if usage patterns clearly diverge) and limiting to no more than 8–10 groups; gate high-intensity surfaces via custom roles assigned to each group. For group spend, assign group-level spend caps as a starting point, review group consumption weekly during initial rollout and monthly thereafter, and consider a "group owner" per department with a custom role granting Analytics (Can view) and optionally Billing (Can view). Status: Confirmed Entry: tool/claude-apps/admin-and-enterprise/role-based-access-groups Revision: 4 Digest: sha256:adc8dc9a7569bc88 (changes whenever the content changes) Timeline: Created: 2026-11-13T02:59:53Z Last changed: 2026-11-19T12:03:56Z (required org role for access: — → Custom) Last verified: 2026-11-20T12:07:39Z Next check: 2026-11-21T12:07:39Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Unit | Source | As of recommended starting group count | 4–6 | groups | [1] | 2026-11-20 maximum manageable groups | 8–10 | groups | [1] | 2026-11-20 initial rollout review cadence | weekly | | [1] | 2026-11-20 ongoing review cadence | monthly | | [1] | 2026-11-20 spend cap starting point | group-level spend caps | | [1] | 2026-11-20 group owner admin permission | Analytics (Can view) | | [1] | 2026-11-20 optional group owner permission | Billing (Can view) | | [1] | 2026-11-20 required org role for access | Custom | | [1] | 2026-11-20 Sources: [1] Anthropic. "Claude Enterprise consumption guide | Claude Help Center". https://support.claude.com/en/articles/14782391-claude-enterprise-consumption-guide Role: primary. Accessed: 2026-11-20T12:07:39Z Quote: "Start with 4–6 and split only if usage patterns clearly diverge." (Supports: recommended starting group count) Quote: "More than 8–10 groups becomes hard to manage." (Supports: maximum manageable groups) Quote: "Review group consumption weekly during initial rollout, monthly thereafter." (Supports: initial rollout review cadence, ongoing review cadence) Quote: "Assign group-level spend caps as a starting point, then override at the user level for outliers" (Supports: spend cap starting point) Quote: "create a custom role that grants the Analytics (Can view) admin permission" (Supports: group owner admin permission) Quote: "and optionally Billing (Can view) so they can see the Usage page" (Supports: optional group owner permission) Quote: "it only takes effect for members whose organization role is set to Custom" (Supports: required org role for access) Snapshot SHA-256: 6e7cb1d59aea0637d3a139f3d8f2a1809fc03a942fac66b33c1394704d9d595d (captured 2026-11-19T12:03:53Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-19T12:03:56Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:07:39Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:07:39Z Last attempt: 2026-11-20T12:07:39Z Notes and limitations: Extracted automatically from a single official source (section "Role-based access controls"). Related: https://latestn.com/tool/claude-apps/admin-and-enterprise/scanning-role-scope How do I control which roles skill and plugin scanning applies to in Claude? https://latestn.com/tool/claude-apps/admin-and-enterprise/scim-group-role-mapping How do I use SCIM to map IdP groups to Claude roles and keep them in sync? https://latestn.com/tool/claude-apps/admin-and-enterprise/seat-management-permissions Who can purchase seats or reassign seat types on a Claude Team plan? https://latestn.com/tool/claude-apps/admin-and-enterprise/retention-required-roles Who can configure custom data retention periods in Claude Enterprise? https://latestn.com/tool/claude-apps/admin-and-enterprise/review-export-survey-results How do I review and export survey responses in the Claude Admin console? https://latestn.com/tool/claude-apps/admin-and-enterprise/revoke-console-invitations How do I revoke a pending invitation in the Claude Console? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-19T12:03:56Z | changed | required org role for access: — → Custom | [1] 2026-11-19T12:03:56Z | changed | optional group owner permission: — → Billing (Can view) | [1] 2026-11-19T12:03:56Z | changed | group owner admin permission: — → Analytics (Can view) | [1] 2026-11-19T12:03:56Z | changed | spend cap starting point: — → group-level spend caps | [1] 2026-11-19T12:03:56Z | changed | ongoing review cadence: — → monthly | [1] 2026-11-19T12:03:56Z | changed | initial rollout review cadence: — → weekly | [1] 2026-11-19T12:03:56Z | changed | maximum manageable groups: — → 8–10 | [1] 2026-11-19T12:03:56Z | changed | group owner permissions: Analytics (Can view) → — | [1] 2026-11-19T12:03:56Z | changed | review cadence: Review group consumption weekly during initial rollout, monthly thereafter. → — | [1] 2026-11-19T12:03:56Z | changed | spend cap approach: Assign group-level spend caps as a starting point, then override at the user level for outliers → — | [1] 2026-11-19T12:03:56Z | changed | access gating example: only members of the "Engineering" group can access Claude Code → — | [1] 2026-11-19T12:03:56Z | changed | group proliferation limit: More than 8–10 groups becomes hard to manage. → — | [1] 2026-11-19T12:03:56Z | changed | recommended starting group count: Start with 4–6 → 4–6 | [1] 2026-11-19T12:03:56Z | changed | group structuring principle: Think about groups in terms of job function and use case, not organizational hierarchy. → — | [1] 2026-11-18T12:04:22Z | changed | spend cap approach: — → Assign group-level spend caps as a starting point, then override at the user level for outliers | [1] 2026-11-18T12:04:22Z | changed | recommended starting group count: — → Start with 4–6 | [1] 2026-11-18T12:04:22Z | changed | custom role requirement: Custom → — | [1] 2026-11-18T12:04:22Z | changed | review cadence: weekly during initial rollout, monthly thereafter → Review group consumption weekly during initial rollout, monthly thereafter. | [1] 2026-11-18T12:04:22Z | changed | spend cap starting point: Assign group-level spend caps as a starting point → — | [1] 2026-11-18T12:04:22Z | changed | starting group count: 4–6 → — | [1] 2026-11-18T12:04:22Z | changed | group proliferation limit: 8–10 → More than 8–10 groups becomes hard to manage. | [1] 2026-11-18T12:04:22Z | changed | group structuring principle: job function and use case, not organizational hierarchy → Think about groups in terms of job function and use case, not organizational hierarchy. | [1] 2026-11-15T12:06:48Z | changed | custom role requirement: — → Custom | [1] 2026-11-15T12:06:48Z | changed | group owner permissions: — → Analytics (Can view) | [1] 2026-11-15T12:06:48Z | changed | review cadence: — → weekly during initial rollout, monthly thereafter | [1] 2026-11-15T12:06:48Z | changed | spend cap starting point: — → Assign group-level spend caps as a starting point | [1] 2026-11-15T12:06:48Z | changed | access gating example: — → only members of the "Engineering" group can access Claude Code | [1] 2026-11-15T12:06:48Z | changed | starting group count: — → 4–6 | [1] 2026-11-15T12:06:48Z | changed | group proliferation limit: — → 8–10 | [1] 2026-11-15T12:06:48Z | changed | group structuring principle: — → job function and use case, not organizational hierarchy | [1] 2026-11-15T12:06:48Z | changed | Group owner permissions: Analytics (Can view) → — | [1] 2026-11-15T12:06:48Z | changed | Review cadence: Review group consumption weekly during initial rollout, monthly thereafter. → — | [1] 2026-11-15T12:06:48Z | changed | Spend cap starting point: Assign group-level spend caps as a starting point → — | [1] 2026-11-15T12:06:48Z | changed | Access gating mechanism: Access is granted by the custom roles you assign to each group → — | [1] 2026-11-15T12:06:48Z | changed | Group proliferation limit: More than 8–10 groups becomes hard to manage. → — | [1] 2026-11-15T12:06:48Z | changed | Recommended starting group count: Start with 4–6 → — | [1] 2026-11-15T12:06:48Z | changed | Group structuring principle: Think about groups in terms of job function and use case, not organizational hierarchy. → — | [1] 2026-11-13T02:59:53Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-apps/admin-and-enterprise/role-based-access-groups/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-apps/admin-and-enterprise/role-based-access-groups POST: https://latestn.com/dispute/tool/claude-apps/admin-and-enterprise/role-based-access-groups with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-apps/admin-and-enterprise/role-based-access-groups?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I structure groups and manage group spend with role-based access controls in Claude Enterprise? Revision 4, last verified 2026-11-20T12:07:39Z. https://latestn.com/tool/claude-apps/admin-and-enterprise/role-based-access-groups (accessed 2026-11-21T10:01:29Z). @misc{LatestN_tool_claude_apps_admin_and_enterprise_role_based_access_groups_r4, title = {How do I structure groups and manage group spend with role-based access controls in Claude Enterprise?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-apps/admin-and-enterprise/role-based-access-groups}}, note = {Revision 4; digest sha256:adc8dc9a7569bc88; last verified 2026-11-20T12:07:39Z; accessed 2026-11-21T10:01:29Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-apps/admin-and-enterprise/role-based-access-groups