How accounts, teams, and organizations fit together.
The hierarchy
inference shell has three layers of ownership:
| Layer | What it is | What it owns |
|---|---|---|
| You | Your account | Profile, sign-in security, sessions, notification preferences, connected apps |
| Team | A shared workspace | Apps, agents, flows, knowledge, vaults, API keys, members, billing |
| Organization | A company layer above teams | Org-wide billing, usage policy, managed accounts, org admins |
Everything you build lives in a team. Every account starts with a personal team — a private workspace that works exactly like a shared team, with you as its only member. Teams can optionally belong to an organization, which is how companies run many teams under one bill and one governance policy.
Settings follow the hierarchy
Open settings and you'll see one tab per layer:
| Tab | Contents |
|---|---|
| you | Profile, security, sessions, connected apps, notifications, data & privacy |
| your team's name | Team profile, members, API keys, usage policy, billing |
| your org's name | Organization overview, usage policy, billing (org admins) |
The you tab is identical whichever team you're in. The team tab follows the team switcher. The organization tab appears when your current team belongs to one; on a standalone team it offers to create an organization instead.
Pages never mix layers: an org-billed team's billing page points you to organization billing rather than rendering the org's numbers under a team heading.
Which one am I acting as?
Your current team (the switcher in the sidebar) decides where new work lands and whose resources you see. Switching teams switches the whole workspace: apps, credentials, knowledge, and billing context all follow the selected team.
Things that never switch: your profile, your sessions, your notification preferences, and personal connections you've authorized (though each personal connection is usable only in the team where you connected it — see credentials).
Next
- Teams — members, roles, and invites
- Organizations — the company layer
- Usage policy — governing what teams can use