Workspaces

A workspace is the shared container that everything else hangs off of. It groups your canvases, the people who can access them, and the workspace-scoped credentials your nodes use at runtime. Access to a canvas is access to its workspace: when you open a canvas, BuilderStudio resolves your role on the canvas's workspace and grants or denies the action from there.

What a workspace owns

• Canvases. Every canvas belongs to exactly one workspace and is listed under it. See Canvas overview for what lives on a canvas.
• Members. The owner plus any collaborators who have been invited and have accepted. Each member has one effective role in the workspace.
• Credentials.Integration connections (OAuth and service/bring-your-own-key) and API keys are stored against the workspace, so a node's run uses the workspace's connected accounts rather than any one member's personal credentials. See Integrations.
• Billing. The subscription plan, plan status, and billing customer live on the workspace, so usage and entitlements are shared by the team that shares the workspace.

Ownership and roles

Every workspace has exactly one owner, recorded as ownerId on the workspace itself rather than as a member row. The owner is immutable — ownership cannot be reassigned or downgraded through the membership tools, and the owner cannot be removed from their own workspace. Everyone else is a member with one of three roles: admin, editor, or viewer. The Roles & Permissions page documents exactly what each role can do.

Create a workspace

1. 1

   Name the workspace

   Pick a name that is unique among the workspaces you own — duplicate names (case-insensitive) for the same owner are rejected. A description is optional.

2. 2

   You become the owner

   The creator is set as the workspace owner automatically. There is no separate "add owner" step, and you do not appear as a member row — owner access is derived from the workspace record.

3. 3

   Add canvases and collaborators

   Create canvases inside the workspace, then invite members by email so they can join with a role you choose.

How access is resolved

On every read or write, BuilderStudio resolves your effective role for the target workspace: owner if you created it, otherwise the role from your membership. If you have no relationship to the workspace at all, the request is rejected before it touches any canvas or credential. Because the same membership grants access to every canvas in the workspace, you scope a person to a body of work by choosing which workspace they belong to, not by sharing individual canvases.

1open a canvas2  -> look up the canvas's workspaceId3  -> resolve your role on that workspace4       owner   (workspace.ownerId === you)5       admin / editor / viewer  (your membership row)6       none    -> request denied7  -> allow or deny the action based on the role

Related

• Roles & Permissions — what each role can and cannot do.
• Inviting Members — the email-based invite and accept flow.
• Multiplayer — editing the same canvas live with other members.