OpenParable
Skip to content
← Back to skills

Clade Enterprise Rbac

Apps & Automation
clade-enterprise-rbac

Clade Enterprise Rbac is an Agent Skill for apps & automation published in the jeremylongshore/claude-code-plugins-plus-skills repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Manage Anthropic workspaces, API keys, team access, and spending limits Use when working with enterprise-rbac patterns. for enterprise Claude deployments. Trigger with "anthropic workspace", "anthropic team management", "claude enterprise", "anthropic api key management".

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/HEAD/plugins/saas-packs/claude-pack/skills/clade-enterprise-rbac/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/clade-enterprise-rbac, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Anthropic Enterprise & Access Management

Overview

Anthropic uses Organizations and Workspaces for access control. API keys are scoped to workspaces.

Organization Structure

Organization (your-company)
├── Workspace: Production
│   ├── API Key: prod-backend (Tier 4)
│   └── API Key: prod-frontend-proxy (Tier 2)
├── Workspace: Staging
│   └── API Key: staging-all (Tier 2)
└── Workspace: Development
    └── API Key: dev-team (Tier 1)

API Key Best Practices

PracticeWhy
One key per service/environmentIsolate blast radius
Name keys descriptivelyprod-recommendation-service not key-1
Set spending limits per keyPrevent runaway costs from bugs
Rotate quarterlyReduce exposure window
Never share dev and prod keysDifferent rate limit tiers

Spending Limits

Set in Anthropic Console → Settings → Limits:

  • Monthly spend limit: Hard cap on total spend
  • Per-key limits: Not yet available — use separate workspaces

Access Control Checklist

  • Separate workspaces for dev/staging/prod
  • Separate API keys per service
  • Spending alerts configured
  • Key rotation schedule (90 days)
  • Offboarding process: revoke keys when team members leave
  • Audit log review (Console → Logs)

Output

  • Separate workspaces for production, staging, and development
  • Dedicated API keys per service/environment with descriptive names
  • Spending limits and alerts configured
  • Key rotation schedule established (90-day cycle)
  • Access control checklist completed

Error Handling

ErrorCauseSolution
API ErrorCheck error type and status codeSee clade-common-errors

Examples

See Organization Structure diagram, API Key Best Practices table, and Access Control Checklist above.

Resources

Next Steps

See clade-migration-deep-dive for migrating from other LLM providers.

Prerequisites

  • Anthropic Organization account at console.anthropic.com
  • Admin access to create workspaces and API keys
  • Understanding of environment isolation requirements

Instructions

Step 1: Review the patterns below

Each section contains production-ready code examples. Copy and adapt them to your use case.

Step 2: Apply to your codebase

Integrate the patterns that match your requirements. Test each change individually.

Step 3: Verify

Run your test suite to confirm the integration works correctly.