Work with a team organization
Create an organization, invite members, and safely separate workspaces, keys, and spending.
Last updated on
An organization is a shared team workspace. Chats, images, videos, API keys, usage, and balance belong to the active workspace, so check its name in the cabinet before starting work.
Create an organization
- Open Settings and find Organizations.
- Select Create organization, enter a recognizable name, and save.
- Select the new organization in the workspace switcher.
Your personal workspace remains available under the same account. Use the account menu to switch between it and organizations; after a switch, the cabinet loads the selected workspace's balance, keys, usage, and history.
Invite members
Open the intended organization's management view in Settings, choose a role, and use either method:
- an email invitation for a specific person;
- a one-use link that you deliver through your own communication channel.
Each member accepts the invitation from their own account. Never share a common password or complete API key with colleagues. If a link has been used, expired, or revoked, create a replacement instead of forwarding the old one.
Choose a role by the required action
Decide what the person needs to do before assigning a role:
| Required action | Suitable roles |
|---|---|
| Manage the organization, members, billing, keys, and workspace content | Owner or Admin |
| Manage balance and invoices and read usage without access to chats or keys | Billing |
| Create keys, work with API, chats, and images, and read usage | Developer |
| Work with chats and images without access to billing or keys | Member |
| Read available workspace data without making changes | Viewer |
Changing billing requires billing-management capability. Owner, Admin, and Billing have it; Viewer can only read the billing data available to that role. Grant the smallest role that supports the task and review it when responsibilities change.
Check the active workspace
The shared balance pays for chat, API, image, and video work inside the organization. API keys created while that organization is active belong to it, and Usage shows its requests and spending.
Create a separate key for each project or service and apply a spend limit. This produces clear attribution and lets you revoke one key without stopping other projects. Do not use a personal-workspace key for a team service or move an organization key into a personal project.
Understand chat visibility
A chat created in an organization belongs to the organization, not only to its creator. Members with chat-read access can see those conversations; the Billing role does not receive chat access.
Switch to the personal workspace or use a separate organization with the intended membership for private or isolated work. A separate API key inside the same organization separates spending but does not make that organization's chats private.