4

I want to restrict users from having read access to user information lists within my entire farm. Is this even possible? If so, how can I achieve this with powershell?

  • 1
    Wouldn't this negatively affect people picker fields? Why do you want to lock down the user information list? – wjervis Jan 22 '18 at 14:52
  • @wjervis there are plenty of solutions where security over functionality is desired – Michael A Jan 23 '18 at 0:31
  • I understand that, I just don't understand what security you're gaining by locking this list down. – wjervis Jan 23 '18 at 19:09
  • 1
    @wjervis the list exposes names and structures of an organization - that's closely guarded information in a lot of applications. – Michael A Jan 23 '18 at 23:48
  • Information that's gathered from user profile services. Why not simply mark those properties that are confidential as not replicable? – wjervis Jan 24 '18 at 13:13
-1

If your User Information List (single Site Collection) contains information about organizations that you don't want everyone to see, then move that information somewhere else. For example, you could built a Personnel roster that contains everyone in your organization, and limit access to that roster. Then, remove the private information columns from the User Information List.

If this information is in Active Directory, then everyone on your network can see this information anyway, if they know where to look.

If you are using User Profile Service and updating all your site collections from Central Admin, then you can control which fields are shared with the site collections.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.