> 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

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.