| name | deepgram-enterprise-rbac |
| description | Configure enterprise role-based access control for Deepgram integrations.
Use when implementing team permissions, managing API key scopes,
or setting up organization-level access controls.
Trigger: "deepgram RBAC", "deepgram permissions", "deepgram access control",
"deepgram team roles", "deepgram enterprise", "deepgram key scopes".
|
| allowed-tools | Read, Write, Edit, Bash(curl:*) |
| version | 1.13.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","deepgram","api","rbac","enterprise"] |
| compatibility | Designed for Claude Code |
Deepgram Enterprise RBAC
Overview
Role-based access control for enterprise Deepgram deployments. Maps five application roles to Deepgram API key scopes, implements scoped key provisioning via the Deepgram Management API, Express permission middleware, team management with auto-provisioned keys, and automated key rotation.
Deepgram Scope Reference
| Scope | Permission | Used By |
|---|
member | Full access (all scopes) | Admin only |
listen | STT transcription | Developers, Services |
speak | TTS synthesis | Developers, Services |
manage | Project/key management | Admin |
usage:read | View usage metrics | Analysts, Auditors |
keys:read | List API keys | Auditors |
keys:write | Create/delete keys | Admin |
Instructions
Step 1: Define Roles and Scope Mapping
interface Role {
name: string;
deepgramScopes: string[];
keyExpiry: number;
description: string;
}
const ROLES: Record<string, Role> = {
admin: {
name: 'Admin',
deepgramScopes: ['member'],
keyExpiry: 90,
description: ,
},
: {
: ,
: [, ],
: ,
: ,
},
: {
: ,
: [],
: ,
: ,
},
: {
: ,
: [],
: ,
: ,
},
: {
: ,
: [, ],
: ,
: ,
},
};