Workspaces

A workspace is the team container. Every board belongs to exactly one workspace, and every workspace has members, a plan, and a bill.

Roles

Workspaces decide who’s on the team and what they can reach. There are three workspace roles (with an Owner tier above Admin for billing-sensitive actions):

• Admin — full control. Manages billing, settings, members, and SSO. Can act on any board in the workspace regardless of board-level permissions.
• Member — full participant. Can create boards, collaborate on shared boards, and use integrations.
• Guest — limited participant. Has access only to specific boards they’ve been invited to; doesn’t see the workspace’s other boards or members. Useful for clients, contractors, or stakeholders who shouldn’t see your full backlog.

The workspace is the billing and entitlements boundary. Plans, seat counts, feature gates (SSO, advanced integrations, MCP access), and audit logs are all workspace-level. Two workspaces are independent — different members, different billing, different boards.

Workspaces own tracker connections too. Once you connect ADO or Jira at the workspace, any board can opt in; credentials live in the workspace, so you don’t re-authenticate per board.

Why members and guests are different tiers

A workspace seat is one audit-attributable identity authorized to push writes to a tracker. Members can create boards and edit tracker-synced cards; guests can’t push tracker writes by design, which is exactly why guests don’t consume seats. It’s not a feature tier — it’s about who can propagate a change to your system of record. See Permissions.

Caution

• Don’t use workspace membership for board-level permissions. Workspace says “you’re on the team”; board collaboration says “you can edit this board.”
• Don’t put every contractor on as a Member for board access. Guests exist for this and protect the rest of the workspace from being visible.