Boards

Configurable shared boards — systems of record for your team's work, with custom columns, grouping, totals, and per-team access.

A board is a shared system of record: a named set of rows with its own column layout and its own access rules. Use one anywhere your team tracks work in a repeating shape — a launch checklist, a hiring pipeline, a support queue, a sales pipeline, an invoice tracker.

Two ideas make boards different from a plain task list:

A board owns its columns. The columns are the board's own layout over properties, so one team's "Stage" can be another board's "Status" without either renaming the other.
A board owns its access. Sharing is per team or per person, and each grant decides which rows a subject can see and what they may delete.

Every board has exactly one owner — you personally, or one of your teams. Boards live directly under Tasks in the sidebar.

The boards list

The boards list groups every board you can reach by owner: your personal boards first, then one band per team, each labeled with the team's name. From there you can:

Search across board names, descriptions, row labels, and scope.
Filter by scope — everything, personal only, or team only.
Filter by description — boards with or without one.
Sort by recently updated, recently created, name A–Z, or name Z–A.

Your scope, description filter, and sort choices are remembered between visits.

Creating a board

Open the create dialog with the + button next to Boards in the sidebar. You give the board:

A name and an optional description.
A row label — what this board calls its rows (see below).
An owner: you personally, or one of your teams.
Its starting columns, picked as chips in the dialog.
Its sharing grants, configured before anything is created.

Columns and access rules are committed in the same transaction as the board, so a board never exists in a half-configured state.

Row labels

A board doesn't have to call its rows "tasks". The row label renames what a row is on this board — "Invoice" on a billing board, "Client" on an agency board, "Candidate" in hiring. The label is used wherever the board refers to its rows.

Columns

Every new board starts with the three columns a task already carries, so a board is usable the moment it exists:

Status — Not Started, In Progress, In Review, Completed, Canceled
Priority — Low, Medium, High, Urgent
Assignees — the people on a row

A column is a view of a property, not a new kind of field: it reads and writes the property it points at. That has two consequences worth knowing:

The default columns reuse the same shared Status and Priority every task in your workspace uses. Fill in a board cell and the task's own chips update everywhere — in channels, docs, and agent chats.
Renaming a column is board-local. Calling a column "Stage" on one board changes nothing on another board or on any task. Clearing the name restores the property's own.

If you customise a default column — renaming it or editing its options — the board is offered its own copy of the property, so the workspace-wide Status stays untouched for everyone else. Rows keep their old values; because those point at the old property's options, you're warned before the switch.

Every column can be renamed, resized, pinned, hidden, shown, and reordered (drag the header, or use the header menu or the Columns popover). Hidden columns keep their data; they're just out of view and out of the new-item composer.

Column types

The + chip adds another column. Types are named for what they are to a person, not how they're stored:

Text — free-form text

Number — plain numbers, with sum-style totals

Currency — money amounts with a currency and money totals

Date — a date, with earliest/latest totals

Checkbox — a tick, with a checked-of-total count

Select — one value from a list you define

Number select — a select whose values are numbers (t-shirt sizes, effort bands)

Multi-select — several values at once from a list you define

Status — a select tuned for stages: Not Started, In Progress, Done

Board link — a reference to another board, resolved to its name

People live in Assignees — there's no separate person column, because a second one would only split where a row's people are recorded. Tags are their own system rather than a column type.

You can also mint a brand-new property from the board itself — name it, pick its type, and define its option values without leaving the dialog or the column editor.

The Team column

The moment a board is shared with more than one team, a Team column appears. Its options are exactly the teams on the board, and every row says which team it belongs to — that's what lets each team see only its own rows. The Team column is managed: it can't be removed while the board spans teams, because rows would stop being attributable.

Rows

Rows on a board are real tasks. Editing a card updates the task everywhere it lives — its @mentions in channels, docs, and email stay live, and agents see the same values.

Add an existing task to a board, or press New Item to compose one directly on the board — the composer offers the board's visible columns as fields, so a row arrives filled in rather than empty.
Rows keep a board order. New rows can be inserted between others, and the order is the board's own — independent of how the underlying list sorts tasks.
A row belongs to one board at a time. Adding a row that already sits on another board relocates it, and that move is always explicit — never a silent duplicate.

Grouping and summaries

Group the board by any property with options — Status, Priority, or one of your own — and the board shows one band per value, including empty ones. A board grouped by Status shows every stage as a column header even before any row reaches it: the bands are the pipeline, not just what's currently populated.

Across the bottom, a totals row summarises each numeric column, and each group header shows its own subtotal. What a column summarises depends on its type:

Sum — the total of a number column, and the count of rows

Money — a currency total with its currency

Checkbox — how many rows are ticked, of how many

Distribution — how rows spread across a select's options

People — how many distinct people are assigned

Dates — the earliest and latest date in the column

Tick a checkbox or edit a number and the total moves immediately — the arithmetic is applied optimistically and reconciled against the server's authoritative aggregate behind it. Summaries that can't be safely guessed from one edit (date ranges, distinct people) simply wait for the server rather than risk showing a confidently wrong number.

Board links

The Board link column type points one board at another — an invoices board linked from a clients board, for example. The link is stored as a reference, not a copy: it survives renames, and its cell resolves to the linked board's name. The link picker offers the other boards you can reach, straight from your personal and current team's boards.

Access is granted per subject — a team or an individual — and each grant controls three independent things:

Access level — view or edit. Viewers can read the board; editors can move and update rows.

Row scope — which rows a subject can see: all rows, rows belonging to their team, or rows assigned to their team.

Delete scope — what a subject may delete: any row, only rows they created, or nothing.

A team you share with gets a sensible default: edit access, their team's rows, and the right to delete only what they created. Narrow or widen any part of it per subject. If a row is invisible to someone, the board doesn't leak that it exists — the server simply doesn't confirm boards a caller can't reach.