Forum Discussion
How to coexist two site collection created for the different purpose for the same department?
- It depends. For large organizations, HR might have multiple communication sites - one for Benefits, one for Recruiting/Talent Acquistion, one for Performance Management plus a "main" HR site that might be a hub for all of the HR sites. See: https://learn.microsoft.com/en-us/sharepoint/planning-hub-sites#what-should-be-a-hub-site for an example. No, you should not activate publishing features on your modern team site (you may break things if you do) and NO do not mix private team collaboration with communication sites for "publishing" content to a broad audience. Your team site is where you "make the sausage." The communication site is where you "sell the sausage." Your multiple site collections are NOT for the same purpose at all. One is for collaboration and the other is for communication. Different purpose, different audience. Especially with HR, you do not want private HR content on a "public" site. I teach a workshop on information architecture for SharePoint intranets if you want to learn more. The next one will be at 365 EduCon in DC in June.
tom_s1865 Another "it depends" answer. If you want the search scope for your hub to just show sites connected to the hub, don't associate private sites. Private content will be searchable at the organization level. Typically, private team collaboration sites are not connected to the hub(s) representing your intranet, but they could be. By associated to the hub, you will remove the ability of the Team Owner to set the theme on the SharePoint site associated to the Team. When a user goes to the team site, which they might not do if they are working in Teams, they would see the hub navigation - which could be helpful or could be a distraction. I typically do not consider private collaboration spaces part of the intranet, so I don't always connect teams sites to hubs, but there are exceptions when there is an outcome goal to scope search (or read permissions) to a group of team sites. If that is the use case, then I might associate a team site to a hub but not add it to the hub navigation.
