Roles and permissions
Five roles, each a set of capabilities — and checkboxes to adjust any member above or below their role.
Owner — everything, including transferring and deleting the workspace, and the subscription itself.
Admin — people, billing (packs and history), settings and keys.
Developer — API keys, webhooks and full generation; no billing, no people.
Creator — generates and publishes in the studio.
Viewer — reads the Library and the usage; cannot spend a credit.
Adjusting a member
In Members, the access editor shows every capability as a checkbox on top of the role: tick what the role lacks, untick what it has. You can only grant what you hold yourself, you can only manage people ranked below you, and nobody can give a role at or above their own. Transferring or deleting the workspace is never grantable.
Keys follow people
An API key inherits the permissions of the member who holds it: demote someone to Viewer and their keys stop generating, without you having to find and revoke them.
The subscription
Only the owner subscribes, upgrades, cancels, changes seats, sets up auto top-up or opens the billing portal — the card is theirs. Admins buy packs by hand and read the history; everyone else sees Billing as a notice.
Related
Still stuck?
Tell us what happened and we answer within a business day.