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

# Mentions

Notify teammates from a recording comment by mentioning them.

Use mentions when a teammate should review a specific thread.

They keep the request tied to the exact recording context.

### Mention a teammate

{% stepper %}
{% step %}

#### Start a comment

Open a new comment, or edit an existing one.
{% endstep %}

{% step %}

#### Type `@`

Type `@`, then choose a teammate from the mention list.
{% endstep %}

{% step %}

#### Post the update

Save or post the comment to send the mention.
{% endstep %}
{% endstepper %}

### What happens next

The mention appears in the comment and Screendesk notifies the teammate.

Mentions work in new comments and edited comments.

### Good uses for mentions

* Ask engineering to confirm a bug.
* Bring support into the customer context.
* Ask product to review severity or priority.

### Permissions

Watch-only users can read mention threads, but 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 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/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 `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.