Trust

Flywheel Slack Scope Inventory

This page documents Flywheel’s current Slack bot-token footprint and why each permission exists.

Flywheel keeps a reviewed public inventory of its current bot-token scopes so teams can inspect minimal Slack access before or after install.

Each scope below is tied to a concrete runtime behavior already present in the MVP. If a scope is not needed for a live feature, it should not remain in the app.

`app_mentions:read`

Trigger Flywheel from top-level channel mentions.

`canvases:read`

Read Slack canvases referenced in conversations so their contents can become agent context.

`canvases:write`

Create Slack canvases when Flywheel needs to deliver longer structured output.

`channels:history`

Read recent public-channel messages for hot-path context and sparse fallback.

`channels:read`

Resolve public-channel metadata needed for conversation context and routing.

`chat:write`

Post Flywheel replies back into Slack conversations.

`files:read`

Read Slack-hosted files so uploaded artifacts become agent context automatically.

`files:write`

Upload files when Flywheel needs to return artifacts to Slack.

`groups:history`

Read recent private-channel messages when Flywheel is installed there.

`groups:read`

Resolve private-channel metadata needed for conversation context and routing.

`im:history`

Handle direct-message conversations with Flywheel.

`im:read`

Resolve direct-message metadata needed for conversation context and routing.

`im:write`

Open a direct message with a linked member when Flywheel needs to send a private follow-up.

`mpim:history`

Handle multi-party direct messages with Flywheel.

`mpim:read`

Resolve group direct-message metadata needed for conversation context and routing.

`reactions:write`

Add and remove the in-flight hourglass reaction during execution.

`users:read`

Resolve Slack user IDs into human display names for context.