It’s not you. It’s actually hard to get a grip on at first, especially if you’re not used to policy-based security systems.
What you want to do, in a nutshell, is to duplicate the standard administrator policy. Then put users in a user group and update that user group in Security -> Access Controls. Create a Context Access ACL entry for the mgr Context with the duplicate policy you created (and a role with a higher authority number than the Admin). Then edit the duplicate policy and remove any permissions you don’t want them to have.
That will limit what the users can do in the Manager.
You can also put specific resources in Resource Groups and specific elements in Categories, then do something similar to the above, but duplicate the Resource policy (for resources) and the Element policy (for elements). You then create Resource Group Access ACL entries and Element Category Access ACL entries with the two respective policies and edit the policies to remove permissions as above. That will limit what users can do with the specific objects in the resource group or element category.
You can also do a lot by just customizing the Manager. You can hide parts of the various forms using Form Customization. Hide parts of the Resource tree by setting a tree_root_id user setting. Hide parts of the File tree with a filemanager_path user setting. Hide the Element tree and File tree altogether by removing the element_tree and file_tree permissions in the duplicate admin policy. Use custom permissions to hide various Top Menu items and subitems.
There’s more information here is you haven’t seen it already:
http://bobsguides.com/revolution-permissions.html
