SonicWave

Good day,

Below are the steps to reproduce the problem

  1. Create 3 custom access group in the site ("Group1", "Group2", "Group3")
  2. Created a document library ("Doc").
  3. Created a folder ("F1") in "Doc"
  4. Remove default permissions and added permissions "Group1", "Group2", "Group3" to "F1"
  5. Created a subfolder ("F11") in "F1" with inherited permission "Group1", "Group2", "Group3"
  6. Removed the inherited permission in subfolder "F11" and remove "Group1", leaving "Group2", "Group3"
  7. Back to folder "F1", removed permission "Group1" and "Group2", leaving "Group3"
  8. Back to subfolder "F11", verified permission. "Group2" was removed and "Group3" remained
  9. At folder "F1", added permission "Group1", become "Group1", "Group3"
  10. Back to subfolder "F11", verified the permission. "Group3" remained and unaffected

Although the permission inheritance was broken at Step 6, somehow the permission removal on folder "F1" still affects subfolder "F11". However, If a new permission is added on folder "F1", it didn't reflect back to subfolder "F11". I tried with 2nd level subfolder "F111" and it seems like some inconsistency in between too.

It's MOSS 2007 Enterprise Ed. with the latest updates installed on the WIndows SharePoint Services 3.0 through Windows Update.

Is it some misconfiguration that missed out or is it an issue Been tried to search for solution in Internet. But seems like no posts that mention this issue.

Thanks a lot.

SonicWave



Re: SharePoint - Design and Customization Folder Permission Inheritance Problem - Inconsistent unique permission

SonicWave

Didn't receive any reply on the question and get any info from internet, so I start to relook into the concepts of the permission inheritance and fine-grained permission. I think I have came to a rough idea on explaining the behavior of the fine-grained permission.

  1. Create 3 custom access group in the site ("Group1", "Group2", "Group3")
  2. Created a document library ("Doc").
  3. Created a folder ("F1") in "Doc"
  4. Remove default permissions and added permissions "Group1", "Group2", "Group3" to "F1"
  5. Created a subfolder ("F11") in "F1" with inherited permission "Group1", "Group2", "Group3"

DocumentLibrary -------------------> Folder1 --------------------------> Subfolder1

(Group1, 2, 3) (Group1, 2, 3) (Group1, 2, 3)

6. Removed the inherited permission in subfolder "F11" and remove "Group1", leaving "Group2", "Group3"

DocumentLibrary -------------------> Folder1 --------------------------> Subfolder1

(Group1, 2, 3) (Group1, 2, 3) (Group 2, 3)

7. Back to folder "F1", removed permission "Group1" and "Group2", leaving "Group3"

DocumentLibrary -------------------> Folder1 --------------------------> Subfolder1

(Group1, 2, 3) (Group3) (Group 2, 3)

8. Back to subfolder "F11", verified permission. "Group2" was removed and "Group3" remained

DocumentLibrary -------------------> Folder1 --------------------------> Subfolder1

(Group1, 2, 3) (Group3) (Group3)

"Group2" in "Subfolder1" was removed as well despite of the unique-permission set. This is logical as "Group2" who cannot access "Folder1" shouldnt be abble to access "Subfolder1" naturally.

9. At folder "F1", added permission "Group1", become "Group1", "Group3"

DocumentLibrary -------------------> Folder1 --------------------------> Subfolder1

(Group1, 2, 3) (Group1, 3) (Group3)

10. Back to subfolder "F11", verified the permission. "Group3" remained and unaffected

DocumentLibrary -------------------> Folder1 --------------------------> Subfolder1

(Group1, 2, 3) (Group1, 3) (Group3)

"Subfolder1" unique-permission was intact. This is logical as "Group1" who can access "Folder1" doesn't neccesary able to access "Subfolder1".

Moral behind the story When no one else except you yourself has the problem, most probably it's a typical "user-problem" and try to look at it from different perspective.

Please correct me if my explaination above is wrong. Thanks a lot.

SonicWave