Is there anything new? Our customer owns 2 brand domains and especially there it must be possible to use several knowledge bases? In many cases, brand domains are money burned... unfortunately.
This would help our enterprise portal, as we are running sites for multiple brands in different service areas. At present we have to look elsewhere for a solution.
Agree with most of the comments here - we have two separate brands and its consistently frustrating that even though we have an enterprise account, that one brand has to taken priority over the other. We desperately need two Knowledge bases to support our increasing customer bases. At the moment, we can only operate one Knowledge Base and, as such are deploying another solution - chances are we will move away from HubSpot if this isn't eventually better managed.
Seems crazy that this still hasn't been made available given it was planned two years ago. We operate multiple brands which are entirely unrelated and the solution provided by Hubspot was simply to use categories to separate the content. This doesn't solve the issue that when someone uses search they'll get irrelevant search results. A very poor user experience in my opinion.
This has definitely got my vote. And I hope Hubspot sorts this soon!
We also would like this functionality ASAP. One for customers, one public, one for internal, etc... OR at very least, the ability to create custom templates so that we can make it appear as though they are separate without listing the full directory for everyone regardless of what main level they enter. (If that makes sense).
Is there a possibility to use different KB's with different Domains? That's what someone suggested yesterday at the GROW Europe Event. Does someone have experience with this?
When (if) this comes, it's important that articles can be shared and/or copied between the various knowledge bases easily, rather than having to Copy/Paste them and then remember to update on every instance when they're edited.
This should definitely be moved to a higher priority in the update queue given a. how many people have been requesting it, and b. the fact that your competitors allow this functionality natively. Our client has multiple Whitelabel partnerships and they need to be able to have a separate knowledge base for each partner that is branded for that partner. One other note that would be incredibly critical for this particular use case is the ability to publish updates to one knowledge base and push it to the other white-labeled knowledge base pages.
I know this is not currently planned, but this would be vary useful for folks trying to segment their KBs by different user bases accessing their site. Even if we could give specific permission based on the who the users are within the CRM, this could help us define who sees which article and display curated content for each, therefore assisting with inbound programs and creating evangelists.
Just adding another voice - this is essential and it is hugely frustrating for us. It is the only piece of the Service Hub we use so we may end up dropping it- especially because the lack of analytics about which users are accessing what content is very limted, meaning there is actually limited benefit to us using HubSpot vs a standalone solution.
Our products are very complex to divide and need different knowledge base chapters at least. If we connot divide these in different knowledge bases, our customers get confused as soon as they switch from one product to another (e.g. by using the search function or by brwosing the navigation). We are already able to divide by categories and link there from our website, but in general there is still the possibility for a customer to switch to the not-fitting articles. So for our product portfolio, divided knowledge bases are vital.