> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/organization-and-workflows/collaboration/reactions.md).

# Reactions

Reactions keep the timeline lighter.

Use them to acknowledge a comment or signal status without adding another reply.

### Add a reaction

{% stepper %}
{% step %}

#### Hover the comment

Move over the comment you want to react to.
{% endstep %}

{% step %}

#### Open reactions

Select the reaction button.
{% endstep %}

{% step %}

#### Choose a reaction

Pick the reaction that matches your response.
{% endstep %}
{% endstepper %}

Reactions appear under the comment and group by reaction type.

This makes it easy to see what was acknowledged or needs attention.

### Good uses for reactions

* Acknowledge that you saw a comment.
* Show agreement on a decision.
* Mark a note as ready for follow-up.

### Permissions

Workspace members who can comment can react to comments.

Watch-only users can see reactions, but they cannot add or remove them.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.screendesk.io/organization-and-workflows/collaboration/reactions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.