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
Hi,
I finally found a solution tu my problem.
I realised that my Active Directory groups used to secure libraries have “Limited Access” rights that was added automatically on site level (rights not visible via web interface but only with SharePoint Designer).
Following these steps resolve my problem :
- Delete these Active Directory groups with “Limited Access” rights directly at the site permission level
- In consequence, these groups will be deleted automatically from libraries permissions (even if inheritance was broken on these libraries).
- Add again permissions for Active Directory groups on each library.
After these actions, everything is OK and user doesn’t see libraries in “Tree View” or in site content.
Unfortunately, if I created new library in my site, the problem will occur again with this new library and I have to do again the same actions to correct the problem.
I Think this is a SharePoint secutity issue and it would be great if Microsoft would publish a patch or solution.
Regards
