Re: DNN 5.0: Breakout of core admin modules

Could you clarify something about module permissions? In DNN 4.x and prior it seems that DNN treats the Administrator role differently from roles that have edit permission on the module. So, even if you grant a role edit permission on a module, that role will never have access to the module settings page, or Delete and Move, only Administrators see that.

Is that distinction still present in DNN 5.x? It is actually a useful distinction, because as the administrator, you might want to make a module fully editable by a particular role but not allow it to be deleted, moved or basic settings changed.

Re: DNN 5.0: Breakout of core admin modules

This tops my list of tasty enhancements, but are you certain about the second example? It implies that having module edit permissions allows a user to access the module settings page, which normally requires page edit permissions to view. Module edit permissions normally only exposes specific management options that have been specifically enabled by the developer... e.g. items on the action menu and action buttons.
The description in the post suggests there is no permissions granularity provided for the former admin modules... "edit permissions = administration permissions". I would be very surprised if this were actually the case.. because if module editors=admins, then the whole point of breaking these modules out would be moot.

Re: DNN 5.0: Breakout of core admin modules

I am drooling over DNN 5.0 just for this piece. We have around 30 people that need rights to add / create tabs, but no other rights from the admin menu. I have had to go in and add work arounds to solve for this, will be really nice to get rid of those work arounds though. It will also be a blessing for me as a host service, cause I can offer my clients more control over the host control panel for things like SQL input box, etc but won't have to give up full host control over to them, for things like Host settings, where I have restrictions on modules etc.

Re: DNN 5.0: Breakout of core admin modules

I think this is obvious. Is there somewhere more info about DNN5 to read?
Thanks
Vlado

Re: DNN 5.0: Breakout of core admin modules

Great feature, thank you.

Re: DNN 5.0: Breakout of core admin modules

2nd question, and maybe a bit off topic. This is regarding allowing the Users and Roles modules to be used by non-Administrators.

Allowing non-Administrators to manage users & roles is for me the biggest payoff in DNN 5.0. However if there are no restrictions in what can be done, it could be "dangerous". For example, I would not want a non-administrator to be able to promote themselves or anyone else to administrator. I might also want to restrict the administration of certain roles to certain users.

So, are there any restrictions an administrator can implement? My ideal would be a rule of the form:

Role X is allowed to administer roles {A,B,C...}, which means (i) edit users who are in these roles, (i) add users to these roles & (iii) remove users from these roles, but only if those users are NOT already members of roles {P,Q,R....}

The reason for the exception is, for example, to prevent the editing of users who are Administrators (but who are also in one of the roles {A,B,C...} that role X is allowed to administer).

Re: DNN 5.0: Breakout of core admin modules

I agree this will be very useful, especially as it is refined and enhanced. Allowing delegated user management was something important to me when I first started using DNN 4. Fortunately, I found WorkControl User Manager, which allows very good granular permissions on exactly what a delegated user is allowed to do, including preventing the editing of Admin accounts.

Re: DNN 5.0: Breakout of core admin modules

Cool, thanks for checking this and updating the post. You had me worried there for a bit.

Re: DNN 5.0: Breakout of core admin modules

As smehaffie suggested I have written my proposal up as an enhancement request in Gemini. The ticket is DNNP-8123 (http://support.dotnetnuke.com/Default.aspx?p=23&i=8123).

Re: DNN 5.0: Breakout of core admin modules

Footnote:
I understand that the scope of DNN 5.0 is now frozen. However my feeling is that this feature is going to cause a lot of upset in the community. People will rush to use the feature and will assume that it is "safe". They will then discover that, for example, it is possible for users to elevate themselves or others to administrators. I think this will cause a lot of bad press for DNN, and be regarded as a security loophole.

Re: DNN 5.0: Breakout of core admin modules

Thanks, I corrected and clarified the Gemini ticket.

I do get your point that administrators ought to understand, and be fully responsible for, the consequences of giving away permission to the users & roles modules. The trouble is, what ought to happen and what will predictably happen are 2 very different things!

Briefly, my point is that I think you are going to get 3 outcomes from releasing this feature as described: (i) people who use it taking responsibility for its limitations , (ii) people who are disappointed that they can't use it the way they thought they could (i.e. to delegate work with no risk), and (iii) people who are really upset because they assumed it was "safe" and then an "incident" occurred.

I am a huge advocate of DNN. The reason I am speaking up about this not just that I want DNN to have great features, but I think outcome iii above will hurt DNN's reputation.