> 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/raidlogs/getting-started/sign-in-and-access.md).

# Sign in and get a role

Sign in with the team login you use in every RAID app. A new account has no role and sees only "Ask an admin to add you" until an admin gives it one in **Manage › Users**.

| Role        | Opens                        | Can do                                                                                          |
| ----------- | ---------------------------- | ----------------------------------------------------------------------------------------------- |
| Pit crew    | Matches, Event setup         | Log matches, upload and tag their logs, set up events, batteries and drive teams                |
| Programmer  | Matches, Event setup         | Everything pit crew can, plus **Event setup › Checks**: turn checks on and off, tune thresholds |
| Drive coach | Matches                      | Read matches, their report cards and logs; post the match debrief from Slack                    |
| Admin       | Matches, Event setup, Manage | Everything, plus roles, users, seasons and API keys                                             |


---

# 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/raidlogs/getting-started/sign-in-and-access.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.
