We have an issue with the numbers of User Roles needed for every tiny permission needed for different users.
Many other software we use [Such as FME] have the ability to assign a user to multiple roles and their permissions become an amalgamation of those roles.
The ability to assign a user multiple roles would allow us to add only the permissions needed for those specific roles.
Example Scenario:
If you need to add the "Version Management" permission to users that are going to be doing QA\QC, and the users already have a mix of roles [some users and some publishers], you would have to add a minimum of 2 new roles in the Enterprise.
If you could create a "QA/QC" User Role that only adds the "Version Management" permission and apply it in addition to the "Publisher" or "User" roles as needed, you would only have 1 new User role to manage.
In Enterprise, User Role field would look something like "Publisher, QAQC"
@DerekWaggenspack thanks for sharing this request, how would you foresee potential permission conflicts being handled between the groups? Editing, viewing, etc..
Since Groups also can't be assigned Roles [another enhancement that I read about], conflicts between Roles are already not being handled between the groups. If someone's type and Role has editing, they have editing across the board, even if a particular item should be view only. That is only shared to a group for reference purposes.
My stance would be that it would have the amalgamation of whatever the highest permissions would be.
Isn't that how other industries handle it?
Having group based Roles would supercede a lot of this though since you could create the roleset for the group.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.