Don't think this has been suggested yet, but Hub sites should definitely allow nesting!! The flat/flexible organization is good, and allowing some hierarchy/rollup with hubs is better, but would be best if a hub could be a sub of another hub (a branch, sub of region, sub of district) and have rollup through each level of nested hubs. Allows best of both worlds - flexibility of flat and dynamic association, with advantages of multi-layer hubs!

Security trim the hub site's top menu bar

Add filtering to News and Events rolled up to the Hub Site e.g. allow filtering by a metadata column to selected items are shown rather than all. This would allow news to show in a connected site but only appear on the Hub based on the filter criteria.

The footer of a Hub Site should be propagated along with the Hub menu and the look and feel to all the associated sites.

We need a cmdlet that lists all the sites that are linked to a Hub Site. Maybe call it Get-SPOHubSiteLinkedSites and it would take as a parameter the URL of the Hub Site.

When will we be able to share lists across modern sites in SharePoint? This is the number one driver for creating subsites.

The unstructured google search nature of managed metadata doesn’t cut it in the business world. Business information is highly structured, based on lists; contracts, purchase orders, work packages, invoices, etc. Filtering and search refiners get results, not hit and miss vague searches based on tags.

You don’t want us to use classic subsites? Fine. Then make the reason for using subsites work in modern.

We have several groups that could really use this simple connections using our existing meta data. This functionality needs to be added in SP Server 2019 on premise

Make option: Create content types on Hub sites that will be available for connected sites

If you have i.e. 10 sites connected to the hub site this option will reduce the maintenance of content types in individual sites.

This should be optional and replace the content type hubs

Hub sites: suppress sites where you have no access.
Sites that are on the sites web part in hub sites should be suppressed when the user has no access.

That is in line with behavior on SP sites

We should have the possibility to choose easily if an link in the lefthand menu or the hub's menu should open in a new tab or not. There 's no option about this nor in the modern settings neither in the hub settings.

Currently if a site owner opens the Site Information flyout menu and opens the dropdown of Hub Sites available for association the user will see all Hub Sites in the tenant, even those the user has no permissions to view. This might reveal Hub Sites with confidential information (like R&D project names) the user otherwise would have never been able to see.

Thus, the dropdown list showing the Hub Sites should only the Hub Sites the current user has (at least) "view" permissions on.

Document libraries in hub sites should be available to sites that are apart of the Hub site. We've recently migrated our Intranet to SharePoint and elected to use the modern Communication site as a hub site and have created other communication sites to serve as department sites. It's frustrating to have to reupload common images (logos, etc.) to each individual site. We'd like to see a scenario where we can browse and use those libraries in the Hub site throughout the connected sites.

In my Intranet I plan to have many hub sites in which I would like to duplicate about a hundred links without having to manually create them all. It would be great to be able to script this with PowerShell.

Another great option would be to allow you to connect to the term store for a set of links to display (giving you centralized control and singular management)

Owners of a Hub site can post new/ links / events that will appear on all connected sites. EG information can flow down not just up.

Support Hub Site Navigation on Classic Web Pages

When a classic web page is added to t a modern site the hub site navigation disappears. I would think that the hub site navigation should not be impacted by this.

Please can we add the same level of customisation as is present in the News and Events web apps to other web apps?

Specfically, I would like to be able to consolidate the associated-sites calendars into one that can be seen and subscribed to from the Hub site.

*English follows Japanese
■Title(件名)：
ハブサイトに関連付けしたサイトの外観について

Ability to change the look of hub site

ハブサイトに関連付けしたサイトの外観を変更しても、ハブサイトに設定している外観が継承される動作となり、関連付けしたサイトで変更した外観が元に戻ってしまい独自の外観に設定する事が出来ません。そのため、ハブサイトに関連付けしたサイトにおいても独自の外観に変更が可能となるよう機能の拡充を要望いたします。

Even if we change the look of hub site associated sites, the look of hub sites gets inherited regardless, end up with 2 exactly same looking sites. Provide ability to change the look of sites.

Thank you for your consideration.