| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| SharePoint | Planning Hub Sites | https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/commits/public/SharePoint/SharePointOnline/planning-hub-sites.md | At their core, the three types of building blocks share a common structure. For |**Content authors** <br/> |**All members are content authors** who jointly create and edit content. <br/> |**Small number of content authors** and a much larger number of content readers or consumers. <br/> |**Hub site owner** defines the shared experiences for hub navigation and theme. **Hub site members** create content on the hub site as with any other SharePoint site. Owners and members of the sites associated with the parent hub create content on individual sites. <br/> | |**Governance** <br/> (as allowed for your organization based on the settings in the Security & Compliance center) <br/> |Norms typically **determined by the team**. Practices are aligned in the best way to get work done. <br/> |Policies often **determined by the organization** to ensure consistency of experience and effective management of organizational information. <br/> |Governance **determined by each owner of the associated site based on the type of site and organizational policies**. The best experience for visitors is achieved when everyone has at least read permissions for associated sites (but this is not required). <br/> | |**Permissions** <br/> |Microsoft 365 group, plus SharePoint groups and permission levels <br/> |SharePoint group <br/> |Same as original site type. Hub sites do not alter an associated site's permissions - but you may add a "reader" group to the hub to make it easier to provide read access to associated sites. For more information, see: [Hub permissions](https://support.microsoft.com/office/set-up-your-sharepoint-hub-site-e2daed64-658c-4462-aeaf-7d1a92eba098#bkmk_managesiteassociationapprovals). <br/> |-|**Created by** <br/> |**Site owner** (unless this has been disabled in your organization) or **admin**. <br/> |**Site owner** (unless this has been disabled in your organization) <br/> |[SharePoint site administrators](/sharepoint/site-permissions#site-admins) and [above](/sharepoint/site-permissions) in Microsoft 365 <br/> | +|**Created by** <br/> |**Site owner** (unless this has been disabled in your organization) or **admin**. <br/> |**Site owner** (unless this has been disabled in your organization) <br/> |[SharePoint site administrators](/sharepoint/site-permissions#site-admins) and above in Microsoft 365 <br/> | |**Examples** <br/> | - Project team working together to complete deliverables and manage tasks. <br/> - Holiday party planning committee planning the annual get-together. <br/> - HR performance management team. <br/> - Executive committeeΓÇödifferent leadership groups within the organization. <br/> - Extranet site to work with Partner A. <br/> | - Travel team publishing guidelines about corporate travel. <br/> - Policies and procedures. <br/> - Micro-site for a new corporate initiative. <br/> - Resources for the sales team for a product or service. <br/> | - HR hub that provides a connection and roll-up for all HR functions, such as benefits, compensation, performance management, talent acquisition, and a manager portal. <br/> - Sales hub providing enterprise resources for the Sales organization and connecting regional sales team and communication sites. <br/> - Location-specific hub that groups the communication and team sites for a specific location (for example, the New York office). <br/> | ## What should be a hub site? |