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

Permission Schemes or Project Role for this situation?

Hi everyone.

We're configuring our new Jira account and here's the situation. We have 2 types of users, let say, Developers and Clients. In both cases, we don't want them to see all projects and we want to define their permissions properly.

So what we noticed that we can easily do that with project roles, except that we need to re-create that role for every single project. We couldn't find a way to create a project role re-usable to all of the projects.

Looking at the permission schemes, we can assign permissions similar to project roles, but not limiting seeing the project list.

What would be the best way?

Thank you in advance.

4 answers

1 vote

There's a bit missing from your question - whether the project is a Classic or Next-Gen project.

For classic projects, project roles are global.  Let's imagine you go to Admin -> System -> Security -> Project Roles and add "Cat wrangler" to the list of roles.  When you next go to any project and use Admin -> People, you will find "Cat wrangler" appears when you click the "roles" button for the role to work with.  You'll find "Cat wrangler" immediately available in the permission schemes too.

For Next-gen projects, no, the roles are local to the project.  I'm afraid there is no way to add a global role to them.  (This is one of the reasons I hold up Next-gen projects as "not ready for real use yet")

Dirk Ronsmans Community Leader Jan 21, 2021

The mention of permission schemes led me to believe it would be Classic

Same here, but the "couldn't create re-usable role" jumped out (had a conversation with yet another client yesterday which ended in "yeah, don't use Next-gen, they're not ready yet")

Had tried it on next-gen, will do on classic

0 votes

Hi @Raph 

Project roles are created globally for an instance. Once you create a role like Developer, Tester, Manager etc then within each project the project admin can add people to these roles. What these role can do depends on the permission scheme.

So using project roles is a good idea so you don't have to create multiple permission schemes, unless you really have to.


0 votes
Dirk Ronsmans Community Leader Jan 21, 2021

Excactly, roles is always a best practice.

You would add the role to the permissions scheme and then the project admin would add the users for that project to the role.

So it would be

  • permission scheme
    • Project Role
      • User

A permission scheme can be shared throughout the projects and you would define the users by granting them the role on a specific project.

Thanks for your answers, very appreciated. I'll try this shortly.

Suggest an answer

Log in or Sign up to answer
Site Admin

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