Hi All,

I am in the process of implementing sharepoint 2013 to one of the client. the client have various departments each have separte type of documents. so what is the best practice... make each department as a site collection or create as subsites.

I know that Site Collections are better boundaries for security, so I typically do a Site collection per department. Have the Root site (/) be for the company.

But if i start with site collection and later may be i want to share some document from one department for another dept, i might have issue.

Any thoughts arou

Generally its best to structure a site along functional rather than structural lines. So instead of building Site Collections named after each department, it might be better to analyze what is actually done and create a structure for that. Orgs can change structure, but the business functions may do so less. Also multiple departments are likely to work on information that moves the business forward. (Unless Departments really are a silo!)

Site Collections do form a boundary for permissions, but so what? You can add users to the new site collections at need too. Also, consider using AD Groups to some permissions that span boundaries. AD Groups set in more than one collection might save some work. (Add user in AD but they get access to both Site Collections)

Consider the likely size of Site Collections before implementing. If the overall size of Content is likely to exceed 100Gb for example, ensure the different Site Collections get their own Content Databases.