Backend manager with multiple editors (not a root level)

Hello,

i have a website with a sitemap like the image here below. Every color (except BLUE) is a different editor. A user in his own usergroup with rights to edit and add pages through the Backend manager.
To lock them in their own section of the website i made a resource group for each usergroup. The BLUE pages belong to the main BLUE editor/admin. By putting these pages in his section all the other colors cant see or access these pages.
But the problem is that if the login the wont see anything in the tree. All root resources belong to the BLUE admin.

How can Editor RED reach his pages in the tree?
I followed the great tutorials from Bob here: http://bobsguides.com/revolution-permissions.html the section after scrolling half down, about "Limiting Manager Users to a Subset of Resources using User and Resource Groups"
If the main pages of the RED editor was on the root level this would work....

You need to put the Region A page in the Resource Group that Mr. Bar's User Group has access to. Similarly, put the Region B page in the Group that Mr. Boss' group has access to.

If you need finer control, you can create two new groups, one for the Region A page and one for the Region B page and give the users access to those pages with just the "Load, List, and View" policy.

Thank you Bob i used the second option. Last days iam turning into a Backend protection specialist...

I also needed to make a resource Group "Our Sales People" and also put Mr. Foo, Mr Bar, Mr Boss and Miss Carry in this Resource group. (or put the "Our sales people" page in their own resource group of the Editors)
As far as i can see to reach their own pages they must be in the Resource groups of all parent pages up the tree. But as said this is solved now. By making sure that if a new editor joins (Mr. New in region B) he is in the resource groups "Our Sales People" and "region B".


An other thing came up.
The main editor is at this moment a user with lots of rights. I dont want him to be a sudo user. Because then the main editor can start changing Elements, website settings, media sources, package etc....
He is member of the "Can see AllDocumennts" resource Group and can edit them all. But blocked from Elements and the other mentioned menu parts.

Case.
Ill add all pages to the Main editor his resource group. The "Can see AllDocumennts" resource Group
Mr. Bar makes a new page. This pages goes into his own resource group. So he can see and edit it.
This new page does not go in the "Can see AllDocumennts" resource Group until i put it there.
The main editor will be abandoned from all new pages editors like MR. Bar make.

Is there an other solution than to give this main editor Full acces with sudo user. (or block him from elements and menu items while being a sudo user...)

(I am above this main editor at the normal admin role)

I allready figured it out. Just put the main editor in their user group. Was that easy [ed. note: voklee last edited this post 11 years, 10 months ago.]

Yes, my policy is to always put myself (or the main editor) in any User Group I create as soon as I create it.