Hide Member Identities
Keep internal context private on public-facing workflows and understand the current limits of identity hiding in Boarbs.
Boarbs does not currently provide a workspace-wide toggle that anonymizes team identities across the public portal.
If your goal is to keep internal identities less visible, the practical answer today is to choose the right surface for the conversation.
What Is Public vs Private
In a typical Boarbs setup:
- public boards are visible on the public portal
- public comments on public posts are visible to visitors
- team notes stay internal
- private boards stay internal
- roadmaps can be public or team-only
So the way to protect identities is mostly about keeping the right discussion on the right surface.
Best Options Today
If you want less public attribution for your team:
- keep internal planning on private boards
- use Team Notes for internal reasoning and coordination
- keep public comments short and customer-facing
- publish the final outcome instead of the internal debate
This preserves transparency for users without exposing every internal conversation.
When This Matters Most
This is especially important for:
- agencies or consultants representing clients
- teams that want one product voice instead of many individual voices
- enterprise workflows with sensitive internal context
- small teams that do not want engineers replying publicly from day one
Public Visibility Without Public Team Discussion
A strong pattern is:
- keep the board public
- allow users to submit and vote
- triage internally
- share status changes and concise public comments only when needed
That gives users visibility while keeping internal coordination private.
What Boarbs Does Not Do Yet
Today, there is no simple switch to replace staff names with a generic label everywhere on the public portal.
If that exact behavior matters, avoid public team-by-team discussion and keep detailed context on internal surfaces.
A Better Question to Ask
Instead of “How do I hide every identity?” ask:
- should this board be public or private
- should this note be public or internal
- does this request need a customer-facing update or just internal discussion
Those choices have more impact than a cosmetic anonymity setting would.
Next Steps
- Use Private Feedback Boards — Keep internal workflows completely off the public portal
- Collect Guest Feedback — Decide how open the public interaction model should be
- Publish an Update — Share customer-facing progress without exposing internal debate