Organize feedback with boards

Create boards, set who can view, vote, comment, and post on each one, add per-board moderation rules, and import or export a board's posts.

JM
James Morton
Written By James MortonLast updated 1 day ago

Boards keep different kinds of feedback apart, so feature requests don't get buried under bug reports and users know where to post. This article covers creating boards, controlling who can do what on each board, per-board moderation, and importing or exporting a board's posts.

Why use multiple boards?

Without boards, everything piles up in one place. Your team spends time sorting through noise, and users don't know where to post.

Common setups:

  • Feature Requests + Bug Reports: simple and effective
  • Feature Requests + Bug Reports + Integrations: when you get a lot of integration requests
  • Mobile + Web + API: separate by platform

Tip: Start with 2-3 boards. You can always add more later, and too many boards confuse users about where to post.

Create a board

  1. Go to Settings > Feedback & Roadmaps > Boards.
  2. Click New board.
  3. Enter a Board name (for example, "Feature Requests") and an optional Description.
  4. Under Access, pick a starting preset:

    • Everyone: anyone can view; sign-in is required to vote, comment, and submit.
    • Team only: workspace members only; the board is hidden from the portal.
  5. Optionally check Customize access after create to open the new board's Access tab straight away.
  6. Click Create board.

The URL slug is generated from the board name. For example, "Feature Requests" becomes /b/feature-requests.

Note: Segments and per-action access are set after creation, on the board's Access tab. The create dialog only offers the two presets.

Board settings

Click a board in Settings > Feedback & Roadmaps > Boards to open its settings. Each board has four tabs: General, Access, Moderation, and Data. Changes on every tab save automatically.

General tab

Edit the board's Name and Description. They save when you leave the field or press Enter.

At the bottom, Delete this board removes the board.

Warning: Deleting a board permanently deletes the board and everything on it: its posts, votes, and comments. This cannot be undone.

Access tab

The Access tab is a permissions matrix that decides who can do what on this board. Board access changes are enforced on the server and recorded in the audit log.

The rows are four actions:

  • View: see posts and discussion
  • Vote: upvote posts to signal interest
  • Comment: reply on existing posts
  • Submit posts: create new feedback

The columns are four tiers, from most open to most restrictive:

  • Everyone: public, no sign-in needed
  • Signed-in users: anyone signed in to your portal
  • Specific segments: members of the segments you pick
  • Team only: workspace members

Each action has its own tier, so access can be asymmetric. For example, a board can let Everyone view while only Signed-in users vote, comment, and submit.

Presets

  • Everyone: View is Everyone; Vote, Comment, and Submit posts are Signed-in users.
  • Team only: all four actions are Team only, and the board is hidden from the portal.

Clicking a preset resets every action to it. Changing any cell switches the board to Custom.

Note: Vote, Comment, and Submit posts can never be more open than View. Raising View's tier bumps the other actions up to match. Cells that would break this rule are locked, and the tooltip names the minimum tier you can pick.

Choose segments per action

When you set an action to Specific segments, click the cell to pick one or more segments. Each action keeps its own list. If an action is set to segments but none are chosen, the cell shows a "Pick segments" warning and the change isn't saved until you choose at least one.

Tip: Use dynamic segments so membership stays accurate automatically: beta testers, enterprise accounts, or a single email domain.

The workspace anonymous switch

Allow anonymous interaction (Settings > Access & Security > Portal access) is a ceiling for every board. When it's off, the Everyone tier is disabled for Vote, Comment, and Submit posts on all boards, and the Access tab shows a banner saying so. View is never affected.

Team members and admins always have full access to every board. They bypass these rules.

Moderation tab

The Moderation tab sets approval rules for this board only, separate from access. There are three rules:

  • Require approval for anonymous posts
  • Require approval for signed-in posts
  • Require approval for new comments

Each rule can be Inherit, On, or Off. Inherit uses the workspace default and shows the resolved value, for example "Inherit (On)". On always holds matching submissions for review. Off always publishes them.

Held items go to the moderation queue. Team members' own posts and comments always publish immediately. See Moderation for the full model.

Data tab

  • Import posts takes you to Settings > Imports & exports, where CSV imports run.
  • Export posts downloads this board's posts as a CSV file.

See Import and export data for the file format.

Keep feedback internal or targeted

Set each action's tier to fit the use case:

Use case

How to set it

Internal team feedback

All four actions Team only (the Team only preset).

Beta program

View: Specific segments (your beta testers); Vote, Comment, Submit posts: Signed-in users or the same segment.

Enterprise-only roadmap

View: Specific segments (an enterprise segment); Submit posts: Team only; Vote and Comment: Specific segments.

Hidden from search engines but open to signed-in users

View: Signed-in users; set the other actions as you like.

Moving from another tool?

Export your data as CSV, fit it to the Quackback template, and import it in Settings > Imports & exports. See Migrate from another tool.

Tip: Import into a test board first to check everything looks right, then delete it and import into the real board.

Was this helpful?

Your feedback shapes what we write next.