Whiteboards

Some work cannot start as a list. Architecture, a user flow, a messy planning session where three people are pointing at the same box — that is a canvas problem, not a tracker problem.

A whiteboard is that canvas, living in the same workspace as everything else.

What you get

An infinite surface with the usual vocabulary: shapes, arrows, sticky notes, freehand drawing, text, and images you can paste straight in.

Nothing here is trying to be clever. It is a whiteboard, and the value is that it is here — same workspace, same permissions, same search — instead of in a sixth tab that nobody has access to.

Two places to make one

Where	How
On its own	The Whiteboards section in the sidebar. Press N to make one.
Inside a page	Type / in any page and pick Whiteboard.

The second one is the underrated option. A diagram in the middle of a spec gets looked at. A diagram linked from a spec does not.

Permissions follow the page

A whiteboard that lives inside a page inherits that page’s access. If a guest can read the page, they can see the board on it — and if they cannot reach the page, the board is invisible to them too.

A standalone whiteboard follows the normal workspace rules. See Roles and permissions.

From canvas to tasks

A whiteboard is where the plan gets found. Once it exists, move it into the tracker — the boxes on the board usually map to tasks one for one.

The fastest route: write the outcomes as a list in the page around the board, select each line, and create a task from it. See Write anything.

Deleting and restoring

Whiteboards archive rather than vanish. A board removed from a page is filed away and swept later, so an accidental delete during a messy session is recoverable rather than final.

Limits

Plan	Whiteboards
Free	1
Pro	Unlimited

Whiteboards are a workspace module. If your admin has it switched off, the section is hidden for everyone — see Workspace settings.

Next

• Pages and wiki — where an embedded board lives.
• Schema designer — the same idea for database diagrams.