Forum Discussion
Erik Wettergren
Jan 29, 2019Iron Contributor
Rollup of content across hubs
Hi,
I'm trying to figure out how to best structure our new Intranet. We're a medium sized company with a number of clients and with many of those clients we have multiple projects.
The initial idea was to make one hub-site for all internal stuff, with associated sites for IT, HR, the Office etc... Then to make one hub for each client and associate all project sites within the scope of this client with the corresponding client hub.
However, but quite often we work on topics in one client project, that would be really relevant to connect to an internal discussion to benefit our collective view and understanding of this particular topic. In other words. I would like to be able to rollup content from various client hubs (end connected sites) to one Internal site.
Any way to accomplish this? Or are there better ways to build the overall structure?
- Alan MarshallSteel ContributorOur company also has many projects for lots of customers so had the same structural questions. We decided to have a Teams space for each project and for each Client, we then use a hub site if we need to across the client and project sites. This split was to distinguish client only information that may be sensitive from projects. We then have a separate hub and Teams space for practices so anything that is cross project/product based goes in there, this may occur during a project or as a wrap up at the end to populate relevant content to the practice. Have practices separately meant we could identify important content form other project content for re-use.
- Erik WettergrenIron ContributorThanks, that definitely seem like a decent workaround. It's invaluable to do proper lessons learned sessions and during those I assume it could be feasible to identify documents and other content that could be useful in a wider context.
- Alan MarshallSteel ContributorWe piloted a number of models to see which worked best and what compromises you need to make for each and settled on this one as having the least number of drawbacks although not perfect. Keeping things loosely coupled would also enable us to re-organise the structure later if needed.
From a provisioning perspective you set this all up so that new projects are added to the correct hub site. The challenge will be the limitation on number of hub sites if you have lots of clients, in which case, you may need to use the highlighted content web part and sites web part to just select the associated sites rather than have it automated through Hub association.
We also have a separate hub site for the intranet published content with a communication site for each major function such as HR and Marketing so they manage their own content.