Hello.
I am trying to find a fix for a weird document library permissions and “visibility” issue in SharePoint 2013.
In two examples so far, the client has sites with the usual Owners, Contributing members and Visitors groups. All intended users are members of the appropriate groups. Permissions on document libraries have been separated from the parent, configured so that only specific users can view or modify. Running the “Check permissions” tool on user xyz library produces and confirms “Access for user abc: None”.
Oddly, if users click on “all site content”, they are able to see all document libraries listed. They can see names, tiles for other libraries, total number of items and modified date indicated beside each library tile. This is not good. The client does not want users to see a list of other users’ libraries.
If a user clicks on a document library for another user, the library page displays but items are not visible. That’s a small consolation but still not acceptable.
How do we make it so users do not see other users’ libraries listed in all site content?
Thanks in advance,
Theresa
So this is where I am at so far:
Created a site collection called Team and the top level site is using the out of the box team site template.
Created the three default SharePoint groups of Visitors, Members and Owners.
Added Test, Test1, Test2 to the Visitors group.
Created a library called Test, test1 and test2
Broke the inhertiance on the three libraries and added in only the corresponding users with full control.
Logging on witht he accounts shows the following:
Test – can see Test, Test1 and Test2 libraries.
Test1 – can see Test1 and Test2 libraries.
Test2 – can see only Test2 which is what I would expect.
Created another user called Test4 and a matching library, that was configured the same way as the previous libraries. Don’t ask me why I did test4 and not test3 as I don’t know :).
Test – can see Test, Test1, Test2 and Test4
Test1 – can see Test1, Test2 and Test4
Test2 – can see Test2 and Test4
Test4 – can see just Test4
So we at least have a pattern emerging here but not one that immediately makes any sense and is not a pattern that we want to see.
Patched the environment upto Oct 2013 CU and no difference.
I now cannot help think that something may be going on with the Distributed Cache Service so this is my next area of investigation.
