Hi all,
We are building our first client website with Revo 2.0.8-pl and cannot get our heads around creating manager users. We want to create a manager user for the client, who needs to see all resources, but hide most of the top-level menus and the elements tab.
We have been following the instructions below, kindly written on Bob’s Guides:
http://bobsguides.com/revolution-permissions.html
But when we login as the user we created, we cannot see any resources at all. We have followed the instructions below to the letter, so not sure why it isn’t working:
Limited Manager Users Who Can See All Documents
Sometimes, you want users who can see all the resources in the tree, but have limited rights in the Manager. To limit the users’ actions in the Manager, you don’t need any resource groups. You just need to assign them a policy in the mgr context that has fewer permissions.
Here are the steps for an example where you want a group of Editors who are not super users:
1. Go to Security->Access Controls->Roles tab.
2. Create a role called Editor with an authority level of 5.
3. If you have the current development version (2.0.5 or higher):
Click on the Policy Templates tab.
Duplicate the AdministratorTemplate Policy Template; call it AdminEditorTemplate.
Create a new policy called AdminEditor based on that template.
4. If you don’t:
Click on the Access Policies tab.
Duplicate the Administrator Policy; Call the new policy AdminEditor.
5. Click on the User Groups tab; right-click on the Administrator user group and select Update User Group.
6. Click on the Context Access tab.
7. Click on Add Context. You’re creating a Context Access ACL entry; use the following settings:
Context: mgr
Minimum Role: Editor
Access Policy: AdminEditor
Save
8. Click on the Users tab
9. Add the user(s) to the Administrator user group with a role of Editor.
10. Click on the Access Policies tab.
11. Right-click on the AdminEditor policy and select Update Policy.
12. If you have the current dev. version, there will be checkboxes next to each permission; just uncheck the ones you don’t want them to have.
13. If you don’t, you need to right-click on the permissions and select "remove permission" -- you might want to make a list of the ones you removed in case you decide to add them back.
If you need to give different permissions to different users, create a new role with a different authority number and a new policy for each group of users that will share a set of permissions and add them to the Administrator group with those roles and repeat the steps above to create a Context Access ACL entry for each group with the appropriate policy.
Further Tips:
Remember that users will inherit the permissions of policies in the Context Access list with minimum roles that have a higher number than they have in the group.
Don’t forget to clear the site cache, flush all permissions, (and sometimes) flush all sessions before testing any changes.
Note that removing the file_tree and element_tree permissions will hide those trees completely.
You can hide specific TVs and Manager form fields using File Customization ruled.
You can also hide specific menu choices in the Top Menu using custom permissions, but that’s another tutorial.
