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
This is because of the feature called “ViewFormPagesLockDown” activated. if you deactivate this feature they will not see view all site content and if they click on any other library it throws “you don’t have permission” error. This is the hidden feature so you need to either run stsadm or powershell.
Hi,
i am having the same problem as you describe, only difference being that the platform is on office 365.
there is one site with difference libraries. i created one new library and that is the one having the issues. all users are able to see the library which should not be happening. the content is not visible to all users.
hope somebody nows what is causing this.
Not sure if audience targetting would fill the gap until we get to the bottom of the issue? I know it is far from ideal, but it seems that security is working when we get to the actual libraries, they are just not being security trimmed from our view.
I also do not trust the DC in my test environment, so I am going to build the environment again and see what happens.
I am also going to apply the latest updates and see if that makes any difference?
I will let you know if I get any further.
Henry,
The issue is still happening in the SP2013 environment mentioned. Thanks for testing the scenario yourself. Much appreciated.
Okay.Â
Thanks but don’t hold your breath. They will likely still show.
