4

Is it possible to 'hide' a page to everyone but a certain user or group of users?

Improve this question

3 Answers 3

Reset to default
4

Yes, you'd go into the library that contains the page and set item level permissions for the page assuming you have the permissions to do so. Or you could create it in a separate library with unique permissions.

Improve this answer
4
  • I created a library but for some reason, I can't edit the permissions; which doesn't make sense since I'm a farm administrator.
    – Iunknown
    May 5, 2011 at 20:08
  • Just being a Farm Admin does not grant you full admin permissions to the site collections. You need specific permissions on the site collection as well.
    – Dave Wise
    May 5, 2011 at 20:14
  • I'm an administrator of the site collection and if I look at the site permissions, I says I have full control.
    – Iunknown
    May 5, 2011 at 20:40
  • Does the Full Control privledge defined for your site collection allow you to Manage Permissions. Perhaps a policy has altered that? I don't have a 2010 install to look at to walk you through the GUI to break permissions on the librrary and create new ones. 2007 it was Settings, Library Settings, Advanced Permissions. Then Actionn, Edit User Permissions, click OK then edit/remove users.
    – Eric Alexander
    May 5, 2011 at 20:51
2

You can make use of the Audiences feature that allows you to restrict visibility of the page via several different mechanisms, including Groups, distribution lists or other rules based on profile data.

Improve this answer
5
  • Audiencing isn't security though.
    – Eric Alexander
    May 5, 2011 at 20:06
  • True, but he said it only had to be hidden, not necessarily secure
    – Dave Wise
    May 5, 2011 at 20:11
  • Yep, that's true I suppose. I'd rather take the route to ensure security than audience target. If they don't need to see it, they shouldn't have access to it.
    – Eric Alexander
    May 5, 2011 at 20:48
  • 4
    Understandable, but I'm coming from the perspective of managing a very large SharePoint deployment where per-item security settings are "evil". They lie out there and multiply in the darkness making the management of site security that much more complex because nobody ever remembers that they put that security out there.
    – Dave Wise
    May 5, 2011 at 21:01
  • I suppose it also depends on the sensitivity of the content needing to be restricted. The preferred route would be creating a secured document library and not item level permissions for various files in a library.
    – Eric Alexander
    May 6, 2011 at 0:29
0

If you have publishing turned on you can do this as well by unpublishing the pages, then you can create groups with specific permissions to see pages in various states.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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