If ‘Everyone’ has no access by default then is there any point in setting up a child principal with ‘No Access’ rights. Wouldn’t every principal that is a child of ‘Everyone’ have no access by default? Thanks.
frank35 
(BOB member since 2005-08-25)
The other group set on that on the object where everyone has “No Access” will overwrite it.
For eg: Folder X --> Everyone --> No Access (Inherited)
Group 1 --> View
Net result on Folder X is Group 1 will have View access and all others no access.
thanks
Sree Konduri (BOB member since 2005-07-14)
Hi. Thanks. However what we have is as follows:
For eg: Folder X --> Everyone --> No Access (Inherited)
Group 1 --> View
Group 2 --> No Access
Group 3 --> No Access
…
My argument is that Group 2 and 3 don’t need to have No Access specifically assigned as they won’t have access anyway. Do you agree?
One other thing, how do you change access permissions on the root folder?
frank35 (BOB member since 2005-08-25)
You are correct – adding Group 2 and 3 in your example is unnecessary.
The only reason for doing this would be to break security inherited from another folder. Consider:
Top Level: Everyone:No Access
FolderA: Group 1:View, Group 2:View, Group 3:View
FolderB: Group 1:(inherited), Group 2:No Access, Group 3:No Access
FolderC: (inherited)
FolderD: (inherited)
In this example, we want Groups 2 & 3 to see FolderA and its children FolderC and FolderD, but we do not want Groups 2 & 3 to see FolderB. So in FolderB we break inheritance by setting Group 2 & 3 to “No Access” and unchecking the two “Inherit” settings. If we didn’t break inheritance, then all three groups would see all folders under FolderA.
To change top-level security, go to Manage -> Top-Level Security -> All Folders.
joepeters 
(BOB member since 2002-08-29)