Decisions explanation
Decisions are a simple way to show community input inside Lets.
They are for product feedback inside the app. In beta, the principle is one account - one voice, while the team reviews safety, abuse, and rules.
When Decisions are useful
Decisions fit topics where the team needs a clear signal from participants and should show what happened after the discussion.
01
Choose between community ideas
For example, which discussion format feels clearer, which topic needs its own space, or which beta flow should be tested next.
02
Report rules that feel unclear
When a rule is hard to understand, a Decision can show that the wording needs review and a simpler explanation.
03
Show product priorities
Participants can show which improvements matter more: notifications, privacy settings, feed quality, or discussion tools.
04
See what happened next
A result can lead to a team note, public report, experiment, or explanation that the topic needs more review.
What Decisions do not replace
Voting helps the team understand the direction of feedback, but it does not override product rules or turn a sensitive issue into a public case.
- Votes do not replace safety rules.
- Reports still go through support and admin review.
- Results guide product priorities, but they are not formal approvals.
- The team can limit spam, duplicate accounts, pressure, and material that breaks the rules.
Where to read next
For safety issues, start with the Safety center or support. For broader context, use the FAQ, White Paper, Community guidelines, public reports, and Decision boundaries.