> 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/getting-started/finding-your-way.md).

# Find your way around

RAIDScout is organised by job. The sidebar lists the places you can go, and the one that's open shows its tabs underneath. On a laptop the sidebar folds down to icons (⌘B or Ctrl+B); on a phone, open it with the menu button at the top left.

The top bar shows where you are and which event is active.

## Destinations

{% tabs %}
{% tab title="Phone" %}
![The sidebar with Data open and its tabs (Teams, Match entries, Audit, Calculated) under it, Help and the account at the bottom, on a phone](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-b1b0f16fbf293aa409407756160956ed05cd50ed%2Fsidebar-phone.jpg?alt=media)
{% endtab %}

{% tab title="Laptop" %}
![The sidebar with Data open and its tabs (Teams, Match entries, Audit, Calculated) under it, Help and the account at the bottom, on a laptop](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-14aed20cdbfc28190a31ec792f10268f00804cdb%2Fsidebar-laptop.jpg?alt=media)
{% endtab %}
{% endtabs %}

| Destination            | Tabs                                                                                                                                                           | Who sees it                                                                                                                     |
| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| **Home**               | What to do next for each of your roles                                                                                                                         | Everyone with a role                                                                                                            |
| **Scout**              | **Matches**, **Pits**, **Pre-scout**, **Questions**                                                                                                            | Everyone with a role                                                                                                            |
| **Data**               | **Teams**, **Match entries**, **Audit**, **Calculated**                                                                                                        | Everyone; **Audit** and **Calculated** are for scout leads, strategists and drive coaches                                       |
| **Our matches**        | A plan for each match                                                                                                                                          | Everyone with a role                                                                                                            |
| **Alliance Selection** | **Team list**, **Pick Priorities**, **Alliance Compatibility**, **Track Alliance Selection**, **My Picklists**, **Sorting Games**, **Mock Alliance Selection** | Everyone; **Pick Priorities**, **Alliance Compatibility** and **Mock Alliance Selection** are for strategists and drive coaches |
| **Manage**             | **Coverage**, **Schedule**, **Pit assignments**, **Events**, **Forms**, **Users**, **Slack**, **API keys**                                                     | Scout leads and admins; **Slack** and **API keys** are admin-only                                                               |

## What comes first follows the event

RAIDScout knows where the active event is and opens on what matters now:

1. **Before the event:** pre-scouting.
2. **Until qualifications start:** pit scouting.
3. **Once qualifications start:** matches.

Opening **Scout** with no tab chosen takes you to the right one. **Alliance Selection** opens on the **Team list** for strategists and **My Picklists** for everyone else.

## Help

**Help**, at the bottom of the sidebar, opens this guide on the page for the screen you're on. **Contents** lists every page. It's part of the app, so it works with no connection.

## Good to know

* **Everything is live.** When someone saves, every screen updates right away.
* **Links keep your place.** The address bar holds the open tab, match, team or list, so you can reload or share a link and land in the same spot.
* **The version** at the bottom of the sidebar (for example **v2026.10.22 cbfd2f3**) says which build you're running. Click it to copy it into a bug report.


---

# 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/getting-started/finding-your-way.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.
