Workspaces and boards

The containment model#

workspace
  ├── board
  │     ├── status column
  │     └── ticket
  ├── wiki
  │     └── page
  └── labels

A workspace is the tenant. Nothing is shared between workspaces: not a board, not a ticket, not a person's role, not a label.

A board belongs to exactly one workspace and holds its own status columns and tickets. A ticket belongs to exactly one board. Labels are the exception to per-board ownership: defined once for the workspace, applied to any ticket on any board in it.

Board access sits alongside workspace roles#

Every person holds exactly one workspace role: owner, admin, member, or viewer. A second, separate list decides where they may work: which boards they can see.

• Owners and admins reach every board in the workspace.
• Members and viewers reach only the boards they have been given. A board they have not been given answers "Board not found." rather than "forbidden" — they are not told it exists.

See Roles and permissions.

Creating a board grants access only to its creator#

Members can create boards, and when they do, they are the only non-admin who can see the new board. The fix is for an owner or admin to tick the board on a colleague's row in User access.

What a wiki belongs to#

The wiki belongs to the workspace, not to a board. Anyone with an active membership can read every wiki page in it, including a member who has been given a single board. See Wiki pages.

What a board is made of#

Beyond its columns and tickets, a board carries a name and position, per-person card display preferences, and sprint settings if it has been turned into a sprint series — see Sprints.

Removing a board archives it: nothing is destroyed, and it can be restored from Trash → Archived boards. See Boards.

Billing state applies to the whole workspace#

Because billing belongs to the workspace, its state applies to every board and the wiki at once. An unpaid invoice makes a workspace read-only; nothing is ever deleted by a billing state.