Explain user auto-assignment to groups [5.2.2-B1]

The permission model in In-Portal looks like this:

1. there are group (entered in "User Management > Groups" section)
2. each group has associated set of actions, that user is allowed to perform (permissions)
3. user can be assigned to several groups
4. allowed actions from all user groups are combined to get final set of allowed actions

One of the groups, that user is assigned to can also be marked as primary. There several things about primary groups that are important:

• user can't be removed from primary group
• this group is shown in user list in Admin Console
• the primary group for each user can be changed, when editing that user in Admin Console (see below)

When user is created, the he/she is automatically assigned to a primary group based on user type ("Member" or "admin"). With that assignment user is granted common set of allowed actions for that user type, including ability to login to the Front-End or Admin Console respectively.

Fact, that user can be removed from his/her primary group can lead to inability of that user to login at all without Administrator even understanding what he/she is done. To prevent that in the  INP-833 - Getting issue details... STATUS  task a code was added, that upon login virtually adds user back to a group based on the user type. This is good, but doesn't work well in cases, when a need araises to create administrator account with limited permissions.

Solution

1. on the group management screen shown, when adding/editing user show following banner in red (as error): The "Member" group will be added automatically, if missing. (the "Member" would match actual group name for new website registrations)
2. on the group management screen shown, when adding/editing administrator show following banner in red (as error): The "admin" group will be added automatically, if missing. (the "admin" would match actual group name for administrators)

Related Tasks