Need help understanding how permission scheme works

Joseph Kodjo-Kuma Djomeda

Hello Guys,

Sorry if this has been discussed over and over again. I have actually read the documentation and I seem to be lacking some understanding. I created a project  A. The project is a procurement project to which I have added only administrators and Finance groups As shows below 

I have created some project roles as well shown below

I have copied the default permission scheme and assigned the copied one to the Procurement project.  To my surprise, everyone can see all the projects regardless of group added under the people section of the project. This has confused me  really. So with more readings, I am thinking I need to edit the permission scheme to use.

 

While editing the permission scheme, at the view project section,  I am not sure of what to use. The intention is that only allowed people in the "people" section of the said project should even see the project. So what is the generic way of saying here that only members of the project should see the project?

 

 

Thanks for reading and thanks in advance for all your answers.

Joe Pitt

The access model has not changed since Jira 3.6, although some of the default groups did change with Jira 7.0.  Best practices for security purposes is to only give users what they need. JIRA uses the Grant model which supports this, not a ‘restrict’ model,

The principle is:

• Grant people the ability to log in
• Grant people the ability to use the projects they need, but only the level they need.

The problem most new users have traces back to Atlassian’s default settings of allowing the "group of users that can log in and use an application", permission to everything in a project. This ends up meaning "can use application" becomes "can log in and see everything"

So, you need to delete that group from all the permission schemes.  If you do that right away life will be much easier.  In your screenshot it is the 'any logged in user'

• Go to "manage applications" and check what the login group is
• Look at all active permission schemes and check how they allow "browse" access to projects, ensuring they say something simple like "Role: user"
• Go through all your projects and remove the "can use application" group from the role of user (and others if the permission scheme says so).  Replace it with the groups and users who should have access to the project.
• Go to Admin -> Roles and change the default role memberships to be empty for users, developers and so-on.  This prevents new projects accidentally granting access to limited users