This should probably help you if you know how to write code for it: https://docs.dnncommunity...nt-system/index.html

Agreed with the guidance given by Timo.  

However, if you're concerned about the content updates coming from anyone, I'd be concerned about giving them a login to begin with.  I hope you have a training program of some kind.  🫣 

To help with this scenario, we have a cool feature in the Upendo DNN Promp suite of commands that implements & enforces a slightly lower content editing level across a DNN site.  This may not be a direct comparison to your use case, but it could be another way to programmatically respond to the need you've posted about.  

Thanks Timo and Will. Will try yo use the method suggested.

Regards,

Alok

However I have a query I can class in DNN code at following path:

DNN Platform/Library/Entities/EventManager.cs

Is it possible that I extend the class in our application and override for events for which we need changes. And add this implementation in configuration to use it as  dependency injection for IEventManager interface. I am assuming that EventManager.cs is the concrete implementation for all DNN events. 

Please advise.

Regards,

Alok

Without confirming what events you might use for this (assuming the right ones exist), you could do it this way.  But, I could see this being a very messy way to do it - from a UX perspective.  🤔 

You're better off implementing a lower level set of permissions, which will enforce fewer abilities for your content editing team in general.  It could also allow you to assign a different toolbar in the HTML editor.  This would be far easier for you to enfore and maintain, without annoying/confusing your end users. 

That, and having a short PowerPoint slide deck to tell them what they should be doing and how you expect them to do it, with screenshots.  

This has always been all that's been necessary for me.  🤷🏽‍♂️