HubSpot Ideas


Multiple Knowledge Bases

The ability to create more than one Knowledgebase. Similar to having multiple conversation inboxes or ticket pipelines.

  • This allows for knowledgebase segmentation.
    • Could be for Internal Vs External or Client Vs Prospect (Sales Vs Support)


HubSpot Updates
April 21, 2023 09:56 AM

Thank you so much for all of your feedback on this idea. It is now possible for all Service Hub Enterprise accounts to host multiple knowledge bases with distinct branding and content, all within one HubSpot account! Read more in this article.

March 16, 2023 06:41 AM

Absolutely agreed! It is currently possible to have multiple languages supported in the KB tool -- more on that in this article. That feature is compatible with the multiple KBs public beta; each KB can be in a different language, and can also have language variants configured. 🙂

March 16, 2023 05:39 AM

Hi everyone -- thanks for the questions and I apologize for the lack of clarity. Multiple KBs is a Service Hub Enterprise feature both during and after the public beta. You can learn more about how to opt your portal into a public beta in this article.

In Beta
March 15, 2023 09:02 AM

Hi everyone! Thank you so much for all of your feedback and interest in this feature over the years. I'm very happy to say that it is now possible (in beta!) for Service Hub Enterprise accounts to host multiple knowledge bases with distinct domains, branding, and content -- all within one HubSpot account. 🎉


If you filled out the form I linked here previously and you have Service Hub Enterprise on the Hub ID you sent in, I've already added you to the beta. Please let us know if you have any feedback as you test the feature out!


You can read more about how to set up multiple KBs in this article.

In Planning
July 12, 2022 10:45 AM

Hi all! I want to thank everyone for continuing to comment on this idea. I have read every comment, and the context shared here has been so, so helpful. 


I am updating this idea to “In planning” today. At the moment, we are unable to share a timeline or subscription level. Updates will be posted here going forward.


If you are interested in talking to our team about this feature or participating in a future beta, please fill out this form. I can’t guarantee that we’ll be able to speak with everyone, but the answers provided in the form will be a great help!


Thank you again for supporting this idea. We are looking forward to making this feature a reality at long last! 🎉

Not Currently Planned
October 29, 2020 07:33 AM

Hi everybody, 


This project is currently on hold and not yet in development, so I'm updating the status to "not currently planned" so you all have a better idea of what to expect. I'm sorry, I know this will be disappointing news 😞


It's unclear when we'll be able to continue working on this project, but it remains one of the most highly requested features for the knowledge base, so I assure you it will be considered in future plans. 


Your upvotes and comments with examples of how this would help you continue to be helpful, please keep submitting that feedback. This post will be updated again when there's more information to share. 


- Snaedis 

April 20, 2020 02:29 AM

Hey just to give an update on this:


Multiple languages for Knowledge Base will be made available this quarter (Q2 2020).


I expect Multiple Knowledge Bases to be available in the second half of this year.

In Planning
August 27, 2019 02:18 AM

Both multi-language and multiple knowledge bases are two features that are on our roadmap. We plan to have these features in place early next year.

214 Replies
Contributor | Platinum Partner

This will be especially useful for Enterprise portals running sites for multiple brands. We're already running multiple brand websites/domains, so adding separate Knowledge bases for them would be useful as well.


Having two or more knowledge bases would help us. We have a several segmented audiences who have different needs within our association. It wouldn't make sense for them to see the same knowledge base.


Multiple products in the same company. Definitely need separate knowledge bases.

Contributor | Diamond Partner

We were told we could do this. This is going to be a problem! We added Service hub to support our various business segments and now I find this request which means it can't be done. 😞 This has my vote! 


I am having this very issue. We chose Hubspot b/c of the ability for a non-tech native business team to capitalize on new technologies, however, given that we have multiple brands for our agency-model business we cannot manage more than 1 single knowledge hub at this moment. Very limiting and frustrating to our user experience. 


I wish this was a high priority issue. I cannot provide a functional, standardized support experience through Hubspot for my various clients now. 





This. Please!


Internal Use
Our usage would be for internal documentation visible by our employees on Hubspot only to walk through documentation

Vendor Use
Help vendors with FAQs on how to sell the products, how to use the products, things of that nature

Customer Use
Help with troubleshooting, setting something up, etc.


Having the ability to have an external knowledge base (which we already have in HubSpot) plus an internal knowledge base for our support team would be a huge help. As it is, unfortunately, I'm going to have to look for another solution for our internal knowledge base needs.


We need this as enterprise customer with over 50 countries and a lot of different use cases. One KB is not enough. 

Participant | Diamond Partner

We also need this badly!


We need one internal knowledge base (password protected if possible) for faculty and staff to view training and internal resources.


And we need a second knowledge base for current student resources.


Any idea when this functionality may be rolled out?


This is very important for us, and something that we unfortunately didnt consider when we moved from Zendesk to Service Hub.


Having multiple knowledge bases is very important being af European SaaS business we have customers with many different language preferences. Sincerly hope this will be priortized and also for Pro customers




This would be wonderful! I hope they implement this soon.


We haven't moved over to the HubSpot Knowedgebase because of this very reason. 


Yes we really need this!


This is exactly the need we have. Also, we would love to have templates and an UNDO button would be AWESOME!


Currently, we're using Google Doc Templates to create our Gizmo Guides™ but it would be amazing if there was a template system built-in to reduce the work-flow.


We need the ability to create multiple KB's to have internal Nerd Operating Manuals™ and External Gizmo Guides™ 


It would also be great if we could have a root domain for our Guides so we didn't have to use a sub domain. We would prefer instead of 

Top Contributor

+1 : multiple knowledge bases are needed. We use HS in several different countries and we need one KB per country. Robot wink


Needs to happen, multilingual!!

Member | Diamond Partner

Multiple products in the same company.

Definitely need separate knowledge bases. [2]


Our company has multiple brands with different websites for each product brand. We need to separate the knowledge base for each brand as information is different across each formulation.

Participant | Platinum Partner

We need this as regular user, don’t cry ’enterprise’ for every function, it required in our business also to support our needs


Being able to have separate KBs for different products would seal the deal for us. If we can't, we'll have to stick with other options.


Totally agree with this idea, my companies badly need this as well!


Today, our two major categories are based on the prefered language, and as a result, our knowledge base portal is not readable by our prospects and customers.


And when customers use the search bar or the chatbot, the resullts appear both in french and english! This is confusing.


Multi KB with different subdomains is a must for us, thanks Hubspot dev team 🙏🏼