| name | apollo-enterprise-rbac |
| description | Enterprise role-based access control for Apollo.io.
Use when implementing team permissions, restricting data access,
or setting up enterprise security controls.
Trigger with phrases like "apollo rbac", "apollo permissions",
"apollo roles", "apollo team access", "apollo enterprise security".
|
| allowed-tools | Read, Write, Edit, Bash(kubectl:*), Bash(curl:*) |
| version | 1.13.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","apollo","security","rbac"] |
| compatibility | Designed for Claude Code, also compatible with Codex and OpenClaw |
Apollo Enterprise RBAC
Overview
Role-based access control for Apollo.io API integrations. Apollo API keys are all-or-nothing (standard vs master), so RBAC must be implemented in your application layer as a proxy between users and the Apollo API. This skill builds a permission matrix, scoped API key system, Express middleware, and admin audit endpoints.
Prerequisites
- Apollo master API key
- Node.js 18+ with Express
Instructions
Step 1: Define Roles and Permission Matrix
Map Apollo API operations to team roles. Apollo's API has two main categories:
- Read-only: search (free), enrichment (credits)
- Write: contacts CRUD, sequences, deals, tasks
export type Role = 'viewer' | 'analyst' | 'sales_rep' | 'sales_manager' | 'admin';
export interface Permission {
searchPeople: boolean;
searchOrganizations: boolean;
enrichPerson: boolean;
bulkEnrich: boolean;
enrichOrg: boolean;
manageContacts: boolean;
manageSequences: boolean;
manageDeals: ;
: ;
: ;
: ;
}
: <, > = {
: {
: , : , : ,
: , : , : ,
: , : , : ,
: , : ,
},
: {
: , : , : ,
: , : , : ,
: , : , : ,
: , : ,
},
: {
: , : , : ,
: , : , : ,
: , : , : ,
: , : ,
},
: {
: , : , : ,
: , : , : ,
: , : , : ,
: , : ,
},
: {
: , : , : ,
: , : , : ,
: , : , : ,
: , : ,
},
};