Agent skill · marketing growth · jeremylongshore
ideogram-enterprise-rbac
Map Ideogram Owner, Admin, and Member roles to application-owned tenant, budget, key, media, publishing, and audit permissions. Use when designing or reviewing enterprise access control. Trigger with "design Ideogram RBAC", "audit Ideogram team roles", or "separate Ideogram duties".
Why this skill is useful
Adds executable scripts for implementing team-based access control and budget management for Ideogram's API that are not covered in public documentation.
What it needs
Requires ideogram account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Ideogram Enterprise Access Control Overview Keep Ideogram team administration distinct from application authorization. Vendor roles govern a shared team boundary, while the application must enforce tenant, use-case, spend, upload, generation, review, publication, retention, and incident permissions. Prerequisites Ideogram team inventory, role holders, keys, billing owner, environments, and emergency contacts. Application identity provider, tenant model, service identities, permission catalog, and audit requirements. Joiner, mover, leaver, key rotation, access review, and break-glass processes. Current Contract Ideogram documents Owner, Admin, and Member team roles. Team members share keys, credits, and billing context; separate keys do not inherently provide per-user or per-environment vendor budgets. Avoid inventing finer Ideogram permissions that the application must actually enforce. Authentication Store each server-side IDEOGRAMAPIKEY in the approved secret manager and send it only as Api-Key to https://api.ideogram.ai. Users authenticate to the application; only constrained service identities reach the vendor adapter. Instructions 1. Inventory vendor role holders, keys, credit authority, environments, application roles, service identities, and asset stores. 2. Define vendor Owner, Admin, and Member responsibilities from current first-party documentation. 3. Build an application permission matrix for request, upload, transform, train, spend, review, publish, export, delete, key administration, and incident actions. 4. Enforce tenant and environment scope at the gateway, queue, async state, webhook, storage, and publisher. 5. Separate requester, approver, publisher, billing administrator, key administrator, and auditor where risk warrants. 6. Test denied access, cross-tenant object access, wrong-environment key use, leaver removal, key rotation, and break-glass expiry. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/ideogram-enterprise-rbac