Simplifying the control panel for content editors

You can now hide virtually any part of the control panel for users with the Content Editor role.

To do so, you must create a Global Setting named admin.custom.control_panel.navigation. In this setting, you put a JSON string that defines what is visible and what is hidden.

Here is an example of the JSON string:

    "content editor": {
        "editors": {
        "panels": {
            "structure": ["templates","css files","js files","xml for rss and atom feeds","smartthemes",{"pages":["add new page"]}],
            "dashboard":["site statistics"],
            "settings":["activation",{"site settings":["configure external apis"]},"private label"],
            "database":[{"advanced database setup":["create custom item types","manage custom item types","import database items"]},"link types"]
        "menus": {
            "structure":["templates","css files","js files","feeds & xml files","smartthemes"],
            "settings":["global settings","my sites","create new site","private label config"],
            "database":["item types","link types","import"],
            "analytics": false

We will be providing documentation on how to create this JSON string soon, and in time we will have a graphical interface to control the settings to make this much easier to use. In the meantime, please contact us if you need this feature, and we will help you set it up.

Some limitations to note:

  • All people with the Content Editor role have the same restrictions.
  • This hides control panel elements, but it does not prevent them from being accessed should a content editor know the URL to get to a hidden control panel element.
  • We do not currently have a mechanism to enable different content editors to access only certain pieces of content (such as selected pages).

If there are other capabilities you'd like to see, please let us know.

Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk