> 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/comments.md).

# Comments

Add, edit, and manage comments in a recording timeline.

Comments keep feedback attached to the recording itself.

Use them to capture what happened, what to check, and what should happen next.

### Add a comment

{% stepper %}
{% step %}

#### Open the timeline

Open the recording and go to the activity timeline below it.
{% endstep %}

{% step %}

#### Write your message

Select **Write a comment or @ to mention**, then enter your message.
{% endstep %}

{% step %}

#### Post the comment

Select **Comment** to add it to the timeline.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
You can attach images to a comment when a screenshot explains the issue faster.
{% endhint %}

### Edit or delete a comment

Comment authors can edit or delete their own comments.

Workspace admins can manage comments when cleanup is needed.

Edited comments stay marked as edited, so the timeline remains clear.

### Who can comment

Logged-in workspace members with access to the recording can comment, unless they are watch-only.

Watch-only users can read comments and activity, but they cannot add, edit, delete, or react to comments.

### Good comment habits

* Start with the issue, outcome, or decision.
* Mention the exact moment or behavior you mean.
* Add an image when one screenshot gives faster context.


---

# 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/comments.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.