Yeah, it is not that big of a deal for sure.

In our case we are primarily going to be using AD and this will be the solution for us. I got AD security groups syncing with the roles last night and we will be using those to distribute security policies and customized content as we already have pre-established groups setup for things like staff vs. faculty vs. students.

Mike,
if there is demand by a valid number of users, I would suggest hierarchical roles for a new permission system in DNN neXt. of course, this would replace role groups, which were introduces as a weak substitute, mainly for the use on this website years ago. (replacement shouldn't be too difficult, just add the groups to role tables as replace roleGroupID with appropriate parentRoleID). A role needs a "inherit parent permissions" flag and all permissions tables should store calculated permissions upon save. To improve performance, I would not store each permission individual as current but one record per object (module, page, folder, ...), holding objectID, roleid/userid, grantedPermissions, deniedPermissions, grantedPermCalc and deniedPermCalc, where each permission value is an integer, interpreted as bit set, making it easy to calculate (allowing for 32 permissions per object type, of which I would reserve 8 bits for common use, first bit always for "full permission") 

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN