Enable voting
Go to Settings → Page → Roadmap and turn on Milestone upvotes: “Allow users to upvote milestone items.”
Two related settings shape how it behaves:
- Milestone upvote count: “Let your visitors see how many upvotes milestones have.” Turn this off to keep votes private to your team while still collecting them.
- Anonymous milestone upvotes lets visitors vote without identifying themselves. Higher volume, lower signal quality.
Requiring identification gets you fewer votes but lets you follow up with the people who asked, and tells you whether a request came from one loud user or thirty quiet ones.
Read-only roadmaps
If you want to publish your plans without inviting input, leave upvotes off. The roadmap still displays; visitors just can’t vote.
Enable Milestone comments under Settings → Page → Roadmap to let visitors leave feedback on individual milestones. Comments are more work to manage than votes, but they’re where you learn why someone wants something, which is usually more useful than the count.
Turning votes into decisions
Vote counts are a prioritization input, not an answer. Weigh them against:
- Who’s voting. A feature with 12 votes from enterprise accounts may beat one with 200 votes from free users.
- What the votes are actually asking for. Several distinct requests often collapse into one underlying problem.
- What you can support over time, which is a bigger commitment than building it.
