Hi
I have a client using revo 2.1.3 and I have setup a user group and role which has restricted access to resources only in the manager but I want to restrict them further to have access to specific resource containers? For example I wish for this editor to only see the news and recipe resources and their children, hiding the rest of the site.
How do I do that?
You can create a user setting for tree_root_id with those two folder IDs separated by a comma. That should hide the other resources.
Note that they will still be able to access and edit the other resources if they can guess the URL to get to them in the Manager.
To truly protect them, you'd need to put all the resources you want to hide in a resource group and attach them to the Administrator user group with a Resource Group Access ACL entry (assuming that the users are either not in the Administrator group, or have a role with an authority level greater than the minimum role specified in the ACL entry).
Hi Bobray
Thanks for the reply. For the tree_root_id suggestion, I cant seem to add a comma and wont this apply to everyone? As the admin I would still want to see it.
I think the second option would be better. I think I have done everything I should, can you have a check?
- Role = "News and recipe editor" with authority 10 (admin is default still at 0)
- User group = "editor"
- add the editor user to the above group
- Resource group = "new and recipes" and added the parent resource container to for both to this
- Go to all resources (except news and recipes) giving access (under "access permissions") to Admin only (and not ticking the "news and recipes" resource group)
I was suggesting a tree_root_id *user* setting (on the Settings tab when you update an individual user). That will override the tree_root_id System Setting, but just for that user. It won't affect you as the admin.
Your last step above looks like it might be wrong, but maybe I'm misunderstanding you. You would put all those other resources in one resource group and then update the Administrator User group and add a Resource Group Access ACL entry for that resource group.
Actually, you could include the news and recipes pages in that resource group too, since the Editors will have access to them through their own Resource Group Access ACL entry for the other resource group (resources can belong to more than one group).
Don't forget to add yourself to the Editors user group with a role of Super User.
