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

I'm about to model an organization with SharePoint 2010. I found out there are lots of Task Passing through different parts and divisions of organization. For example a task created from Management Division, then, it assign to Finance division, then it assign to Engineering division, and so on. Task (and Document) passing aside, There are lots of information as many lists, belongs to each division.

First, I tried to create different subsites for each division:

  • MyOrg Site Collection
    • Division 1 Sub site
    • Division 2 Sub site
    • ...

    Then I create some custom workflow activities to create subsites dynamically and copy lists and list items between subsites. The problem is data load over list item passing along with huge data replication (assume a manager on MyOrg want to track a task history and states, also all related divisions). Definitely, there is some reasons behind not supporting subsites negotiations by SharePoint.

Now, I don't know how to implement an organizational hierarchy structure with SharePoint, as when a user logs in, he traverse over different divisions, and view lists and libraries of that division.

I'm looking for a way to map the hierarchical structure of the organization with SharePoint, with or without subsites.

What do you suggest?

share|improve this question
Please rephrase mate. Your question makes no sense to me. Tx – Fox Dec 19 '12 at 8:21
@Fox: thank you! – Reza Owliaei Dec 19 '12 at 8:40

Your Answer


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

Browse other questions tagged or ask your own question.