Magic LibrarySummary: Why Thread Requires Slack Permissions
Thread’s Slack integration is designed to bring ticket updates, notifications, and automated workflows directly into Slack. To do this securely and reliably, the app needs permission to read messages, identify participants, respond to events, and send updates. Thread does not access or store Slack data that is not directly required for message syncing or ticket actions.What the permissions enable
- Message syncing – Reads channel and DM messages where the app is present to align Slack conversations with tickets in Thread.
- User identification – Retrieves names, emails, and profile basics to map Slack users to the correct contacts.
- Workflow automation – Listens for message events, reactions, and commands that trigger automated ticket actions.
- Posting updates & replies – Sends ticket updates, confirmations, and automated responses back into Slack channels and DMs.
- File handling – Reads files attached to Slack messages and uploads files needed for ticket workflows.
What Thread does not do
- Does not retain Slack data beyond what’s required for ticket context
- Does not use permissions for analytics or workspace-wide monitoring
- Does not access private content outside allowed scopes
Why User + Bot scopes
Slack separates “user access” and “bot access,” even when the capability overlaps. Thread uses both because:- User scopes allow user-initiated actions (like DMs or thread replies)
- Bot scopes allow consistent automated behavior (like posting updates or receiving events)
User Scopes
These scopes allow Thread to perform actions or read information on behalf of the authenticated Slack user.Bot Scopes
These scopes allow the Thread bot to read messages, respond to events, and send updates within Slack channels and DMs.
Alongside these scopes, Thread subscribes to Slack events (such as direct messages and reactions) so the bot can react in real time. Event subscriptions are configured in the Slack app itself and are covered by the message and reaction scopes above.
See Security updates in the changelog.