Individual Group Administration Permissions

Allow Crowd to be used in a delegated environment where program managers take responsibility for their team members access to their repositories. Currently only a Crowd administrator can add users to groups which means that all user access allocation needs to be done by a central team to make sure that no one adds users to the super admin roles.

Groups within crowd should be able to be managed by specified users (or groups) allowing those members to add/remove users from the group.

For example, we are looking at setting up the following group structure within Crowd for each;

project-admins
project-developers
project-users

We should be able to define that members of the project-admins group can log into Crowd and add or remove users from the project-admins, project-developers and project-users group. They should only be able to manage this the groups that they have permissions for and not be able to see any of the Application, Users or Administration settings.

This way we can develop a properly de-centralised solution for our users.