This would be an incredibly useful addition, both for multi-brand companies, but also companies that service multiple user groups along the supply chain. We fall into both of those categories.
We're a B2B software company, and we need a separate knowledge base for our client implementations, and one for end-users. And we do not want end-users to see the implementation resources.
Hi there, It's unfortunate that this functionality doesn't exist. For us, I'd like to have a knowledge base for general onboarding and customer service support and a second knowledge base specifically used for the diagnostic services we offer - best to keep these search functions separate.
It seems worth noting that Hubspot itself has separate knowledge bases on it's help center, One called "knowledge base", one for Community, etc.. It would be great to have that same feature available as a customer.
We just upgraded to business units and so now I still can keep the two business units contained because they need to share a knowledge base. This impact branding ect.
Hey HS Team... Haven't heard an update regarding this request since 2020 when you admitted that it was one of the most highly-requested features. Curious if there's been any news?
I upvote this. We're dithching Zendesk in the process of implementing Hubspot, but the ability to have multiple bases (in my case, on for Internal support and one for External support) are sorely missed.
Also would love to know what the status is on this. With Business Units, two knowledge bases are essential and obviously needed for other use cases as well.
I agree with other folks, this would be extremely helpful for us - different KBs for different product lines (enteprise, consumer, API docs, etc.). Ideally they'd live at different subdomains, and gated access would be a nice feature too.
I upvote for the multiple knowledgebases project. We have three stakeholder groups (end users, agencies, distributors) who have very different questions and needs and overlap between would cause confusion and other issues. Categorizing doesn't get us where we need to be on this in the current KB.
There are two reasons this would be EXCELLENT. 1. So many smaller SaaS companies end up with Value Added Resellers whitelabeling their products or OEMs embedding their products. This would be killer to eliminate the need to manually create duplicate articles based on Brand
2. The ability to have internal & external articles would be amazing. I have all of my internal job aids stored in word on Sharepoint. So my employees have to look in two places for how-tos. What if they could look in one place!
Ideally, I can see this solved via the following: 1. Create an article, and add option to publish to KB 1 with Brand color scheme 1, and also to KB 2 with Brand Color scheme 2. 2. Allow articles to be published internally and/or externally
Giving this another bump, I have so many ideas that can't be launched until this is available and have been waiting for three years now. Please put this back on the roadmap.
