> 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

Use reactions to acknowledge or triage comments without replying.

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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.