How a vote works
Each person has one vote per post, and clicking the vote button again takes it back. Voting needs an account: someone who is signed out and clicks vote is asked to sign in, and the vote is cast when they return, so nobody loses the click.
Voting also follows the post for that person, so they hear when its status changes or when it ships without having to subscribe separately. Because every vote belongs to a signed-in account, one person cannot vote twice on the same request.
Who can vote on each board
Every board has a Who can vote setting with three choices: anyone who can view the board, workspace members only, or admins only. Who can post and Who can comment work the same way, so you can, for example, let customers vote and comment but keep new posts to your team.
On a public board, anyone with the link can view, so anyone who signs in can vote. On a private board, viewers are your workspace members plus the emails and domains on the board's allowlist.
Votes your team logs
From a post's menu, Vote on behalf of… adds a vote for a workspace member by their email address, which is useful when a colleague asks for something in a meeting rather than on the board.
For customers, the Chrome extension lets an admin file a request under the customer's name, adding them by email if they are new, so the request is counted against the person who actually asked.
Sorting requests
On the public board, visitors can sort by Trending (the default), Top voted, Newest, Oldest and Recently updated, and filter by status, by tag and by their own activity: posts they voted on, posts they wrote and posts they follow. New posts, votes and comments appear without a page refresh.
In the admin Posts inbox, your team sees every board in one list, with the same sorts plus filters for board, status, tag and Assigned to me. Saved views keep the combinations you use often.
Vote milestones
When a post reaches 10, 25, 50, 100, 250, 500 or 1,000 votes, its author and followers are notified. A milestone is a natural moment to review a request: it tells you demand has grown since anyone last looked at it.
Exporting the list
The admin Posts inbox exports the current view to CSV, with each post's id, title, status, vote count, comment count and creation date. Filter to a board or a status first, then export, to get the list you want to discuss in a planning meeting.
From ranked list to roadmap
Once you decide what to build, move those posts to Planned. The public roadmap shows Planned, In progress and Complete as columns, so the post appears there straight away and its followers are told about the status change.
When the work ships, publish a changelog entry and link the posts it resolves. Everyone who asked is told that something they asked for has shipped.
Customer context on votes
On Growth and Business, the Segment integration can send each person's company, plan and MRR to Looph. Once that data arrives, the admin Posts inbox adds Most MRR and Most customers sorts and a Voted by filter for plan, company and minimum MRR. Teammates need the People permission to see it.
Customer data changes how you sort and filter, not how votes count: every vote still counts once, and weighting votes by revenue is not available.
A prioritisation rule you can explain
Votes are one input, not the decision. Read the comments on the top requests: they tell you why people want something, which is often a cheaper problem to solve than the feature they named. Write down what else matters to the decision, such as strategy, cost and which customers are asking, so the team can see why a post with fewer votes was planned first.
Keep the vote count visible and revisit the top of the list every few weeks. If the most-voted requests keep surprising the people who talk to customers, ask whether the board is reaching the customers who matter most to you.