Agent skill · product strategy · jeremylongshore
anth-enterprise-rbac
Configure Anthropic enterprise organization management, Workspaces,
Why this skill is useful
Provides specific role-based access control patterns and API key management practices for Anthropic's platform that the AI wouldn't reliably generate on its own.
What it needs
Requires anthropic account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Anthropic Enterprise RBAC Overview Anthropic provides organization-level access control through Workspaces, API key scoping, and member roles via the Console at console.anthropic.com. Organization Structure Console Roles Role Capabilities ------ ------------- Owner Full access, billing, member management Admin Manage workspaces, API keys, view usage Developer Create/revoke own API keys, view own usage Billing View invoices and usage reports only Application-Level RBAC Key Management Best Practices Practice Implementation ---------- --------------- One key per service prod-auth-service, prod-search-service Rotate quarterly Calendar reminder + automated rotation Least privilege Dev workspace for dev keys only Audit trail Log which key made each request Revoke immediately On employee departure or compromise Error Handling Issue Cause Fix ------- ------- ----- Key works in dev, fails in prod Wrong workspace key Verify key belongs to prod workspace New team member can't access Not added to workspace Invite via Console > Members Usage not visible Viewing wrong workspace Switch workspace in Console Prerequisites Obtain the organization owner’s approved workspace map, role matrix, service inventory, key owners, rotation schedule, and incident/revocation contacts. Create isolated dev/staging workspaces with synthetic requests; production changes require an approved change record and least-privileged service identity. Define the allowed models, token/rate budgets, data classes, destinations, and redacted audit fields for each role and service. Instructions 1. Map each human and service to the minimum Console role and workspace required for its job. Separate development, staging, and production keys; store them only in the approved secret manager. 2. Enforce application RBAC before constructing a request, including model, token, rate, data-class, and destination checks. Treat unknown roles, stale memberships, and missing workspace mappings as deny. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/anth-enterprise-rbac