suite 4.x Suggestion: Allow users to become moderators of their own groups.

[ScarletCox]

We run a board where users are encouraged to form smaller project groups to achieve teamwork goals.

As it currently stands, Administrators must create user groups for each and every project, and give those groups permissions for the project's subforums.

It would be extremely beneficial to us if the smaller group designated as moderator for those subforms had the ability to add / remove users from the project team without any requirement for an Administrator to do this (or Moderators with AdminCP access).

Example: It isn't unusual for the membership of each team and project to fluctuate as the project evolves. Members which may have had the time when they joined may find themselves unable to meet the commitments three months later, and new members are sought to replace those who step away. It would be time-effective if the project leaders didn't need to wait for an available staff member to remove non-participating members or to add ready and eager new ones to the roster.

[Joel R]

Check out Group Collaboration in the Marketplace by @Kevin Carwile

[ScarletCox]

[prupdated]

On 9/30/2015, 3:56:45, ScarletCox said:

We run a board where users are encouraged to form smaller project groups to achieve teamwork goals.

As it currently stands, Administrators must create user groups for each and every project, and give those groups permissions for the project's subforums.

It would be extremely beneficial to us if the smaller group designated as moderator for those subforms had the ability to add / remove users from the project team without any requirement for an Administrator to do this (or Moderators with AdminCP access).

Example: It isn't unusual for the membership of each team and project to fluctuate as the project evolves. Members which may have had the time when they joined may find themselves unable to meet the commitments three months later, and new members are sought to replace those who step away. It would be time-effective if the project leaders didn't need to wait for an available staff member to remove non-participating members or to add ready and eager new ones to the roster.

The only way I found around it was to write a relatively simple front end script to manage people's secondary groups through SQL. It's just an array field in the member table. Then everything else runs natively without other programs and hooks using resources.

I don't think this would be viewed favorably on the cloud though. It's probably an idea for stand alone server eyes only. It does has the advantage of having everything else running natively without substantial performance hits though.