> ## Documentation Index
> Fetch the complete documentation index at: https://docs.onset.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Reactions

> Let readers react to releases and see what actually lands.

Reactions are the lowest-friction feedback you can collect. A reader doesn't have to write anything. One click tells you whether a change resonated.

## Enable reactions

Go to **Settings → Page → Releases** and enable **Release reactions**: *"Allow users to react to releases."*

Reactions then appear at the bottom of each release on your public page and in the widget.

## Reading the results

Reaction counts show up on each release in your dashboard. What to look for:

* High reactions and no support tickets: the change was clear and welcome.
* Lots of traffic but almost no reactions: either it didn't matter to readers, or the notes didn't explain why it should.
* A negative skew on a change you thought was minor: worth a follow-up post or a docs page.

<Note>
  Reactions are anonymous signal rather than a survey. Use them to decide what to look into, and confirm with something more specific before acting.
</Note>

## Related

For deeper feedback on things you haven't built yet, use [roadmap voting](/guides/roadmap/voting) instead.