Nested Hub Sites
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!
The idea was posted over 2 years ago and people are still adding comments. Is this getting any traction at all?
Agreed! We would greatly appreciate this feature. I understand we can create Subsites, but if the idea to stay away from them we certainly need nested hub sites.
This is critical for big organization like us, please put it in the roadmap as soon as possible
I have a need for the same thing. We have so many sites that are associated with a Hub but also need to be nested as a subhub within the main Hub.
We have the need for this as well. Many of our large departments (IT, Finance, etc. Need to be a hub site, but I also need to connect these to our Portal Hub with all the functionality of a hub site. This means I would want to nest them in the Portal, but allow them to be their own hub (two menus).
I'm here looking for the same thing. I want to have a hub site with three sites. Then each of those 3 sites could link to 100's of opportunities. I'm unsure how to structure the 100's of opportunities within the limits of Teams channels.
Ruben Hugo commented
We commonly have clients that require multiple levels of Hub Sites to model their organisational structure along the lines of:
Org Wide > Directorate > Department > Functional Site/Team
It would be good if Hub Sites could be nested down to 3 levels at least - but ideally 4.
Ryan Robinson commented
There is a new PowerShell command for associating one hub with another hub: https://docs.microsoft.com/en-us/powershell/module/sharepoint-online/add-spohubtohubassociation?view=sharepoint-ps
It says it is in preview and I don't have it in my tenant. I also haven't heard any announcements about how it will work. I would love to know what gets inherited down multiple levels and what doesn't. In our context, I would love to inherit the navigation down multiple levels but only inherit the site/group icon from only one level above.
Venkatesh Setty commented
This is like a primary/standard feature that should have been available in the first release. There are hundreds of organizations whose structure level cannot be managed with 1 level. This is needed or should have been available almost 2 years ago.. but we still don' have it. When is this gonna be made available ????
Rumen Moskov commented
The should be an option for a Global Tenant Wide Native Navigation instead of manually creating one on a HUB Level. The Case in our organization is that we are a Global Business Service Center in two location each with a Communication Site connected via a HUB Site. All other related sub departments are under either a SPO Team Site or a Function Communication Site with various web parts for the needs. However both centers are about 4k people you can imagine the number of sub-departments and eventhough we are taking a hybrid model which onboard various departments to collaborate on MS Teams in private channels and MS OG Groups this does not allow us to have a global company wide native navigation across all other sub departments, regions etc. Ingram Micro is operating in over 100 countries and you can imagine that on the global level the corporation has a different menu than on our Sub Organizational Entity which supports the Global Business. We would really appreicate your efforts in providing a Global Tenant Wide Navigation for large scale corporations with more than 20k people.
Greg Mc commented
Still looking to see if this has been done. Very simple case scenario: A Sales organization that has 30 plus distributors around the globe. These are setup in about 6 different groupings by region. I would associate them with the Sales Hub. The Sales hub should associate with the Company wide hub. This allows the Company wide menu and theme to be passed to Sales which in turn allows the company wide menu and theme to be passed to all the sales regional sites along with any special global menu settings at the sales level. Would love to see that but can't seem to find it. Yet.
My problem, having 5 different sites with local news, together with Corporate news, and Marketing news, cluttering all different news together on our intranet front-page, would be solved by associate a News hub to our Intranet main hub. Enabling to gather all news in one place, and differentiate the different news in separate web-parts on the Front-page.
It's been almost 2 years since this post was made, has anybody found anything from microsoft indicating how its coming along? (if it's coming along...)
Absolutely, Our Intranet is SharePoint and if our Hubs were nested we would only have to changing the themeing on the top hub for all the others to follow. Instead we have to go through each hub to update themeing.
The use case is: one site collection for HR that at the top level is regional. Subsites would then be created for each country in the language of the country. Each country has a hub site with multiple site collections or sites associated with it. The HR site for that country would be one of those sites.
The advantage is that HR (or Health & Safety) just stay in one place to maintain all their content.
Villads Chester commented
SO, SO needed feature for large companies. Flat hierarchy? How to build an effective intranet using SharePoint without this functionality? ONE Hub to connect main sites, but then no hub functionality for smaller sites? That is our option for now. PLEASE, PLEASE consider this.
Yes, designing a proper menu function would require some work, but still. PLEASE, PLEASE
Mike H commented
Law enforcement/police departments really need hub sites!! having to adjust without it for now. Thanks
Ashwani Singh commented
Needed this feature very badly, We designed 2 level hubs-sites and want to associate sub-hubs to main hubs.
Yes, the whole idea of hubsites is to allow your site associations to morph as your organizational structure changes -- but whose org structure is only two levels deep?
If a hub site could also be associated to a hub site, you could completely remove the old ability to create subsites, and we could create an n-level hierarchy with the ultimate flexibility to be changed when needed.
Totally agree. we have 10k+ users and would benefit from this feature!