Yes, we've seen this. We have had to add the "Content Manager" or "Content Editor" to all users, so that roles that worked before still work. I;m not aware of having to add it to each page?

It's not a big issue for us, but I agree it's wrong. Roles should carry on working on upgrade.

I do not know the reason for this. If you have a lot of users, one way around it is to add the roles to each user via the database. (not the best way)

Just to make sure I understand the concern here.

Content Editors & Content Managers = Yes, these roles ALWAYS exist, and they ALWAYS have permissions on the pages. That is/was the intended behavior of that addition.

At this time there it not a way to remove those two roles from the system roles behavior. Does that address your concern, or are you talking about a conflict after upgrade with an older role of the same name?

I do not recall seeing Content Editors & Content Managers roles until DNN 10, but I never build that side of our systems. But even if they did exist we did not need to use them. Now you MUST use these roles or you cannot edit the modules on the page that were editable before without those role.

The may have existed in Evoq, but I do not think they existed in DNN platform, otherwise we would not always created a standard set of roles for our clients.

Posted By Mitchel Sellers on 2/13/2026 12:16 AM
Just to make sure I understand the concern here.

Content Editors & Content Managers = Yes, these roles ALWAYS exist, and they ALWAYS have permissions on the pages. That is/was the intended behavior of that addition.

At this time there it not a way to remove those two roles from the system roles behavior. Does that address your concern, or are you talking about a conflict after upgrade with an older role of the same name?

There is an issue local to us in that we created a "Content Editor" role that we use sparsely to allow others in our corporation to edit some pages... but not all of them. We keep editing of pages limited within our corporation, for a variety of reasons. Now there is a bit of a potential security trap here, as we have a similarly named role that allows (for us) inadvertent elevation of privileges. 

In fact, an audit revealed a couple of users placed in both Content Editors and Content Managers that didn't make sense for those users to be there(!) No one on my team recalls moving those users to those roles. So a couple more roles we have to audit on a regular basis.

This sounds like something we're just going to have to live with. It's too late now I guess but would prefer an "off switch" of some sort that blocked the assignment of editing rights on every page. And/or the ability to remove the editing rights for these roles on the pages, even if it could be done via SQL.

 

 

There really should be a way for a Site Administrator to remove "Content Editor" and "Content Manager" access from editing a specific page or module if needed.   Example: We use a customized Login Module that only a Site Admin should be able to administer.  

I logged the issue on https://github.com/dnnsof...Platform/issues/7185

Cheers
Tycho