| name | clay-enterprise-rbac |
| description | Configure Clay workspace roles, team access control, and credit budget allocation.
Use when managing team access to Clay tables, setting per-user credit budgets,
or configuring workspace-level permissions for Clay.
Trigger with phrases like "clay SSO", "clay RBAC", "clay enterprise",
"clay roles", "clay permissions", "clay team access", "clay workspace".
|
| allowed-tools | Read, Write, Edit, Grep |
| version | 1.14.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","clay","rbac"] |
| compatibility | Designed for Claude Code, also compatible with Codex and OpenClaw |
Clay Enterprise RBAC
Overview
Control access to Clay tables, enrichment credits, and integrations at the team level. Clay uses a workspace model where team members are assigned Admin, Member, or Viewer roles. This skill covers role assignment, credit budget allocation, API key isolation, and audit procedures.
Prerequisites
- Clay Team or Enterprise plan
- Workspace admin privileges
- Understanding of team structure and data access needs
Instructions
Step 1: Define Role Matrix
Clay has three built-in roles with fixed permissions:
| Capability | Admin | Member | Viewer |
|---|
| Manage workspace members | Yes | No | No |
| Manage billing and credits | Yes | No | No |
| Create/delete tables | Yes | Yes | No |
| Run enrichments | Yes | Yes | No |
| Configure integrations | Yes | No | No |
| Export data | Yes | Yes | Yes |
| View all tables | Yes | Yes | Yes |
Recommended role assignments:
roles:
admin:
assign_to:
- Revenue Operations Lead
- GTM Engineering Lead
why: "Controls billing, integrations, and team access"
member:
assign_to:
- SDRs building prospect lists
- Growth
