Shared workspaces with members, roles, and their own resources.
What a team owns
A team is the unit of ownership on inference shell. Apps, agents, flows, knowledge, vaults, secrets, and API keys all belong to a team, and the team's username is the namespace its published work appears under (acme/report-writer).
Your personal team is created with your account and behaves like any other team with one member. Shared teams add members and roles on top.
Roles
| Role | Can do |
|---|---|
| Owner | Everything, including team settings, usage policy, and deleting the team |
| Admin | Manage members, billing, secrets, and vaults |
| Member | Use and build with the team's resources |
Set roles on the members page in team settings.
Inviting people
Admins and owners invite by email from settings → team → members. Invitees get an email with accept/decline links; pending invites count toward the team size limit.
If the team belongs to an organization, invites are bounded by the org perimeter: you can invite people who are already part of the organization (a managed account or a member of another org team). Bringing in someone from outside the organization requires an org admin — a team inside an org can't become a side door into it.
Team API keys
API keys created in settings → team → api keys authenticate as the team and are visible to every member. Use them for CI, servers, and anything that should act as the team rather than as a person. Keys minted by the CLI's device login act as you instead and follow you across your teams.
Switching teams
The team switcher at the top of the sidebar lists your personal team, your organization's teams grouped under the organization's name, and any standalone teams. Switching reloads the workspace in the selected team's context.
Deleting
Team owners can delete a shared team from its settings. Deleting your account removes only you and your personal workspace — shared teams you belong to are never touched by account deletion.