We have an established SharePoint 2010 intranet portal, which has many and various team sub-sites. These sub-sites are created on request - sometimes it's because one of our locations wants their own little area to share documents, or it might be for a company-wide project or initiative.
We are now slowly moving over to SharePoint Online. Mainly, it's to replace Box and Dropbox (which some teams use), and allow our staff to share files externally if needed. Nothing special, just a document library. More often than not, each site will have its own unique permissions.
Now, our SharePoint 2010 site is one large site collection (wasn't my idea). As an administrator, that makes my life quite easy as it's one content database, one set of content types, etc. But, with SharePoint Online, I don't need to think about content databases, and won't be using custom content types with these sites.
So, I'm a bit stuck. My options, as I see it, are:
- One large site collection (pretty much a no-go as these shared files might get quite large)
- One site collection for each request, no questions asked (which might lead to hundreds of site collections)
- Create a site collection for each office location, and then a sub-site for each team in that location (as requested) - and also create a site collection for each company-wide function, and create a sub-site for each project within that function
Can anyone give any pointers towards the "best" option to use here?