Forum Discussion
For group integration, does SP site need to be a subsite of main tenant Site Collection?
- 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
I want to make sure i understand clearly because this is a nuanced question:
In the future (planned rollout or whatever projection is most appropriate), will a subsite be able to receive an independent group? Can a subsite have its own group in the future?
OR, is it actually this: when groups are fully integrated with team sites (to the point where existing team sites can connect to groups and it is "feature complete"), will we only be able to have a group for the entire site collection? Therefore subsites would be essentially part of the same group as the top level site?
- 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
The part that introduces some confusion is Drew Madelung 's post that shows an infographic. The infographic says that admins will be able to selectively upgrade existing team sites. What if this team site is actually a subsite within a site collection? (again, in the future)