Sep 22 2016 05:35 AM
This discsussion has two parts:
Firstly, I've seen three different approaches in Office 365 where you can manage SharePoint sites:
Using approach 1 above the site seems to end up as a root site alongside other /teams/ or /sites/ sites. (I can see this in SharePoint admin center under site collections)
Similarly using approach 2 above you end up with the site created at the same location. (I can see this in SharePoint admin center under site collections)
Then, using approach 3 above I created another test and yet that site didn't show up in Site Collections in the SharePoint Admin Center. Where does this end up in the hierarchy?
SiteManager.aspx
If I go to the site manager using the following URL: https://mycompany.sharepoint.com/_layouts/15/sitemanager.aspx I see the following:
What I don't see are the sites created using approach 1 and 2.
So my questions are:
Sep 22 2016 06:38 AM
I'm not sure if I 100% understand your post.
Approach 1 and 2 are creating site collections approach 3 is giving you subsites.
Site manager gives you an overview of your current site collection.
Office 365 Admin/SharePoint Admin gives you an overview of site collections
Sep 22 2016 07:43 AM
SolutionSep 22 2016 09:02 AM
Sep 23 2016 12:42 AM
I would be interested to know that too
Sep 26 2016 11:31 AM
@Juan Carlos González Martín - in terms of best practice I've seen a lot of material/courses on the web suggesting the structing of SharePoint data into subsites by, for example, department. It goes further and describes scenarios where you could have public and private websites per department so for example HR could have an internal/private site that holds content and documents that is secured in such a way that only they can see/edit it. Then they could have a public site where content and documents are made available to the entire organisation.
A disciplinary action document would be stored in their private site, but a 'leave application document' would be stored in the public site.
I don't think this is a bad approach considering it clearly defines the boundaries in terms of security.
Bringing this back to Site Collections vs Sites. Would it be advisable to create a Site Collection for HR and have the two sites (private/public) in that Site Collection or would one rather just create an HR subsite under the main Teamsite and then two additional subsites under that one for public and private access?
I think the reason why this line questioning came up for me is because of the SharePoint landing page and the fact that clicking that New Site button creates a new site instead of a Site Collection. It seemed to me that Microsoft was pushing the idea of keeping all new subsites under the root Site (whichever that was supposed to be), because if you didn't manage Site Collections from the Admin Center then ultimately you would end up with a hierarchy under the TeamSite. For me landing on the SharePoint landing page and clicking on Create Site should from the start have created a Site Collection then you could use Site Contents to add additional subsites under that.
Sep 26 2016 11:47 AM
Sep 27 2016 08:41 AM
Feb 06 2017 05:15 PM
I agree with yourself Dean, for a heavily managed and governed and limited usability business go down the manual site collections and thousands of sub-sites.
I much prefer the site collections for containers of data and a site directory if users don't want to use the SharePoint landing page.
This is a model I think needs to be following in Office 365 with each SharePoint site only getting 1 O365 group and with all the O365 services tied to groups.
Sep 22 2016 07:43 AM
Solution