> 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/admin/manage.md).

# Manage

**Manage** is for admins.

## Seasons

Each season keeps its own data. The active season is the one everyone sees; **Set active** switches it. A season with matches, events or other data can't be deleted.

## Users

Give each person their roles. You can set a **Display name** (leave it blank to use the name from their team login) and their **Slack member ID**, which links them to their Slack posts. Slack IDs are shared by every RAID app.

## API keys

| Key                                          | What it's for                                                                              |
| -------------------------------------------- | ------------------------------------------------------------------------------------------ |
| **Schedule sync** (The Blue Alliance, Nexus) | Syncing match schedules. Without a TBA key, matches are numbered by hand.                  |
| **RAIDSystems**                              | Copying robot revisions from RAIDSystems. Make the key in RAIDSystems › Manage › API keys. |
| **Pit uploader keys**                        | Letting the pit laptop upload logs without signing in. A key can only upload log files.    |

Keys are stored encrypted; nobody can read one back, only replace or remove it. The Anthropic key for the check list and questions is set in **Event setup › Checks**.


---

# 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/admin/manage.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.
