nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira / Slack - Can it be read-only? Can we block interacting with Jira through Slack?

Marta Zapatero_2jw0md

We have recently migrated from Jira Server to Cloud.

We're interested in getting Jira notifications on Slack up and running again- the usual "new issue created, new issue assigned to you. you have been mentioned in this issue" etc.

But for security, data integrity, and user permission reasons, we want it to be A ONE-WAY CONNECTION. We want to disable ANY kind of interaction from Slack, such as changing the status or commenting on the issue. To interact with the issue, a user should click on the link in the message to open Jira and do it from there.

We know Atlassian ensures everything is secure, but our tech leads would much rather replicate the way Jira Server / Slack integration worked.

The Jira Cloud for Slack marketplace page mentions management settings, but it has no documentation about what options there are to manage permissions and interactions.

So if anyone has that information, I'd be very grateful!

PD: We're only allowed to use official plugins (either Atlassian or Slack), so third-party marketplace app suggestions won't do, no matter how cool they are

Accepted answers

Marta Zapatero_2jw0md

After contacting Atlassian Support and doing our own tests, we reached the conclusion:

> Note: This stands true as of September 2025. Who knows if it will change in the future.

As Slack and Atlassian formed an official partnership, Slack integration in Jira Cloud has become much more seamless, and does not work like common marketplace apps.

This means that it skips "atlassian-addons-project-access" and uses directly the permissions of the user that has linked their Slack and Jira accounts.

So, removing that permission from project schemes does not prevent user actions from Slack.

However, Slack administrators can block Slack users' permission to interact with the Jira bot. They will not be able to authenticate with it, so they won't be able to interact with Jira issues from Slack. This will also mean they won't be able to configure personal notifications for issues they create/watch/are assigned to.... but at least the integration can be used as a global link unfurler to preview issues, and to send notifications to channels, as long as select Jira/Slack admins configure those.

All comments

arielei

Hello @Marta Zapatero

In the project permission scheme remove the "atlassian-addons-project-access" role from the create work-item option.

Marta Zapatero_2jw0md

Thank you very much!

And would we be able to give different roles to different addons, or is it forced on all of them? We want Slack to have read-only access, but we may want Jenkins to update issues.

Marta Zapatero_2jw0md

I would like to update this, so anyone who stumbles upon this post in the future is informed:

Since Slack became a built-in integration, it's not affected by "atlassian-addons-project-access" and uses directly the permissions of the user that has linked their Slack and Jira accounts.

Marta Zapatero_2jw0md

This means that it skips "atlassian-addons-project-access" and uses directly the permissions of the user that has linked their Slack and Jira accounts.

So, removing that permission from project schemes does not prevent user actions from Slack.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

slack

atlassian-marketplace-cloud