Restricting user group to a specific collection of ever-changing projects?

Matthew Walker_xs6lpl

Is there a way to organize projects into groups to which I can grant user-permissions? 

The goal is to avoid having to set multiple project permissions for each new Project, of which we have numerous starting each day, each which has one of 20 unique teams (both internal and external users).  It would be great to be able to create a Project and then, by associating it with a certain Project "container", associate its permission schemes immediately, in one step. Category evidently can't - nor was intended - to be used this way, so I'm thinking there's perhaps no easy solve.

If there's no out-of-the box solution, is there an add-on that allows for this?

Earl McCutcheon

Hello @Matthew Walker ,

For your use case "organize projects into groups" you can set up permission schemes for the projects so that a shared set of permissions are applied to the projects so that they will line up across all the projects applied, then within the Permission scheme you can set these to project roles with a default membership set to a group.  

If you set up the project to use role membership in the permission scheme with groups assigned to the Role by default, all the new projects created will use the group access, but gives project admins the ability to edit the roles later on if additional restrictions are needed to lock the project down further or expand to include additional groups or users by adding and removing role membership ad-hoc.

We have a really good walkthrough covering the concepts for this in the KB "How to restrict project access for teams in Jira Cloud" and details on setting up the default role membership for the groups can be found in the  "Managing project roles"  documentation.

Regards,
Earl