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

# Slack

**Manage › Slack** (admin-only) turns on messages to the team's Slack.

## Messages

Each kind of message posts to its own channel through an incoming webhook:

* **Someone new signed in and needs a role**
* **A scout's shift starts in 3 matches** (one post per shift, listing each station's scout)
* **A scout is assigned a team to pit scout**
* **A scout is asked to collect data**

For each kind, paste a **Webhook URL**, set the **Channel**, and **Send test** to check it.

Pings @-mention people who have a Slack member ID, set in **Manage › Users**.

## Direct messages

Each kind can also message each person directly. Once:

1. At api.slack.com/apps, make a Slack app with the `chat:write` bot scope, install it, and turn on App Home › Messages Tab.
2. Under **Direct messages**, paste its Bot User OAuth Token (`xoxb-…`) and save.
3. Tick **Also message each person directly** on the kinds you want.

Only people with a saved member ID get a direct message. A kind can send only direct messages, with no webhook. **Remove token** stops direct messages.

## App URL

Set **Where RAIDScout lives** under **App URL**, so messages link back to the app.

## Asking from Slack

Strategists, drive coaches and admins can ask scouts for data without opening RAIDScout by mentioning the team's Slack bot:

> @RAID ask 1678 how long their climb takes

The bot files it under **Scout › Questions** at the active event and says so in the thread. When a scout answers, the answer is posted back to the thread with an @-mention of whoever asked.

* The team is the first number in the message that's a team at the active event; the question is the rest.
* The asker is matched by the Slack member ID saved in **Manage › Users**.
* This needs the bot token saved, the app URL set, and some one-time setup by whoever maintains the app.


---

# 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/slack.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.
