Organizations and workspaces

BuildBot separates who you are from where your work lives. If you’ve used GitHub or Vercel, the model will feel familiar: your account is an identity, an organization owns the work and the bill, and a workspace is where agents are built.

Thing	What it is	Like on GitHub
Account	You: your sign-in, profile and API keys.	Your user account
Organization	Owns workspaces and pays for them. Every plan is billed to an organization.	An organization
Workspace	Holds agents, projects, skills, commands, rules, MCPs and hooks. Belongs to exactly one organization.	A repository
Member	Someone invited to a workspace, with a role.	A collaborator

When you create an account, BuildBot creates a personal organization for you, with a default workspace inside it. A solo account is simply an organization of one: your plan, your usage and your workspaces all belong to it.

Your personal organization is always yours alone. It can’t be handed to someone else or merged with a team.

Once you belong to a team, an unused personal organization stays out of your way. If it has no content, no subscription, no API keys and no purchased credits, BuildBot doesn’t list it under Switch organization and opens your team when you sign in. It’s still there: Settings → Organizations → Use personal workspace opens it, and it shows up again as soon as you put something in it or leave your last team.

Every workspace belongs to exactly one organization, and everything in it (agents, projects, skills and the rest) belongs to that workspace. Work never crosses into another organization on its own: only people you invite can see a workspace, and only a share link you create makes something viewable outside it.

You can create more workspaces to separate clients, products or experiments. How many you can have depends on your organization’s plan.

You share a workspace by inviting people to it by email. Each person gets a role in that workspace only:

Role	Can
Viewer	Read everything in the workspace
Editor	Create and edit content
Admin	Manage members and workspace settings

Owners and admins of an organization are admins of every workspace in it, without being invited.

Workspaces in your personal organization share view-only access: everyone you invite there is a Viewer. Editing together needs a team organization, where people from outside the team can be at most Editors.

Inviting someone to one workspace gives them no access to your other workspaces or to your organization’s billing. Someone invited from outside your organization is shown as an Outside collaborator.

Invitations expire after 14 days, and you can remove a member at any time; they lose access immediately.

A team organization is an organization shared by several people, with its own workspaces and its own Team plan, billed per seat. You can belong to your personal organization and to any number of team organizations, and switch between them from your account menu at the bottom of the sidebar (Switch organization). The header always shows which organization and workspace you’re in; for your personal organization it shows just the workspace. Creating team organizations from the app is on the way; until then, invitations to your personal workspaces are view-only.

You can try BuildBot without an account. Guest mode keeps your work on our servers in a temporary account. When you sign up, your work comes with you; when you sign in to an existing account, you can bring all of it, uploaded documents included, into that account. Inactive guest work may be deleted, so sign up to keep it.

• Sharing and collaboration — when to share a link, export, or invite people
• How to think about Projects

If you’re an owner or admin of two organizations, you can move a workspace from one to the other in Settings → Workspace → Transfer workspace. Everything in it moves too: content, members, share links and history. Before you confirm, BuildBot shows what changes:

• If the destination already has a workspace with the same URL, the moved one gets a numbered URL (for example platform-2). Old links still redirect.
• People who aren’t in the destination organization become collaborators there: at most Editors in a team organization, Viewers in a personal one.
• API keys for the old organization stop reaching the workspace.

A workspace can’t be moved if it’s its organization’s default, if it’s archived, or if it would go over the destination plan’s limits. BuildBot lists each limit that’s in the way.