Step 1
Vote or remove your vote
- Open a public idea or issue
- Find its vote rail
Open a public item in Roadmap and Ideas, then find the vote rail beside its description.
Our counts and requests are synthetic. this worked example does not cast a vote on the live community board.
Step 2
Read before expressing interest
- Check the type, status and description
- A vote is not a purchase or a release promise
Read the full description and development status before voting. A vote expresses interest in that particular item.
It does not purchase a feature, promise a release date, or automatically submit a new suggestion.
Step 3
Vote adds exactly one
- Use the original vote control
- Check Voted and the updated count
Use the vote control once. In this example the count increases from eighty-six to eighty-seven, and the rail says Voted.
The request sets your desired state to voted. It is not an instruction to add another vote every time the same request is replayed.
Step 4
Remove your vote when your choice changes
- Use the same control to remove your vote
- Check Vote and the restored count
Use the same control again to remove your vote. Our example returns to eighty-six and the label changes back to Vote.
Removing your vote does not delete the community item, another person's vote, or any saved expense.
Step 5
Pro does not add vote weight
- Treat Pro as cosmetic author metadata
- Paid and unpaid identities each add one
A Pro badge is cosmetic display metadata. Regular paid access does not give a vote extra weight.
Our paid-display example still adds exactly one. Neither Premium nor cloud AI permission is required to express interest in a public item.
Step 6
One per identity is not one per person
- Use the private installation feedback identity
- Do not assume reinstall preserves the old vote
The limit is one vote per feedback identity, not a verified one vote per person. Pennie uses a private random installation identity.
Main-app sign-in does not link these votes to your account. Reinstalling or clearing storage may lose access to that installation's activity.
Step 7
An unconfirmed response may already be saved
- Read the visible connection error
- Reload before voting again
If a response is lost, the service may already have saved the vote. The actual detail page disables another vote and asks you to reload.
Do not guess that the count stayed unchanged or keep pressing the vote control. First confirm the saved state.
Step 8
Reload learns the saved vote
- Choose Reload feedback and comments
- Check the current Voted state
Choose Reload feedback and comments when the service is reachable. Our lost-response example then displays Voted and eighty-seven.
Reloading reads the saved state without adding a second vote. Only then decide whether you want to remove it.
Step 9
Only eligible public items are votable
- Respect moderation and parent visibility
- A private report is not a public ballot
Voting belongs to eligible public items. Pending-review ideas and private bug reports are not public ballots.
If an item is unavailable or its visibility changes, respect that result rather than trying to bypass moderation.
Step 10
Read, vote deliberately, confirm uncertainty
- Vote or remove exactly your own vote
- Reload after an uncertain result
Read the item, vote deliberately, and use the same control to remove your own vote when needed.
After an uncertain result, reload before changing it again. Keep identity limits, cosmetic Pro and development status separate.