A project in Boardssey is a board of tasks, usually for one game's development, sometimes for a non-game initiative like a Kickstarter or convention prep.
This page walks through creating a project from scratch.
What this page helps you do
Create a new project in your team workspace.
Decide whether to link it to a game.
Set up columns (statuses) that match how you work.
1. Open the Projects hub
In the sidebar, click Boards. Click New project in the top right.
2. Name and describe the project
Enter a clear project name. Examples: Castle Project, Development, Spring 2026 Kickstarter, Castle Project, Pitching.
The description is optional. Use it for the project's purpose, scope, or any context teammates need to know what this is for.
3. Link to a game (or leave standalone)
Pick whether this project is tied to a specific game:
Linked to a game: every task on this board belongs to that game. Choose this for development work on a specific design. The project shows up on the game's page too.
Standalone: for cross-game or non-game work. Examples: studio operations, marketing prep for a conference, multi-game licensing research.
You can change this later, turn a standalone project into a linked one, or move it between games, from the project's settings.
4. Pick a starting layout
Boardssey gives you a few starting templates for the board's columns:
Default development: Backlog → In progress → In review → Done. The most common starting point.
Playtesting cycle: To test → Testing now → Reviewing → Iterating → Shipped. For projects where each task is a playtest round.
Pitching cycle: To pitch → Pitched → Awaiting reply → Won → Lost. Less common since pitches have their own dedicated tracker, but useful for high-volume outreach.
Blank: start with no columns and add your own.
You can rename, reorder, add, and remove columns later. Pick the closest fit and adjust as you learn what works.
5. Create
Click Create project. You land on the empty board.
From here:
Add your first task, see Tasks and subtasks.
Adjust columns or add new ones, see Adjust your project board.
Invite specific Collaborators if you want to scope this project to a few people, see Sharing access on a game (per-game permissions cover project access too when the project is linked).
Tips & common questions
Should I have one project per game or multiple per game? Most designers start with one. Split into multiple only when one board becomes too noisy, e.g. one for design work, one for production work, one for marketing.
Can I copy a project's structure to another project? Not directly today. Manually re-creating columns takes a minute and is flexible.
Can a project have its own visibility settings, separate from the game? Project visibility follows the linked game's permissions. If you scope a Collaborator to a game, they see the project too. Standalone projects are visible to everyone in the team.
I picked the wrong template, can I switch? You can rename and reorder columns freely. There's no template-switch button; just edit the columns directly.