How I can Manage the Permissions in Next-Gen Projects (Cloud) ?

[Essam.Fahad@btc.com.bh]

All Users can Manage and Update Projects in Next-Gen and the Role atlassian-addons-project-access Seems to be granted and cannot Be Revoked . I need A Quick Fix and An Easy one without any work around .

[Earl McCutcheon]

Hello Essam,

First off the permissions set for "atlassian-addons-project-access" are set by default.  They are not intended to be changed, and should not be altered in any way as they are a special system group that give apps from the marketplace an elevated permission set in the background required by the apps to complete administrative actions.  Additional details on this can be seen here.

Next check out the following Documentation on Next-Gen permissions, and the settings for the permissions are under "Project Settings >> People":

• Overview of permissions in next-gen projects

By default when creating a Next-Gen project with the most open settings everyone is granted the Member role as covered in the article above will set permissions as the following:

The project's access level gives any logged in Jira Software user a certain role in your project:

• Open. When a next-gen software project is open, Jira gives all licensed users (regardless of application access) the Member role. People can view your project’s issues, and create or edit issues in your project.

• Limited. When a next-gen software project is limited, Jira gives all users on your Jira site the Viewer role. They can search for and view issues in your project, but they can’t create or edit them.

• Private. When a next-gen software project is private, you manually give people access to your project via the People page in your project's settings. If you haven’t added a person or group, they cannot search for, view or interact with your project’s issues in any way. Read more about adding people to a next-gen project.

The behavior you are describing sounds like the option of the Administrator role has been granted to Anyone with access to the Jira instance.  If this is the case, you are required to have at least one admin in the project to remove an admin role so make sure you or a group you are a member of that you want to have admin permissions in the project are listed as an administrator explicitly on the people page, then either remove the "Anyone with access" from all roles or set them to Member or viewer.

Regards,
Earl