Slack permission scopes
The Slack permission scope that the Suptask app is making use of
Last updated
Was this helpful?
The Slack permission scope that the Suptask app is making use of
Last updated
Was this helpful?
Suptask have been built with data privacy in mind from the very start where the minimum amount of permissions are being utilized to function properly. This ensures that the least amount of data and information is shared with Suptask.
Suptask is making use of different permissions within your Slack workspace in order to provide the features it comes with. Slack have standardized the permissions an application like Suptask can make use of. Therefor it is Slack itself who explains and summarizes the permissions that are asked for when your user is being authorized.
Suptask uses messages and message threads inside of channels to support its unique ticketing system. Suptask do not store any Slack messages, we are rather referencing these into Slack.
Suptask can only access the messages in a channel where the Suptask App is invited to explicitly, including public channels.
Here follows a summary of the common permissions that Suptask is using:
Basic information about channels - Used to list channels and present channel names when configuring a Ticket Form.
Basic information about users in the channel(s) - Name and ID of the users in the channels where Suptask App is invited to.
Message access - Read messages that are sent in as tickets to Suptask in the channel(s) where the Suptask App is invited to.
Send messages - Send messages to users that are using Suptask.
Shortcut & Workflows - Enable shortcuts to create tickets from messages and have Suptask available in the Slack Workflow builder.
Extended permissions are optional and can be used to create tickets using the ticket emoji in Direct Messages (DM).