When private beats public
Enterprise accounts often cannot post publicly, and beta programmes under NDA must not leak. A private board keeps the same voting, statuses and comments while restricting who can see it to a list you control.
Who can see a private board
A board's visibility is either Public, where anyone with the link can view, or Private, where only your workspace members and the people on the board's allowlist can. The allowlist takes single email addresses, such as person@example.com, or whole domains, such as @acme.com, so everyone at one customer gets in without being added one by one.
People you add by email receive an email telling them they have access. Anyone else who opens the link sees nothing of the board's content.
- 1Open Admin, then Boards.
- 2Create a board with Visibility set to Private, or edit an existing one.
- 3Choose Access on the board.
- 4Enter an email address or an @domain and choose Add.
Internal notes
Your team can leave internal notes on any post, alongside the public comments. Customers never see them; the restriction is enforced in the database, not just hidden in the page. Use them for account context and the reason behind a decision, so the public reply can stay short and the reasoning is still recorded.
Moving a post to another board
Someone on your team with the Triage feedback permission can move a post to a different board from the post's menu with Move to board…. Its votes, comments and followers go with it, and internal notes stay visible to staff only. Moving a post from a private board to a public one is how you share a request once an embargo lifts; check the comments first, because everything public on the post becomes visible to anyone with the link.
Who can post, vote and comment
Visibility decides who can see a private board. Three further settings decide what viewers can do: Who can post, Who can vote and Who can comment, each set to anyone who can view the board, workspace members only, or admins only. A private beta board might let everyone on the allowlist vote and comment, while a board for one enterprise account might keep posting to your team, who log requests from calls.
Plans and access
The Free plan includes 1 public board and no private ones. Starter includes 3 public boards and 1 private board, so a public feature board and a private enterprise board can run side by side; Growth raises that to 10 public and 5 private, and Business has no limit.
Access to a private board is a list you control: workspace members always see it, and you can add single email addresses for a contractor or design partner, or a whole @domain.com for every person at one customer. Remove an entry from the same Access list when the engagement ends.
What to keep private, and what to show
Keep a board private when the people on it cannot or should not see each other's requests: a single enterprise account, a beta under NDA, or internal requests from employees. Keep it public when seeing other customers' requests helps, which is most feature boards: people vote instead of posting duplicates, and prospects see that the product is moving.
If you are unsure, start public with a clear posting policy and move sensitive requests to a private board as they come up. Moving a post to a public board later takes one action; walking back something already published is not as easy.