The Whiteboard comes in two flavours:
Standalone whiteboards: opened from the sidebar, not tied to any one game.
Per-game whiteboards: opened from a game's page, tied to that game.
Both use the same canvas and tools. The difference is where the board lives and who can see it. This page helps you pick.
What this page helps you do
Decide whether your next whiteboard should be standalone or per-game.
Understand the access implications of each choice.
Move content between the two if you change your mind.
Standalone whiteboards
Open from the sidebar's Whiteboard section.
Lives at: the team workspace level.
Who sees it: everyone in the team workspace with general access (not per-game restricted).
Best for: - Cross-game ideation: exploring a mechanic that might fit several games. - Studio operations: non-game work like roadmap planning, hiring notes, convention prep. - Visual brainstorms that don't yet have a home in a specific game. - Workshops or working sessions with multiple participants.
Standalone boards are also where you'd start things that might graduate to a game later. If a brainstorm yields a real game idea, you can create the game and continue working on a per-game whiteboard.
Per-game whiteboards
Open from the Whiteboard tab on a specific game's page.
Lives at: the game level (inside the game's record).
Who sees it: people with access to that specific game, including Collaborators with per-game grants.
Best for: - Game-specific ideation: sketching this game's economy, this game's card layouts. - Playtest debriefs: capturing what changed in this game's design. - Production planning for one game. - Sharing visual context with a freelancer who's only granted access to one game.
Per-game whiteboards travel with the game, if you transfer the game's data or hand it off internally, the whiteboard goes too.
The access difference matters
The most common reason to pick per-game is access scoping.
If you've granted a freelancer Collaborator access to one game, they can see that game's per-game whiteboard but not your standalone team whiteboards. You can sketch with them on this game's canvas without them seeing what's brewing on other games.
The reverse is also true, a Member or Admin sees everything anyway, so the access difference doesn't matter for them.
For more on access, see Sharing access on a game and Set yourself up for success: collaborator permissions.
Moving content between them
If you started something on a standalone board that turned out to be about one specific game, you can move it:
Open the standalone whiteboard.
Select the relevant items (or a frame containing them).
Cut (
Cmd/Ctrl + X).Open the per-game whiteboard for that game.
Paste (
Cmd/Ctrl + V).
The content lands on the per-game canvas; the standalone board no longer holds it.
You can move the other direction the same way.
Patterns that work
A few real-world setups:
Studio scratch board (standalone), running list of ideas across the studio. Items graduate to per-game whiteboards when they become real projects.
One per-game whiteboard per active game: design notes, mockups, playtest debriefs all live on the same canvas for that game.
Convention prep (standalone), booth layout, schedule, demo assignments, the works.
Multi-game licensing pitch (standalone), when you're pitching a bundle, the standalone board holds the meta-narrative; per-game boards hold the per-title detail.
You don't have to pick one model. Most studios use both kinds based on what each piece of work needs.
Tips & common questions
Can I link from a standalone whiteboard to a game? Add a text label with the game name and a link to the game page. There's no automatic association, that's what per-game whiteboards are for.
A per-game whiteboard's content is too sensitive, can I make it private to me? Per-game whiteboards inherit the game's access list. If you want a board nobody else on the team can see, use a standalone whiteboard with locked- down access, though even there, every team member sees it. For truly private notes, use the game's Notes section instead.
Why doesn't a freelancer Collaborator see my standalone whiteboards? By design, Collaborators are scoped to specific games. Standalone whiteboards aren't on any game, so Collaborators don't see them. To share one specifically, use a read-only link (see Sharing and exporting).
Can a per-game whiteboard be shared publicly via a read-only link? Yes, read-only links work the same way regardless of which kind of whiteboard the board is. See Sharing and exporting.