Syntphony hub sites. Behaviour, content roll up and SharePoint integration.

Architecture information is crucial in SharePoint online to guarantee a correct distribution of contents through the communities. Syntphony provides the capability to create well design architecture information by using hub sites. The concept and use is similar to how SharePoint online works with Hub sites, but including less limitations as we will check.

Syntphony hub sites. Content roll up.

Defining a site as hub in Syntphony is straightforward and can be done during site creation or edition through the community forms.

Community owners can select whether to define a site as hub as well as its parent hub site if it applies. These configurations will end up in a well structured architecture information of hub sites and its children in different levels as shown in the picture as example

Having this hub structure allows to apply content roll up within the dashboard components which means that if dashboard is configured to do so it can query contents for the specific sites and its children. This is very useful for organizations to apply global and specific sites contents and show them in dashboards.

SharePoint hub integration

By default when a site is defined in Syntphony as hub it will be synchronized also in SharePoint and registered as a Hub site so that the information architecture remains equal than in Syntphony.

Limitation: Due to technical limitation the capability to join a hub site to another hub is limited in SharePoint to only users having administrator access to SharePoint online admin center. This means that starting by a 3 level architecture the hub to hub joining needs to be performed in the SharePoint central admin by an administrator.

https://learn.microsoft.com/en-us/sharepoint/hub-to-hub-association

Syntphony and SharePoint hub comparison

The following table presents the main differences between both type of hubs.