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

# Comments and mentions

Discuss a recording or bug report in its activity timeline, mention teammates and react.

Every recording and bug report has an activity timeline for your team's discussion. Watch only members can read it but can't comment, mention or react.

{% embed url="<https://app.screendesk.io/recordings/8028a398-9acc-4362-b420-67ef7232a523>" %}

<figure><img src="https://3820804400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfW6XSzJSKsNyZnOkSJPt%2Fuploads%2Fd9hSKtcWuZzRpRGcbCb2%2Fdocs-window-recording.png?alt=media" alt="A recording with its comments"><figcaption></figcaption></figure>

## Comment

Write in **Write a comment or @ to mention** and post. You can **Attach images**, and on videos **Insert timestamp** adds the current playback time so readers can jump to that moment.

Hover a comment to **Edit**, **Delete**, **Copy link to comment** or **Add reaction**. Authors can edit and delete their own comments, and admins can edit or delete any. Edited comments are marked as edited.

A comment link opens the recording at that comment. It doesn't grant access: the person still needs to be able to see the recording.

## Mention

Type `@` and pick a teammate. The comment lands in their [Inbox](https://docs.screendesk.io/organization-and-workflows/overview.md) and, unless they turned it off, they get an email. Adding a mention when you edit a comment notifies that person too.

## Follow

Commenting makes you follow the conversation, so new comments land in your Inbox. Assignees get new comments too. To follow without commenting, select the bell at the top of the timeline; select it again to stop.

## React

**Add reaction** offers a fixed set: 🐛 Bug, 💜 Love it, ✅ Fixed, 👀 Oooo, ❓ Unclear, 👏 Bravo, 🔥 Fire and 👍 Got it. Reactions group under the comment.


---

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