Settings Reference
See what each Boarbs workspace settings area controls, what changes are public-facing, and where the current product still has gaps.
This page covers workspace settings, not personal account preferences.
If you are trying to understand what changes the public portal, what affects internal team workflow, or where a control actually lives, start here.
Workspace Settings at a Glance
| Area | What it controls | Important notes |
|---|---|---|
| Settings → General | Organization logo, organization name, primary color, email theme, Remove Boarbs branding, guest interactions | This is the main public-behavior area for the workspace |
| Settings → Members | Invite members and review current workspace members | Best place to add product, support, and engineering teammates |
| Settings → Boards | Board name, description, icon, slug, visibility | PUBLIC vs PRIVATE is one of the most important public workflow decisions |
| Settings → Roadmaps | Roadmap name, description, icon, filters, ordering, columns, visibility | Roadmaps have their own visibility model separate from boards |
| Settings → Statuses | Status names, colors, categories, default status | New posts are assigned the default status automatically |
| Settings → Tags | Tag name, color, public/private visibility | Private tags are useful for internal segmentation |
| Settings → Integrations | Linear sync plus one Slack and one Discord notification channel | Organization admins manage the connections; see Linear Integration, Slack Integration, and Discord Integration |
| Settings → API | Organization API keys and API quickstart | Keys can be read-only or read-write; the plain key is only shown once |
| Settings → Users | Portal users who have signed in | This is about end-users on the portal, not your internal members |
| Settings → Billing | Active plan and plan changes | This matters for limits such as board count |
| Settings → Danger Zone | Delete the organization | This is destructive |
| Settings → Permissions | Placeholder page | It is currently not the main source of access control logic |
What Changes the Public Experience Immediately
These settings have the biggest visible impact on public users:
- board visibility
- roadmap visibility
- guest interactions
- organization name
- logo
- primary color
- board copy and roadmap copy
- public vs private tag choice
If something “feels wrong” on the portal, the issue is usually in one of those controls.
What Is Mostly Internal
These settings are mostly about internal workflow quality:
- default status
- internal comments
- internal notes
- assignee changes
- private tags
- team-only roadmaps
Those controls help your team stay organized without changing the public experience directly.
General Settings
Settings → General is the workspace-level control surface.
This is where you manage:
- organization logo
- organization name
- primary color
- email theme
- Remove Boarbs branding on outbound emails (Pro only; the footer stays on by default)
- whether guests can vote, comment, and subscribe without signing in
If you only review one settings page before launch, make it this one.
Board Settings
Settings → Boards is where structure becomes visible to users.
For each board, you can control:
- name
- description
- icon
- slug
- visibility
The most important decision here is still whether the board is PUBLIC or PRIVATE.
Roadmap Settings
Settings → Roadmaps controls how planning becomes visible.
For each roadmap, you can manage:
- name
- description
- icon
- visibility
- sort order
- base filters
- columns
- whether a column is shown publicly
This means a roadmap can be public and still selective.
Status and Tag Settings
Settings → Statuses defines your workflow language.
That includes:
- status names
- colors
- categories like
INBOX,PLANNED,IN_PROGRESS,COMPLETED, andCANCELED - which status is the default for new posts
Settings → Tags defines your labeling system.
That includes:
- name
- color
- whether the tag is public or private
API and Users
Settings → API is for machine access.
Use it when you need:
- organization API keys
- embed session creation
- backend integrations
- automation from scripts or CI
Settings → Integrations is where organization admins configure Linear sync and choose Slack and Discord channels for public post and comment notifications. Connected Slack channels can also create a draft with /boarbs or the Create Boarbs post shortcut, then Approve or Reject it in Slack. See Linear Integration, Slack Integration, and Discord Integration for the complete workflows.
Settings → Users is for portal end-users who have signed in.
That is different from Settings → Members, which is your internal team list.
Gaps to Be Aware Of
Some topics sound like they should live in settings, but do not currently exist as a simple workspace toggle:
- fixed portal language for the whole organization
- custom footer links editor
- self-serve CSV importer
- custom domain setup in the current settings UI
Those workflows can still be planned, but they are not a single settings page today.
Outside Workspace Settings
A few relevant controls live elsewhere:
- personal language preference is account-level, not organization-level
- embed identity is supplied by your backend when you create the session
- public portal URLs depend on your workspace slug
Recommended Settings Review Order
If you are preparing to launch or clean up an existing workspace, review settings in this order:
- General
- Members
- Boards
- Statuses
- Tags
- Roadmaps
- API
That order gets structure and public behavior right before automation.
Next Steps
- Permissions and Visibility — Understand how these settings combine into real access rules
- How Notifications Work — Understand which actions create customer-facing emails
- Branding — Go deeper on portal appearance and public rollout choices