Control who can vote on ideas to ensure you're addressing the most important pain points from your actual users. This helps maintain data quality and prevents spam voting.
Note
If you have set up and your customers are logged into your app, they won't need to reidentify themselves.
Best practices
For public-facing Ideas boards: Consider requiring email addresses to reduce spam and anonymous voting.
For internal teams: Optional email collection may be sufficient.
For product feedback: Requiring an email address helps you follow up with users for clarification.
Access Beamer Feedback settings
Select Settings > Beamer Feedback from the sidebar.
Scroll to the Order and Visibility section.
Request an email or name to submit an idea or comment
Set up whether you collect a name when a user submits an Idea.
Request an email address when a user suggests an idea
Optional: Allows users to submit the idea and, optionally, enter their email address.
Email Required: Only submits the idea if they enter their email address.
Don’t request email: They will not be prompted to enter an email address.
Request a name when a user suggests an idea
Optional: Allows users to submit the idea and, optionally, enter their name.
Email Required: Only submit the idea if they enter their name.
Don’t request name: They will not be prompted to enter a name.
Request email when users send a comment
Optional: Allows users to submit comments and, optionally, enter their email addresses.
Email Required: Only submit the comment if they enter their email address.
Don’t request an email: They will not be prompted to enter an email address.
Notifications display name
Select First name, First and last name, or Custom name. If Custom name is selected, enter a custom name in the space provided.
Note
If the Public Roadmap is visible to everyone, including prospects, we recommend collecting email addresses so you can keep them updated on Ideas that they’ve voted on or requested.
How voting works
Each user gets one vote per idea.
A user can add or remove their own vote. Clicking the vote control again removes it.
One user cannot remove or change another user's vote.
There is no downvote. The only vote is an upvote, so there is no way for a customer to register that they dislike an idea.
Votes are counted per user, not per company. If several people from the same organisation vote on an idea, each vote counts.
A second user cannot find where to vote
If you have submitted an idea and then signed in as a different user to test voting, and the vote control is not there, the usual cause is the audience setting rather than the idea.
Check who is allowed to vote. Go to Settings > Feature Requests. If voting is set to Identified users, only users Beamer has identified can vote. Setting it to All users removes that requirement.
If you are keeping Identified users, make sure the user is actually identified. The user_id and email address have to reach Beamer through beamer_config. Your technical team can confirm this.
Open the widget before the standalone page. Going to the standalone Feature Request page directly can mean Beamer never receives the user's details for that session. Open the widget on your site first, then open the standalone view from it. The Vote option appears once the user is identified.
What people see on an idea
Names on comments. End users can see the first and last name of anyone who comments on an idea. They do not see email addresses. There is no setting to hide a commenter's name.
Hiding a specific comment. As an admin you can hide an individual comment. Open the idea in the editor and hide the comment there.
The date next to the flag icon. That is the ETA set on the idea, which you set in the idea editor. It is not labelled by default, so customers often do not know what the date means. You can add a label with custom CSS under Settings > Appearance, for example:
.roadmapItemETA::before {
content: "ETA";
font-size: 12px;
font-weight: 600;
color: #666;
margin-right: 6px;
vertical-align: middle;
}