An organization owns members, product permissions, resources, API keys, and the calling wallet. Your account handles sign-in, your profile, and security. You can rename a personal organization or invite collaborators without moving its resources.
Switch or create organizations
- Sign in to Console and open the organization switcher at the top left.
- Select an organization or create a team organization. The full organization list includes your memberships and pending invitations.
- Confirm the organization name before opening Agents, Box, Powers, or Gateway.
Switching organizations clears the previous resource, Agent, and session selections. A direct link to an organization you can no longer access shows an access error instead of opening another organization. Free access in a new organization does not include a calling balance.
Understand roles
| Role | Permissions |
|---|---|
| Owner | Rename the organization; manage resources, projects, keys, and billing; invite admins and members; change non-owner roles or remove members. |
| Admin | Manage resources, projects, keys, and billing; invite or remove regular members. Cannot manage the owner or other admins, or rename the organization. |
| Member | View organization resources, usage, and billing, and use resources when product and runtime permissions allow. Cannot prepare instances, create projects, manage keys, or invite members. |
Organization roles do not override product restrictions. Admin access does not guarantee sufficient balance, available models, or a configured runtime.
Invite a collaborator
- An owner or admin opens Members, enters the collaborator’s email, and selects a role they are allowed to invite.
- The recipient signs in with a matching, verified email and accepts or declines the invitation in their organization list.
- If needed, the recipient starts email verification in account settings before handling the invitation.
Organization invitations are in-app invitations; no organization invitation email is sent. They expire after seven days. Pending invitations can be revoked. An invitation also stops granting access if its sender loses the required permission.
Use projects when needed
Products work without projects. To group related resources and historical usage, an owner or admin creates a project with a name, an organization-unique identifier using lowercase letters, numbers, and hyphens, and an optional description.
Switch project scope from the Agents or Box product page. Powers projects attribute calls; they do not create separate connection catalogs. A project filter never expands member or key permissions.
Archiving a project disables its services in Console and prevents new services and keys for that project. Archiving does not delete data, stop running resources, issue refunds, or change existing API key behavior. Use product controls to stop work and revoke keys to remove programmatic access. Unarchiving makes services accessible again, subject to their current authorization.
Leave or change access
Non-owners can leave from organization settings. The current owner cannot leave or be removed. Ownership transfer and organization deletion are not currently available.
A member’s organization keys stop working when they leave or are removed; rejoining does not restore old keys. Demoting an admin to member permanently revokes their previously created organization keys, even if they later become an admin again. Arrange replacement application keys when changing administrators.
Profile and security settings are in the account menu at the top right. Product calling balance is managed in organization Billing.