Boards

A board is the named, ownable thing you and your team collaborate on. Every board lives in a workspace, has a name, has collaborators (managers, editors, viewers), and contains one map — the canvas where the work happens.

Boards are the unit of ownership and access. “I created a board for our Q3 planning”; “share the roadmap board with the design team”; “archive the old discovery board.” Sharing, renaming, duplicating, archiving, and exporting all happen at the board level. Permissions and notifications attach here.

Inside the board, the map is the canvas. The map has a type — story map, sitemap, kanban, persona, and others — and the type determines the canvas grammar (how cards can be arranged, what’s structural and what’s decorative). The board is the container; the map is what you draw on; the map type is what kind of drawing it is.

A board belongs to exactly one workspace. The workspace decides who can be a member, who’s a guest, what features the board has access to, and who pays the bill. Within the board, collaborators have a role that decides what they can do.

Boards can connect to one external tracker (ADO or Jira). When connected, cards on the board can mirror tracker items, and edits flow both directions. The connection is at the board level — a board has at most one tracker, and a tracker connection can’t span boards.

Caution

Don’t change the map type after a board has been worked on — pick the right type at creation. The map type is immutable once cards exist, because switching would change the grammar of where everything sits.