This topic is a follow up on the brainstorm session held at DNN-Connect 2023. For more info, check this blog post. This thread can be used for discussions and contacting the lead for the topic, and to keep the community posted on achievements.
The group of post-its where Peter Donker volunteered to lead for, had these texts:
I think it might be easier/simpler than that. With built-in roles, they all have permissions that are not at all defined in the permission grids. Those grids are primarily meant to offer the ability to distribute some of these permissions to modules and pages that others would ordinarily not have access to them.
In this case, I think a content editor would function more like an Administrator-lite... Meaning, it could edit all content on all pages and modules, but not perform any administrative actions. So, I think that all edit views would be available, but none of the things that would otherwise be something that an administrator should be doing.
Admins should rarely be actually editing content, when there's a content editor role. This also will further secure the website in many cases, because some people just add people to the Adminstrators role today, because manually creating a Content Editor role is extremely time-consuming to setup and maintain. You're constantly having to work on it.
Just my $0.02. :)
These Forums are dedicated to the discussion of DNN Platform.
For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:
Awesome! Simply post in the forums using the link below and we'll get you started.