Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Security User Roles - Groups - Permissions!?!Security User Roles - Groups - Permissions!?!
Previous
 
Next
New Post
7/31/2008 8:35 AM
 

Hi everyone,

I've been looking and searching how to extend the security roles and permissions on DNN 4.8.4. In fact what I want to achieve is somewhat common to other CMSs. First, I would like to be able to add permissions under the security roles. For example to view, edit, configure, administrare modules. Basically add more permission types in the core security module of DNN. An example to this would be i.e. on a page where an editor can log in, to be able to change only content within modules, and not add/remove modules or even use the design mode. (this includes what modules specific users see at the control panel, however there is a very good module out there for this issue).

With this, the second issue I would like to look at is as above. Specify user roles and group and modify their permission for different mode settings (view, edit, design). This I have no clue how to do...any ideas?

Last, and most important, I want to add permission to specific type of content editors, allow them to change content but request approval by an administrator before the changes go "live" (basically, visible to the public). Maybe this can be a feature on DNN 5.0 but who knows...

I have looked at some modules out htere availble but can't seem to identify everyhting that I need. Maybe any one of you know something better that exists or a way to extend the security roles.

Many thanks

¬k²

 
New Post
7/31/2008 11:42 AM
 

[quote]An example to this would be i.e. on a page where an editor can log in, to be able to change only content within modules, and not add/remove modules or even use the design mode[quote]This sounds like you want to use the Module Edit settings. If you go to the module settings and give a role Edit access it, generally, will have more access to control the module. What that will be totally depends on the module itself.

[quote]this includes what modules specific users see at the control panel[/quote]I think this is getting put into 5. Not sure where along the 5 path, but I think I remember it being something they wanted to get in.

[quote]Last, and most important, I want to add permission to specific type of content editors, allow them to change content but request approval by an administrator before the changes go "live" (basically, visible to the public). Maybe this can be a feature on DNN 5.0 but who knows...[/quote]From my understanding (could be wrong, but) this type of feature isn't going to be in the core of DNN.
This feature is a CMS feature which will require CMS module to make that control available (There are modules that do it, don't know any off top o'head). DotNetNuke is being built as a framework to allow anytype of development to be done on top of it. Removing (or not adding) features which are specific to a type of website will allow the core team to work on enhancing the framework that allows developers to build better modules to use dotnetnuke as any type of website.  (Just to say again - not on core team - no insider information what so ever, this is just the impression I have about things like this)

[quote]Maybe any one of you know something better that exists or a way to extend the security roles.[/quote]The only way I can think of to extend the security roles is to build it into the module settings. So to do this you would need to custom build or have access to source. You can make a permissions grid specific to your module and store the roles and their permissions, which you can then load and use in the module to determine how things go. I've noticed a couple modules that extend the permissions grid in the Module Settings section. Haven't quite figured out how they do that yet...


That's all I got for ya right now. Hopefully it helps shed some light on things. :)

 
New Post
7/31/2008 1:40 PM
 

if true..   why is the focus now on 'community' modules..  that's why 5.x is being done..   that goes against your only a framework comment

what is true.. is DotNetNuke will have the features that 'customers' are paying for ...     workflow, editing history, etc..   is part of every content system... except..

 
New Post
7/31/2008 3:37 PM
 

You can create custom permissions for your modules.

Vicenc expalins the process here:

Custom Module Permissions. Enhance your modules!


DotNetNuke Modules from Snapsis.com
 
New Post
7/31/2008 3:49 PM
 

Ahhh, swank - been looking for that. :)

EDIT - After looking at it a little more - I was REALLY close to that with the Deny ability I posted about a  while ago, hehe. Just didn't know about the moduleDefID association. It was my first major adventure into the DNN core, so I don't blame myself too much. hehe

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Security User Roles - Groups - Permissions!?!Security User Roles - Groups - Permissions!?!


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out