Permission helper shows me that <USERNAME> is not part of the atlassian-addons-project-access role

[Peter Mazur]

Hi there.  When I try to test user access to various projects they all keep getting similar errors: "<USERNAME> is not part of the atlassian-addons-project-access <USERNAME> is not part of the atlassian-addons-project-access role role."  Solutions suggested by Permission helper is to add <USERNAME> to that role, which is not possible. That's because atlassian-addons-project-access is a system role.

This issue affects all of my projects that I'm trying to migrate from on-prem serve to the cloud.

Anybody has an idea what is workaround for this?

[Trudy Claspill]

Hello @Peter Mazur 

What specific permission are you trying to validate for the user? What is the actual problem you are trying to solve?

Can you show us the output of the Permission Helper screen?  

Generally access to projects is based on the Browse Projects permission in the Permission Scheme assigned to the projects. Check the Permission Scheme for the projects to see which roles and user groups are assigned to the permissions and confirm that the user is assigned to the necessary roles and/or user groups.