The Don't Interrupt app for Slack requests only the permissions and access it needs to function effectively. These permissions, known as scopes, are necessary to interact with the Slack platform in a secure and controlled manner. Slack ensures that apps like Don't Interrupt are only granted the specific scopes they require to operate. We prioritise your security and privacy, complying with relevant data protection regulations.
This page details the permissions and access that the Don't Interrupt app requires, categorised into User Scopes and Bot Scopes. Additionally, we provide transparency about what data the app does not have access to.
User Scopes
These are permissions related to specific users who have authenticated with the Don't Interrupt app.
openid
In order to login to Don't Interrupt with a Slack account, Slack requires apps to use OpenID. This permission is the minimum requirement for this.
profile
When logging in with OpenID, this permissions lets Don't Interrupt see the users profile information such as name and avatar, these are used to personalise the users dashboard and communications.
email
In order to send emails to the users, including billing information and account changes, the email permission is required to see the authenticated users email address.
team:read
When a user adds their Slack account, they are associated with the Slack team they are in on the Teams page. This permission is needed to get the Team's name, logo URL and ID.
dnd:read
One of the main features of Don't Interrupt is to set a users Do Not Disturb settings. In order to set them at the correct time and not override the users existing settings, the app needs to be able to read the authenticated users Do Not Disturb settings.
dnd:write
A continuation of the above permission. This permission is required to set the authenticated users Do Not Disturb settings. Including whether it is enabled/disabled and how long for.
users.profile:read
The authenticated Slack users status text and emoji are within the users profile. Therefore this permission is needed to see what the users current status text and emoji are, in order to ensure we do not override it, unless the user requests it.
users.profile:write
To set the users status text and emoji, the app needs access to update the users profile. No other details are updated other than the status text, emoji and expiry.
users:read
To see if the authenticated user is offline or online, this permission is needed. No other information is used and this only gives access to the authenticated user, not others users within the Slack workspace.
users:write
In order to updated the authenticated users availability (setting the offline or online), this permission is required. No other details are updated.
Bot Scopes
These are permissions granted to the app's bot, allowing it to interact with users and channels on behalf of the app.
app_mentions:read
The bot will get notified if it is mentioned in any channels as this means the bot was invited to a channel.
emoji:read
Users can use their Slack workspaces custom emojis, as well as the full set of emojis in the unicode standard. This permission gives the app permissions to read the custom emojis in the workspace.
chat:write and im:write
This permission in combination with im:write let the app write messages in the Don't Interrupt's "app home" messages channel. This is the only channel that is written to.
im:history
To read messages in the Don't Interrupt "app home" within Slack, this permission is required. This allows the user to write messages to enable, disable and create overrides by writing in the "messages" tab.
What We Don’t Have Access To
The Don't Interrupt app takes your privacy seriously and does not request access to the following:
Private Messages: The app only has access to direct messages (DMs) that are sent to or received from the Don't Interrupt app itself. It cannot access DMs between users or any messages outside of its own interactions.
Admin Access: The app does not have administrative rights or permissions over your Slack workspace. It cannot make changes to user roles, workspace settings, or other administrative functions.
All Users: Don't Interrupt only accesses information about users who have directly authenticated with the app. It does not have visibility into non-authenticated users in your workspace.
Questions or Concerns
If you have any questions or concerns regarding the permissions and security practices of the Don't Interrupt app, please visit our Support Page for further assistance.