Organizations & invitations
Team roles, organization switching, and invitation flows.
A shared workspace for your team
Organizations own API keys, prepaid credit, usage records, and membership. Select the active organization near the top of the console sidebar. Every view and action is scoped to that organization.
Membership is checked on the server for each organization-scoped request. Changing a URL or passing another organization ID does not grant access.
Roles and permissions
| Action | Owner | Admin | Member |
|---|---|---|---|
| View usage, balance, masked keys | Yes | Yes | Yes |
| Create/revoke API keys | Yes | Yes | No |
| Add credit | Yes | Yes | No |
| Invite/remove members | Yes | Yes | No |
| Change non-owner roles | Yes | Yes | No |
| Rename organization | Yes | No | No |
Owners cannot be removed or demoted through the member-management flow. Ownership transfer is not currently available. Individual API keys are bearer credentials: anyone holding one can spend within its limits, regardless of their console role.
Invite a teammate
- Open Members in the correct organization.
- Enter the teammate’s email and choose Member or Admin. Start with Member when management access is unnecessary.
- Create the invitation. A link is sent to the invited address; owners and admins can also copy it.
- The recipient signs in with the invited email and accepts. Membership is created only after email verification.
Invitation lifecycle
Organization invitations expire after 7 days. Pending invitations can be cancelled from Members. Cancel a pending invitation before sending a replacement to the same address. Expired or withdrawn links cannot grant access.
Public registration does not require a platform invitation. Verified users can create their own organizations. Optional referral links can grant access to an offer; they never grant membership in somebody else’s organization.
Good organization hygiene
- Use a separate key for each production service and development environment.
- Review admin access and unused invitations periodically.
- Rotate keys when staff or deployment responsibilities change.
- Inspect the Usage page by model and key before increasing spend limits.