> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/getting-started/work-with-your-team/mentions-in-dscout.md).

# Mentions in Dscout

Mentions can be used to tag in your colleagues or Dscout Research Advisor team in notes + comments to share interesting data, start a conversation, or collaborate on your research design.

{% hint style="info" %}
**Don't see the ability to @ mention a colleague?** At this time, Mentions are only available for subscription accounts. Chat with your Account Manager to learn more!
{% endhint %}

## Mentioning a project member

Use @ mentions in Dscout to tag your colleagues in screener, entry, or interview session notes.

1. Click into an individual application, entry, or interview session.
2. Click into the “Notes” tab on the righthand sidebar.
3. Begin typing “@” and the person’s first name, last name, or username. As you type, a dropdown list will appear with matching project members to select from. Project members are mentioned by their username.

As a reminder, **notes are only visible to other researchers, not to scouts**. No scouts will ever see notes or mentions between researchers!

### Diary studies

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/0iWdB4F0B8EklZssOads/360048982452)

### Screeners, usability tests, and media surveys

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/KBu2I4dUCdmUDm3aYfil/21741859679252)

### Interview studies

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/1NguwdLGJOVt0IeVRIhB/21741864957588)

## Mentioning a Dscout Research Advisor

When you submit a screener or study for review, your Dscout Research Advisor will collaborate with you via comments + mentions. Utilize @ mentions to call your Dscout Research Advisor's attention to anything you'd like their input on.

1. Create a comment in the Builder section of your study or screener
2. Type “@” followed by the name of your Research Advisor
3. Select their name to notify them of your comment

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/7nW7jK5JXteDTGR7iRlV/21741864963476)

## Receiving notification of mentions

Whenever you’re mentioned, you’ll receive an email notification. Email notifications include the note text and a direct link into the relevant application, entry or session in Dscout.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/AqFvvgSNS7xk7yCKefef/360049112071)

## Changing your username

When you create your account, Dscout will automatically create a username for you. It’ll be something like *firstnamelastname*—it may also have a number at the end. This username is only used for other researchers to mention you in notes—it’s **not** used for logging in (you’ll still log in with your email address).

If you’d like to change your username, navigate to your Dscout Profile settings by clicking your profile picture in the top-right corner, then selecting “Profile.”

Write your desired username in the Username field, then click “Update Profile” to save. You can change your username to any name that is not taken. Usernames must be at least 3 characters and can only contain letters and numbers.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/EFVxqsNDL3GCYhRgeEmB/360048982472)


---

# 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://help.dscout.com/getting-started/work-with-your-team/mentions-in-dscout.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.