Workspaces & organizations
A workspace is one organization (tenant). Everything — telemetry and the Brain — is scoped to the workspace you're in. Workspaces are fully isolated from each other by row-level security: nothing crosses between them.
One login, many workspaces
You can belong to more than one organization with a single account. When you do, a workspace switcher appears in the sidebar footer — pick a workspace and the entire console re-scopes to it (dashboard, entities, and the Brain). With one workspace there's no switcher, just the name.
Creating another organization
- New, separate org: sign up with a different email. A signup with no pending invite auto-provisions a fresh organization with you as its admin (14-day trial).
- Join an existing org: an admin invites your email; you join on sign-up (or immediately, if you already have an account) with the role they chose.
Inviting people & roles
From Plan & people (or Admin), invite by email and assign a role:
- Owner / Admin — manage the org, people, plan and keys.
- Manager — see the whole fleet, no org management.
- Viewer — see only their own usage and knowledge (optionally a department, if they administer one).
Machines and workspaces
A machine's ingest key belongs to one organization, so an enrolled machine reports to exactly one workspace. The agent ships all AI work on that machine to whichever org its key belongs to — so for clean separation, enroll a separate machine (or a separate agent home via TB_HOME) per organization rather than pointing one machine at two. Mint each org's key from its Onboarding / Admin → Keys.
Seeing across organizations
Switching workspaces is how you read each org's full console. A workspace's data never appears in another's — by design.