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

If you have various departments like Human Resources, Operations, Marketing, etc. what is the best way to setup Sharepoint to accommodate each department?
Should each department have a subsite of their own?

And, how does one handle shared resources like document libraries?
I.e. each department might have their own subsite, but would still need to share documents across different departments?

share|improve this question
up vote 0 down vote accepted

It is wise to segregate departments as separate functions. Each department function has their own unique processes. Granted there are times when they may cross. Each department can have their own set of sub sites contained, with unique permissions and content.

You can create shared workspaces. This can be access restricted with the creation of SharePoint groups which could contain members of different departments. I use this with certain projects. My experience is not vast with SharePoint, but you should certainly branch out your corporate functions and utilise the inbuilt security model to meet your requirements.

share|improve this answer

Is this SP 2013 or SP 2010 ?

Generally, it is cleaner to give each department there own site collection.

But, there is one thing to keep in mind when splitting your departments across different site collections vs keeping them in one. Cross-SPSite query'ing is usually a problem. Everything inside an SPSite is more or less accessible from accross other Subsites, but once you need something from outside the SPSite, you will usually see that it is troublesome.

There are several options for showing data from one site inside another:

  • SP2010
    • Content Query Web Part
    • A good tool for aggregating content
    • Needs a custom XSL to look cleaner
    • List View WebPart
    • With some customization, you can view lists from a different site with it (export the built-in wp's through SPDesigner for example
  • SP2013
    • Same as SP2010
    • Content Search Web Part
    • Uses the search engine to aggregate items, cross-SPSite is possible
    • Has some built-in templates but not as nice as a ListViewWebPart (like CQWP)

You should look up the software limits for Site Collections and figure out if you would need several site collections to accomodate your needs or not.

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.