Forum Discussion
Solved
For group integration, does SP site need to be a subsite of main tenant Site Collection?
I read that now we will have the choice to select if we want to create a group associated with our site when we generate a site. The question I have is if this needs to go through the Waffle Menu -->...
- Ok...the right statement would be: admins will be able to selectively upgrade existing team sites (Site Collection scope, no subsite scope)...and I'm talking here about linking a Team Site (A Site collection behind the scenes) with a Group...if you are talking about subsites, you will have there modern pages and all the new cool UI stuff..but not a Group...the Group is already linked at the root site
IMHO, the answer is "Yes" and you will always create a Site Collection linked to a Group or viceversa, but not a single subsite
- Interesting. Ok. That seems sensible. The reason I ask is because the current behavior is that a subsite of our main site is generated when using the "+" sign. Are you saying that if/when I finally get the ability to associate new site creation with a new group (i.e. New site -> asked if I want a new group, not the reverse), then this site will actually be in its own site collection just like current group sites (although hidden) are?
- Yes, that's what I'm saying...you will see that the creation experience is completely different and you will have to use a wizard for creating a Modern Team Site and the related Group
- @juan Carlos many +1s to you.
I was thinking that we would create site heirarchy (site collections with subsites) and be able to have groups associated with subsites but it looks like that is not the way things are going (or this isn't enabled yet). If that is the case, then I can't wait for the day we can generate relationships between groups/sites. I do wonder what will happen with peoples' current site collections (particularly for those who have more than one collection, each with subsites).
