Documentation
Slack and Microsoft Teams
Connecting REAP to Slack (opens in a new tab) and Microsoft Teams (opens in a new tab): prerequisites, permissions, setup, what is read and written, troubleshooting.
Overview
Investigation summaries and runbook results where your team already works. In-chat approvals are confirmed per pilot; console approvals are available.
Prerequisites
- Slack (opens in a new tab) workspace or Microsoft 365 tenant
- Permission to install an app / register a bot app scopes
Permissions requested
| Scope | Permission | Why |
|---|---|---|
| Write | Post messages to designated channels | Summaries and runbook results |
| Interactive | Interactive approvals: scopes; console approvals available | Approvals, where confirmed |
Setup
- Install the REAP app; authorize the channels.
- In REAP: map approval roles to users/groups; choose channels per site or domain.
- Test a summary post; test an approval round-trip where in-chat approvals are in scope.
What REAP reads
- Approval responses and their authors
What REAP writes
- Investigation summaries, approval requests, runbook results
Troubleshooting
| Symptom | Likely cause | Check |
|---|---|---|
| Approvals not recorded | Interactive endpoint blocked | Check egress from the collaboration platform to REAP |
| Messages missing | Channel not authorized | Re-authorize the app |
Changelog
- September 2026 · page created (draft).
Engineering to confirm
- App scopes and endpoint requirements for interactive approvals
Last reviewed: October 7, 2026 (draft) · Owner: solutions engineering · Corrections: security@reapnet.ai