Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Project Role (atlassian-addons-project-access) has been added to our project permissions?

A new user role has been added to all of our permissions, but we did not add it. Does anyone know what this user is and if we need it? I assume it was part of the maintenance push from last week, but am not 100% sure. 

3 answers

1 accepted

6 votes
Answer accepted
seb Atlassian Team Jul 22, 2015

When a Cloud add-on is installed into your instance that requests permission to view project data, a new group is created "atlassian-addons-project-access". We put a user in this group which is only available to the add-on.

This allows you to finely restrict access from specific projects. By default, the add-on is given access to all projects.

The concept is nice (giving fine-grained access to project admins). BTW we have problems with JIRA Service Desk right now, the add-on can not access JIRA Service Desk projects (server to server) as it receives a 404 error (add-on user has the atlassian-addons-project-access role as you mentioned). Any ideas? (so far this problem occurs for us only for Service Desk projects)

Seems like when we create new Service Desk projects, a new permission scheme is created for each and the atlassian-addons-project-access is not part of that scheme.

Like # people like this

I had installed an add-on and noticed a difference when I couldnt view new service desk projects that I created as site admin itself. Thank you for sharing this clear response @seb. Really helpful!

Like Calvin Laarakkers likes this

Not a good idea to give addons all access to your data. Of course atlassian checks cloud addons, but who can be sure that the plugin does not have a time bomb or steals passwords or credit card numbers from issues?

I would prefer that an addon lists required permissions in documentation and that admin can choose which addon has access to this or that data in project. E.g. sprint addon may schedule issues and transit them, but it should not read comments nor description.

Hey Amanda, in case this user is the System Administrator, than this could be related to any troubleshooting / workaround being executed from Atlassian's end. In case not, I believe you may want to open a ticket to Support.


Rodrigo Silva 

Did you install an Atlassian cloud add-on recently? This looks like a automatically created group from an Atlassian Connect add-on to give it the required permissions that it's scopes requested at install time.

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you