crewkit for Slack

A Slack discussion is a thread in a Slack channel crewkit's app is in, where crewkit posts messages from your team's crewkit sessions and relays the replies people write in the thread back to those sessions. Any member of your organization who has connected their Slack account can start one, except in a data-resident organization or in a channel shared with another organization. In Claude's asking modes the member, in their own session, confirms before their Claude AI session (Anthropic's Claude) joins, and a session run in a mode that asks nothing (auto or bypass permissions) joins and posts without asking; a session started as sensitive cannot join. Read how a session joins a discussion for the details. Slack discussions are off until an organization admin turns them on.

1. As an organization admin, sign in to crewkit and select your organization.
2. Open Settings → Integrations, find Slack under Messaging, and choose Connect Slack to add crewkit to your Slack workspace. Complete Slack's authorization flow.
3. Open Settings → Organization → Slack discussions and turn Slack discussions on.
4. Each member connects their Slack account at Profile → Slack.
5. In the Slack channel for the discussion, run /invite @crewkit to add crewkit to the channel. Discussions cannot open in a channel shared with another organization.
6. In that channel, run /crewkit discuss <topic> to start a discussion.

Bot scopes

• chat:write — Post, update and delete crewkit's own messages, including private notices to one person. When a person is erased in crewkit, crewkit asks Slack to delete the messages it posted for them.
• chat:write.customize — Post agent replies under the agent's display name and icon, and discussion messages under the name of the crewkit member who sent them.
• app_mentions:read — Receive mentions of the app so agents can respond.
• channels:history — Receive message events in public channels where the app participates and, when crewkit cannot confirm its opening post reached Slack, read that channel's recent top-level messages to find it (see the privacy policy).
• groups:history — Receive message events in private channels where the app participates and, when crewkit cannot confirm its opening post reached Slack, read that channel's recent top-level messages to find it (see the privacy policy).
• im:history — Receive message events in direct messages with the app.
• mpim:history — Receive message events in group direct messages where the app participates.
• users:read — Look up a reply writer's Slack display name for discussion replies.
• commands — Handle the /crewkit slash command to start a discussion.
• channels:read — Read public channel details and membership, and receive membership and sharing events, so a discussion opens, is listed and stays open only where its members are connected.
• groups:read — Read private channel details and membership, and receive membership and sharing events, so a discussion opens, is listed and stays open only where its members are connected.

Sign in with Slack scopes

• openid — Connect your Slack user id and workspace id to your crewkit account.

Read Slack discussions privacy for what crewkit posts and keeps, retention, and erasure. See Security and Abuse for security reporting, or contact crewkit support.