> 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/screen-recorder/debug-a-capture/collaboration/mentions.md).

# Mentions

Notify teammates from a capture comment.

Use mentions when a teammate needs to review a specific part of the conversation.

### Mention a teammate

{% stepper %}
{% step %}

### Start typing

Type `@` in a new or existing comment.
{% endstep %}

{% step %}

### Pick a teammate

Choose the right person from the mention list.
{% endstep %}

{% step %}

### Send the comment

Screendesk adds the mention and notifies that teammate.
{% endstep %}
{% endstepper %}

### When to use mentions

* Ask an engineer to confirm a bug.
* Bring a support teammate into the customer context.
* Ask a product teammate to review behavior or priority.

### Access

Watch-only users can read mentions.

They cannot create comments or mention teammates.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.screendesk.io/screen-recorder/debug-a-capture/collaboration/mentions.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 `build a script that syncs our docs to a CMS` 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.