I know that this is a very broad question and I am looking for a very broad answer. We are beginning to plan our Sharepoint deployment in the Online, Office 365 version of the software. We are open to a hybrid setup if necessary, but would rather contain everything in the cloud as MS is slowly moving there anyway.
We have a company of roughly 250 employees. They are broken into roughly 15 planning teams. We have roughly 150 clients. Each client has roughly 10-30 projects in a given year. That is the basis of our setup.
Permissions are based on the teams, but there are little sub-teams of IT, Research, Reporting and stuff like that.
We initially thought we would set it up under one site container, but the 2000 subsite limitation per site-container put a kibash on that. Initially, I was planning on creating a workflow that would create a new project under that client as a subsite in a templated way. Clearly that isn’t going to work as I first thought.
Automating processes is our number one goal (maybe 1a, if you consider file storage and organization as maybe a number one goal). My natural inclination would be to create a site collection for each client now, with the projects still as subsites, but that brings in a higher level of complexion than I am comfortable with at this point…I think.
Can I automate the creation of these “Client” site-collections? Is that the best method? Can I template a site-collection so that I can build one and expect the other ones to look the same way? Will having approx 250 site collections limit my installation’s ability to operate?
Basically, am I missing something?
Thanks.
~Joe Fedorowicz
You Need to define the information Architecture in a well defined Manner.
-Create a Site Collection Based on Planning team and then Create a Subsites based on Projects that Planning teams are working.
can you Please provide more details about how the teams are collaborating based on Projects with Clients currently? Are this clients internal or external?
Hi,
For Site Collection Creation automation Process:
———————————————-
You can Create a Site Template and the upload as a solution and can use that site template to create a new Site Collection.
http://blog.ciaops.com/2013/07/using-site-template-with-new-site.html
its better you first create site collection and select template later. The PowerShell options, http://technet.microsoft.com/en-us/library/fp161370.aspx, for creating a site collection should provide the same. I don’t see an option to upload a template and create the site at the same time.
For Automatic sub site creation under Site Collection:
——————————————————
You can Restrict the Template selection from the Option : Page Layout and Site Template Settings (required Publish feature to be activated) So the user can only create site based on the specific templates.
Create a Normal List On the Main Landing page and ask users to fill out the details and activate a alerts on that list and you will get notification for new request.
The automation Process for creation of sites either require a Workflow/event receivers. For office 365 event receiver option cannot be used. For workflow it is achievable using a SharePoint designer and rest api.
https://www.dmcinfo.com/latest-thinking/blog/id/8661/create-site-fr…
http://blog.vgrem.com/2014/05/08/consuming-the-sharepoint-2013-rest…
There is also one path by using azure you can achieve the most of the development but i am not sure how that can be done but is possible through azure connection to O365.
