Understanding Jira's Required Permissions for Slack Integration
Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.
Summary
This knowledge base article explains why Jira requires specific permissions for its integration with Slack. These permissions are essential for the seamless operation of the integration, allowing users to interact with Jira issues directly from Slack channels.
Required Permissions and Their Purposes
For the new on-boarding flow, all scopes will be requested at the point of installation. The reason for this is so that the installer user has a user token stored for them at the time of installation, and does not need to re-authorize when enabling the issue panel.
Here are some specific elaborations on the required permissions:
| Permission | Purpose | Usage |
|---|---|---|
| im:read, mpim:read | These permissions allow the app to access the names of direct message (DM) and multi-party instant message (mpim) channels. | When a user performs an action in these channels, such as adding a Slack message to a Jira ticket, the channel name is used in the link back to Slack from Jira. |
| links:read, links:write | These permissions enable the app to detect if a pasted link is a Jira ticket from an Atlassian site. | If a Jira ticket link is detected, the app posts an unfurl message with useful context about the ticket to everyone in the channel. |
| channels:write, groups:write | These permissions allow the bot to invite itself into public or private channels. | This typically occurs during the onboarding flow or when posting in a channel once a connection is established. |
Partial permissions
The integration requires all permissions to function correctly, and partial permissions are not acceptable.