Agent skill · marketing growth · jeremylongshore
clay-enterprise-rbac
Configure Clay workspace roles, team access control, and credit budget
Why this skill is useful
Provides specific role assignment strategies and API key management practices for Clay that the AI wouldn't reliably generate on its own.
What it needs
Requires clay account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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: Step 2: Invite and Manage Team Members In Clay UI: Settings > Members > Invite Best practices: Use company email addresses (not personal) Start new members as Viewers until they complete Clay training Audit member list quarterly -- remove departed employees immediately Step 3: Isolate API Keys by Integration Create separate API keys for each downstream system to enable independent revocation: Step 4: Set Credit Budget Controls Since Clay doesn't have per-user credit budgets natively, implement controls at the table level: Step 5: Quarterly Access Audit Error Handling Issue Cause Solution ------- ------- ---------- 403 on table creation User is Viewer role Upgrade to Member role Credits exhausted mid-campaign No budget cap on table Set maxrows on table Integration key rejected Key was revoked Generate new key, update integration config Unauthorized data export Viewer exported sensitive data Review export audit log Former employee still has access No offboarding process Immediate removal on departure Output Publish a redacted access-and-budget review that identifies workspace/table roles, privileged integrations, data-export boundaries, cr …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clay-enterprise-rbac