Create Boards

Every new workspace starts with a public Main board. For many teams, that is enough to get started.

Create additional boards when you truly need a different feedback surface, audience, or visibility level.

When a New Board Makes Sense

Good reasons to create another board:

• you manage multiple products
• you want a separate internal-only board
• you need a dedicated board for beta customers or a specific audience
• different teams should collect feedback independently

Usually, a new board is not necessary when:

• you only want a few different categories
• you want to separate bugs from feature ideas
• you want to group requests by theme

In those cases, use statuses, tags, and filters before creating more boards.

How Boards Work in Boarbs

A board controls the public or private surface where posts live.

At the organization level, boards share:

• the same member list
• the same statuses
• the same tags
• the same roadmap settings area

That means you do not need to rebuild your whole workflow every time you add a board.

Create a New Board

1. Open Settings → Boards
2. Choose Create board
3. Add a board name
4. Optionally add a description and icon
5. Choose the visibility:
   • PUBLIC if the board should appear on your portal
   • PRIVATE if it should stay internal
6. Save the board

Public vs Private Boards

If you are unsure, start with a public board only when customers actually need to see it.

How Visibility Changes Access

Board visibility is not only about appearance. It also affects who can submit into the board.

• public boards can be used for external feedback collection
• private boards stay inside the workspace
• guests cannot submit into a private board
• authenticated users who are not members of your workspace cannot submit into a private board

Use a private board when the work itself is internal.

Use a public board with tighter interaction rules when the content should stay visible, but participation should be narrower.

Suggested Starting Structures

One-board setup

Best when:

• you have one product
• you are just launching feedback collection
• you want the simplest possible setup

Recommended structure:

• keep Main
• use tags for themes
• use the default statuses

Two-board setup

Best when:

• you need one public board and one internal board
• you want to separate customer requests from internal product ideas

Recommended structure:

• Main as the public board
• one private internal board for team-only ideas

This is the most common “clean external + practical internal” setup.

Multi-product setup

Best when:

• each product has a distinct audience
• roadmap and feedback should stay clearly separated

Recommended structure:

• one board per product
• shared organization statuses and tags where possible

Recommended Practices

• start with as few boards as possible
• prefer tags and filters before splitting into many boards
• make a board public only when it is ready for customers
• revisit board structure after a few weeks of real usage
• avoid creating a separate board for every request type or tag
• use private boards for internal workflows, not as a substitute for customer sign-in rules

Next Steps

• Use Private Feedback Boards — See when a private board is the right tool
• Invite Members — Bring teammates into the workspace
• Tag New Submissions — Keep categories manageable without multiplying boards
• Triage Feedback — Organize incoming posts efficiently
• Portal — See how public boards appear on the hosted portal