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
I think this has been suggested earlier on in the disucussion and it certainly did nothing for me other than remove the site contents link. Might work for others though.
This is because of the viewformpageslockdown features activated. Deactivate and you will see the change. This Feature is Sitecollection level feature. it is a hidden feature.you need to run PS or stsadm from the server for that sitecollection.
Unfortunately still no miracle cure in sight that is for sure. However I will try and find some time to take another look and see if I can come up with a consistent workaround if nothing else.
Has there been any updates on this? Â We are also experiencing this issue. I have found that if I create a new subsite within the site collection permissions are fine and work as they should at least for awhile and then something changes and users can see libraries that they don’t have access to. Â The content doesn’t display but if they don’t have permission to it they shouldn’t see it. Its a frustrating problem that is for sure.
Henry, this sounds like the work-around my colleague had tried but with inconsistent results.Â
Appreciating your persistence on this topic!
