I am running installs of both systems on my server and have a few questions about the basic permissions in Revo. It seemed to get much more complex. I am stumped!
In Evo I set up a manager in addition to the admin user that just had access to the basic CMS editing ability and nothing more. No extra settings permissions or anything. I cannot for the life of me figure out how to get a user to just see the site tree and be able to edit pages with as little else as possible in Revo. Any help?
They’re definitely more complex, but also more flexible in Revo.
The element and file tree are hideable in the current RC1 version by removing the file_tree and element_tree permissions.
All the top menu items and subitems are hideable by giving them an additional custom permission in System | Actions (again, you need the current version for this) and then giving that permission to everyone else. Permissions there can be a comma-separated list and everything on the list will be required to see the menu item. You can use the same permission for all of them.
IOW, add a permission called show_menu to all the actions (menu choices) you want to hide (if there’s already a permission there, add yours after a comma).
Then duplicate the "administrator" policy, add that show_menu permission, and assign that duplicated policy in the Context Access control entry in the administrators user group (Security | Access Controls | User Groups -- right-click on the administrator user group and update it. Then go to the Context Access tab and right click on the mgr entry and change the policy to your new duped admin policy.
Hope this makes sense.
Thanks for this info. It is a lot to swallow and learn, but at least it gets me going in the right direction. I appreciate all the hard work and the quick responses. You have another loyal MODx CMS follower. I look forward to helping out in the future.
Also when you say the most recent version do you mean the bleeding edge release version of Revo?
MODX Staff
