It should be possible in the application to group users.

Grouping of users makes only sense for

• task PMs,
• and for parent users in the user hierarchy.
• in the future for owning projects

It does not make sense to

• inherit ACL rules (this has to be done on ACL rule level)
• associate groups to tasks - therefore multiple users can be added to tasks

Additional restrictions:

• Groups are only usable for users which are PM and/or admin, in any case not for normal editor users.
• if removing the above roles, the user must also removed from its groups.
• this must be communicated to the user

Additional notes:

• If a user belongs to multiple groups, and adds a new user, then by default the first group is the new parent of the new user.This preselection can be changed manually afterwards by the user.

Background of this need

1. task PMs

Assume that the application is configured, so that PMs can only the see the tasks in which they are set as PM. Further currently only one PM can be defined for a task. If that user is in vacation or ill, no other PM with the same access levels has access to that task.

2. user hierarchy

For the user hierarchy theres a similar problem as for the tasks. Since a user can only have one parent, and if this parent is not available no other user from the same level can access the child users.

Possible solution

Introduce Groups which can be used similar as a user. Then a Group can be used in user hierarchy and and in the task instead one single PM.

Keep in mind:

• multi-tenancy
• evaluate best-practices to that topic