Your current situation

You are in charge of a large JIRA Instance with many projects. Of course, you have configured too the jurisdiction in these project by

using Project Role

 in Workflow Conditions,

in Permissions Scheme

 and Notification Scheme. Also your colleague

as Project Administrators

 are able to

manage Project Role's Membership

 by themselves ... Nice !

But now ...

• These Project Administrators have also in charge perhaps more than one project with transverse Development Team requiring an access to more than project. And each time a new Team Member arrives, you have nothing to do on your side ... All works is done by the Project Administrators, they save your time ... But who save their time ?
  
  
• For a Project based on many Project Roles (Sure... it

• exists ), some team member are trying to understand why they do not have the same privileges than their other colleague. The only way to compare their memberships to the concerned Project Role is to check together the list of these memberships. It may be complex, if all stakeholder are not available ...
  
  
• A transverse team (QA, Security ... or any other) need to access many projects, then you have integrated them the jurisdiction rules by using a Group set as member of a Project Role in each concerned project, or by using directly the group in the Permission Scheme. But they want to manage by themselves the member of these group ... Not so easy ! 
  
  
• Due to some good reason, you have activated the Nested Groups ... Fun, but not easy to check who is member of these groups, and how to let know Project Administrator and Team to identify that some users are able to see their project or not.

Users and Group Management by Project Manager tries to provide you a new way to cover such requirements ...