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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

People VS Permissions in Company Managed Project

Hi All,

For a Company Managed Project, you can define a set of Permissions based on Groups, Roles, etc. It seems to me that you can almost manage all access security from this setting. However, in Project Settings there is also a "People" item (left column).

In my tests, if I create a project with limited access (for example an HR project), I can manage it well with Permissions.
But if I click on People, in Project Settings, I see ALL the roles that I have created in Jira, including the roles of standard users who do not have access to this HR project.

What is the difference between "Permissions" and "People "security in Projects settings (company managed projects)?



2 answers

1 accepted

2 votes
Answer accepted

Hi @Bernard Van Heuverswyn

In the permissions tab, you'll see the 'Permission Scheme' that is associated to the project.
The permission scheme is a mapping of all individual project permission to users, groups or project roles. One permission scheme might be used in multiple projects, so that's why those permission are not mapped directly inside the project.

The peoples tab displays the mapping of users/groups to project roles.

Only if you use a specific project role in the permission scheme does it mean something within the context of the project if a user is assigned to that project role.

Project admins can only assign user to project roles, not user groups. That's because project role assignment is project specific while user groups are global.

Therefore Jira recommends to use mostly project roles in permission schemes so that project admins have the flexibility to grant project permission themselves.

I hope that helps, please check the official documentation for more infos

Thanks for this answer. Yes, I have already set up these Roles, groups, permission schemes.. and it seems to work fine. But in the "Project Settings", the point "People" seems to be redundant to me.

Kelly Arrey
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Apr 25, 2023

The People tab is the place where project admins assign people and/or groups to roles for that project, in contrast to the global default roles set at the system admin level.

Like Bernard Van Heuverswyn likes this

Ok, super. Thanks for your help 

Like Kelly Arrey likes this

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events