Reference
Understand how access, visibility, subscriptions, notifications, and workspace settings behave once your Boarbs portal is live.
After setup, the next questions are usually operational:
- who can see this board
- why can this user interact here but not there
- which changes send emails
- which setting actually controls this behavior
This section answers those questions directly.
What This Section Covers
| Guide | What it helps with |
|---|---|
| Permissions and Visibility | Public vs private boards, guest interactions, roadmap visibility, tags, internal comments, and embed access |
| How Notifications Work | Subscriptions, email triggers, and why some changes stay silent |
| Settings Reference | What each workspace settings area actually controls |
| Troubleshooting | Common launch and day-to-day problems |
Best Reading Order
If your team is still getting used to Boarbs, read these in order:
- permissions and visibility
- settings reference
- notifications
- troubleshooting
That sequence removes most of the ambiguity around public vs internal workflows.
What This Section Does Not Try to Do
This section does not repeat the first-run setup flow.
If you still need to create boards, invite teammates, or choose your rollout path, go back to Get started first.
Recommended Use
Keep this section open when you are:
- making something public for the first time
- deciding whether to use a public board or a private board
- explaining portal behavior to support or product teammates
- debugging why someone did not receive an update
Next Steps
- Get started — Build the initial structure first
- Branding — Shape the public portal experience
- Collect — See the hosted experience from the user side
MCP
Connect Cursor, Claude, Claude Code, ChatGPT, or another MCP client to Boarbs through the official hosted Model Context Protocol server.
Permissions and Visibility
Understand how identity, board visibility, roadmap visibility, guest interactions, internal comments, tag visibility, and embed access work in Boarbs.
