Feedback boards and voting
Public boards that collect typed requests, let customers vote and comment, and give you moderation, request types, and merge tools.
A feedback board is a public place for customers to tell you what to build, report what is broken, and vote on what matters most. Boards are where the customer-voice loop starts.
Boards and visibility
A board collects requests from customers and guests. Each board has a visibility:
- Public: anyone can view and submit.
- Private: only authenticated customers.
- Internal: staff only.
Per board you also control whether guests can post without an account, whether posts route through moderation before appearing, and whether voting and comments are on. A default sort (newest, top by votes, or trending) sets how the board opens.
A board's visibility only decides who can see it once your workspace's public site is live. The public site (boards, roadmap, changelog, and help center together) stays dark until an owner explicitly publishes it from Boards, and can be taken down again the same way.
Request types
Posts are categorized by request type (for example, Feature, Bug, Inquiry). Request types are data you configure, not a fixed list, and each board declares which types it accepts and in what order. This keeps a bug report and a feature idea clearly distinct.
Voting
Voting is how priority emerges from your customers rather than from a guess. Each person gets one vote per post: signed-in customers are deduplicated by their account, and anonymous voters by a privacy-preserving fingerprint (never a raw IP). Vote counts are kept on the post for fast sorting.
Comments and moderation
Customers can discuss a post in comments. Posts carry a moderation status (pending, approved, rejected, or spam) so a board that requires approval holds new submissions until a moderator reviews them. Staff with the right permission moderate and triage; configuring the board itself stays Admin and Owner.
Merging duplicates
When two posts are the same request, merge one into the other. Votes roll up to the canonical post, so the true level of demand is not split across duplicates. Posts can also be pinned to keep an important one at the top.
Status pipeline
Each board runs its posts through a status pipeline (the same workflow engine the rest of Hark uses). Moving a post through statuses is what drives the roadmap and, eventually, the changelog.