This page lists each permission Thorpe asks for when you add it to Slack, so you can check them before you approve the install.
Bot scopes only
Slack calls these permissions scopes. Thorpe asks for bot scopes only: it acts as the Thorpe app, never as a person in your workspace. It asks for no user scopes and no admin scopes.
Each scope and why
| Scope | Why Thorpe needs it |
|---|---|
channels:history | Receive messages posted in the public channels Thorpe is in, so customer messages open requests and your team's thread replies count as answers. |
groups:history | The same for private channels you invite Thorpe to. |
channels:read | See the public channels Thorpe can join, their names and their members, and notice when a channel is shared or stops being shared, or when people join or leave it. |
channels:join | Join the public customer channels an admin picks during setup. |
groups:read | See the names and members of the private channels Thorpe is in. |
chat:write | Post as Thorpe: request cards and SLA alerts in the triage channel, the weekly digest, card thread updates, and the messages your admins turn on, such as the rating prompt. |
im:write | Open direct messages, for SLA alerts to owners, claim reminders, the daily owner list and replies to private requests. |
im:history | Receive messages people send to Thorpe directly, for private requests. |
users:read | Read people's names, which workspace they belong to, and their Slack status. The workspace is how Thorpe tells your teammates from your customers, and a status such as 🌴 marks a teammate away. |
reactions:read | See emoji reactions, such as 🙋 when a teammate claims a request, or 👍, 😐 or 👎 on the rating prompt. |
reactions:write | Add Thorpe's own reactions: 👀 on your team's first reply to a request, and in private requests 👀, ✅ and ⚠️ to show a message arrived, was delivered or was not delivered. |
team:read | Read your workspace's name, to use in messages to customers, such as the private request greeting. |
commands | Required by Slack for message shortcuts, such as Track as request and Discuss internally. |
What Thorpe reads
Slack sends Thorpe messages only from channels it has been added to. Thorpe opens requests only in the channels an admin marks as customer channels. Channels and stakeholders explains the channel types.
When Thorpe asks again
If your workspace's install of Thorpe doesn't include im:history, Settings > Private requests says Thorpe needs one more Slack permission to receive private messages. Choose Update Slack permissions and approve it in Slack.
Some coming features need more bot scopes. For example, the SLA bookmark in customer channels needs bookmarks:write. Thorpe will ask for each one when its feature ships, and it will still be a bot scope.
Removing Thorpe
Uninstalling Thorpe from Slack removes every permission at once. Thorpe deletes its Slack tokens straight away. Privacy and security says what happens to the rest of your data.
What's next
- Getting started walks through install and setup.
- Privacy and security explains what Thorpe stores and for how long.