Hi All,

I am having great difficulty trying to set various levels of permissions.

The Document Library is made up of 6 levels.

All Users can see the very top Tier.

Inside each folder there are several sub folders which only 1 specific role per folder can see. They have been set to (View, Add, Approve)- 7 folders, 7 Different roles.

Within each of these folders users should not be able to set any permissions but only add new Folders, Files. Once they have added their new file it is not approved and the 'Edit Attributes' appears. When checking the new folders permissions with the admin account it has set (View, Edit, Add, Approve) as opposed to the 3 I had asked it to.

Would anyone be able to shed any light, my brain has been frazzled by the number of folders, and permissions they are after.

In essence any user in the role should only ever be able to view and add folders, they should never be able to edit any attribute regardless if they created that folder.

Many Thanks,
Dom

I found a solution in another post about 7 pages down that relate. My understanding is that it assume the edit function as you want to 'edit' that particular folder as you have responsibility over it. It limits what you can do so that is fine.

Is this just on a user basis, so another user who didnt create that folder but has all the same permissions will they be able to 'edit attributes'

One last question, whilst using the Host account and applying Permissions to children, when I check back it has always been unticked?

Permissions are role *and/or* user based. Normally you'd just specify roles, so all users belonging to that role get that permission. Note that specifying an "approval" permission means that all content needs to be approved (by someone with that permission) before it's displayed. So don't use it unless you want this to happen.

"Unify on children" is a one-off operation. So it unchecks and lets you recheck in case you want to unify again.