> For the complete documentation index, see [llms.txt](https://docs.raidrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raidrobotics.org/raidscout/admin-guide/users-and-roles.md).

# Users and roles

**Manage › Users** lists everyone who has signed in. Use **Filter by name or email** to find someone.

A new account has **No role** and sees only a message to ask an admin. If Slack is set up, a message says when someone new signs in and needs a role.

{% tabs %}
{% tab title="Phone" %}
![Manage › Users with Filter by name or email, and each person's roles with Roles and a ⋯ menu, on a phone](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-80c47a08ae7f2a73553f388124926488e3264f28%2Fmanage-users-phone.jpg?alt=media)
{% endtab %}

{% tab title="Laptop" %}
![Manage › Users with Filter by name or email, and each person's roles with Roles and a ⋯ menu, on a laptop](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-d861bf02dd55b5e029597900593daaed56eb0452%2Fmanage-users-laptop.jpg?alt=media)
{% endtab %}
{% endtabs %}

## Give or change roles

Open **Roles** on a person's row and tick the roles they need: **Admin**, **Scout Lead**, **Strategist**, **Drive Coach**, **Scout**. A person can hold any mix.

* **Admins** can change any role, rename and delete people.
* **Scout leads** can turn only the **Scout** role on or off. Every other change is admin-only.

Ticking or unticking **Admin** asks first (**Make admin** / **Remove admin**). They keep any other roles they have. You can't remove your own admin role.

| Role        | Opens                                                                                                                                                     |
| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Scout       | Home, Scout, Data, Our matches, Alliance Selection                                                                                                        |
| Scout Lead  | Everything a scout opens, plus Data › Audit and Calculated, and Manage (all but Slack and API keys)                                                       |
| Strategist  | Home, Scout, Data (with Audit and Calculated), Our matches, Alliance Selection (with Pick Priorities, Alliance Compatibility and Mock Alliance Selection) |
| Drive Coach | The same as Strategist for now. Their **Not a fit** marks are seen only by strategists and drive coaches                                                  |
| Admin       | Everything                                                                                                                                                |

## Slack member ID

Set a person's **Slack member ID** so pings @-mention them and so they can ask questions from Slack. In Slack: their profile › ⋯ › **Copy member ID**. Leave it blank to clear it.

The ID is shared with every RAID app. People see theirs in **Profile** but can't change it.

## Rename or delete

The person's ⋯ menu (admins only) has:

* **Display name**: change the name the team sees.
* **Slack member ID**.
* **Delete user…**: removes their account and roles. Data they entered stays. You can't delete yourself.


---

# 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.raidrobotics.org/raidscout/admin-guide/users-and-roles.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.
