Forum Discussion
Limitation on the number of Hub Sites
This limit disappoints me greatly. I had envisaged "normal" users being able to leverage Hub functionality. My own team is a "line of service" team and as such we have over 20 different SharePoint sites, and a Hub would have been the perfect solution, but in my organisation of 150,000 people, being allocated a hub from such a small pool is never going to happen :(
Thanks John
I had assumed based on the current limits that the "expected" use of this functionality was going to be limited to high to mid level organisational constructs such as "finance", "HR" etc, and so also assumed that even if the limit was raised it wouldn't be a particularly large number.
Are we saying that the vision is that anyone will be able to create a hub site (to replace the old "sub site" functionality)? If so this would be great news
- Conceptually, hub sites are not limited to organisational constructs. A hub site is a site which has been registered to allow other sites to be associated with it. A hub site enables a common navigation and look and feel together with focused search capabilities. Hub sites are not a replacement for sub sites and don’t serve the same hierarchical function. Any user can be permitted to create a hub site but from a governance perspective limiting access would be advisable. Unlike legacy site types, hub sites are easy to create, modify and delete. Deletion does not delete the site simply it’s role as a hub. So, the limitation on the number of hub sites is not restricted because of the ‘role’ of the site but a decision by Microsoft to cap this number. Different organisations may find the limit problem free but many, particularly larger organisations may hit issues. Hope this helps! There is plenty of content by Microsoft and other contributors here which better explain hub sites. Regards.
Hi John,
I understand the concept of hub sites (well I thought I did lol), but am a little bit confused by your statement "Hub sites are not a replacement for sub sites and don’t serve the same hierarchical function". Given that Microsoft direction is groups, and creating an MS team effectively creates a Site collection, then "Sub sites" are effectively redundant and they would not have MS Teams functionality (for example). Whilst you can create as many "channels" as you like in an MS team, there are plenty of scenarios where you would want to create a totally separate Team for something, yet have these teams grouped together, so when hubs was announced, I thought this was one of its intended uses. If not …. it should be :)