SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We're assessing SharePoint to use for our intranet site.

I want specific groups of users to be able to edit some hierarchies of content but not others. For example, HR contributors should be able to edit pages in the HR area of the site but not the Customer Service pages.

I've looked at doing this by:

  • Creating a wiki pages library for each area of the site - looks like it would be the simplest way of doing it but I can't see a way of setting specific permissions for a wiki library
  • Creating a new pages library (like 'SitePages') - site pages has options for setting permissions but I can't find a way of creating a pages library like this, only the wiki pages library.
  • Creating a new site collection for each of the areas of my site. This was suggested in a guide I read but seems a bit heavy handed.

What is the simplest way of doing this? I'm sure I'm missing something obvious.

share|improve this question
up vote 4 down vote accepted

You can set permissions at the list/library level, but I think I would agree with the guide and create a new site collection for each site.

Dealing with future requirements is then probably easier and permission inheritance is cleaner as you're not breaking inheritance for specific lists.

The following article is very useful -

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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