# Multiple Knowledge Bases

**URL:** <https://community.hubspot.com/t/multiple-knowledge-bases/10253>\
**Category:** HubSpot Ideas\
**Tags:** content\
**Created:** [September 17, 2018, 4:15pm UTC](https://community.hubspot.com/t/multiple-knowledge-bases/10253 "2018-09-17T16:15:33Z")\
**Posts on this page:** 20\
**Page:** 9

<div class="post-metadata">

**Author:** ![trevorhatfield](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/trevorhatfield/32/32521_2.png) [@trevorhatfield](https://community.hubspot.com/u/trevorhatfield)\
**Post date:** [January 30, 2022, 11:42am UTC](https://community.hubspot.com/t/multiple-knowledge-bases/10253/161 "2022-01-30T11:42:41Z")

</div>

Needed for multi-brand companies. Kind of crazy this isn’t available as I’m sure it is keeping many larger companies from adopting HubSpot.

---

<div class="post-metadata">

**Author:** ![LMcGill](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/lmcgill/32/14727_2.png) [@LMcGill](https://community.hubspot.com/u/LMcGill)\
**Post date:** [January 31, 2022, 3:55pm UTC](https://community.hubspot.com/t/multiple-knowledge-bases/10253/162 "2022-01-31T15:55:18Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![JBerk](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jberk/32/29368_2.png) [@JBerk](https://community.hubspot.com/u/JBerk)\
**Post date:** [February 3, 2022, 12:44pm UTC](https://community.hubspot.com/t/multiple-knowledge-bases/10253/163 "2022-02-03T12:44:03Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![DSresneck](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/dsresneck/32/59606_2.png) [@DSresneck](https://community.hubspot.com/u/DSresneck)\
**Post date:** [February 23, 2022, 11:16pm UTC](https://community.hubspot.com/t/multiple-knowledge-bases/10253/164 "2022-02-23T23:16:25Z")

</div>

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.

Thanks

---

<div class="post-metadata">

**Author:** ![FManzano](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/fmanzano/32/193630_2.png) [@FManzano](https://community.hubspot.com/u/FManzano)\
**Post date:** [February 28, 2022, 2:14pm UTC](https://community.hubspot.com/t/multiple-knowledge-bases/10253/165 "2022-02-28T14:14:18Z")

</div>

This would definitely help HubSpot’s own CRM 😉 Hopefully they can develop this.

---

<div class="post-metadata">

**Author:** ![richardwalsh](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/richardwalsh/32/9004_2.png) [@richardwalsh](https://community.hubspot.com/u/richardwalsh)\
**Post date:** [March 3, 2022, 5:09pm UTC](https://community.hubspot.com/t/multiple-knowledge-bases/10253/166 "2022-03-03T17:09:04Z")

</div>

At the enterprise level, with multiple brands and the new Business Unit addon, this is an absolute must.

---

<div class="post-metadata">

**Author:** ![michaelpalmer](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/michaelpalmer/32/92702_2.png) [@michaelpalmer](https://community.hubspot.com/u/michaelpalmer)\
**Post date:** [March 3, 2022, 6:38pm UTC](https://community.hubspot.com/t/multiple-knowledge-bases/10253/167 "2022-03-03T18:38:46Z")

</div>

This is a must needed solution.  
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.

---

<div class="post-metadata">

**Author:** ![JSevere](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jsevere/32/35926_2.png) [@JSevere](https://community.hubspot.com/u/JSevere)\
**Post date:** [March 7, 2022, 8:41pm UTC](https://community.hubspot.com/t/multiple-knowledge-bases/10253/168 "2022-03-07T20:41:52Z")

</div>

hello we need multiple knowledge base, what are you doing.

---

<div class="post-metadata">

**Author:** ![JPeypers](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jpeypers/32/48165_2.png) [@JPeypers](https://community.hubspot.com/u/JPeypers)\
**Post date:** [March 10, 2022, 12:20pm UTC](https://community.hubspot.com/t/multiple-knowledge-bases/10253/169 "2022-03-10T12:20:44Z")

</div>

Is there any update with regards to this request?

---

<div class="post-metadata">

**Author:** ![tcxen](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/tcxen/32/99782_2.png) [@tcxen](https://community.hubspot.com/u/tcxen)\
**Post date:** [March 14, 2022, 10:53pm UTC](https://community.hubspot.com/t/multiple-knowledge-bases/10253/170 "2022-03-14T22:53:08Z")

</div>

Still needed

---

<div class="post-metadata">

**Author:** ![noahmckeon](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/noahmckeon/32/78446_2.png) [@noahmckeon](https://community.hubspot.com/u/noahmckeon)\
**Post date:** [March 30, 2022, 3:30pm UTC](https://community.hubspot.com/t/multiple-knowledge-bases/10253/171 "2022-03-30T15:30:53Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![PAtlan](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/patlan/32/42298_2.png) [@PAtlan](https://community.hubspot.com/u/PAtlan)\
**Post date:** [March 31, 2022, 12:17pm UTC](https://community.hubspot.com/t/multiple-knowledge-bases/10253/172 "2022-03-31T12:17:14Z")

</div>

Hi,

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.

---

<div class="post-metadata">

**Author:** ![jweed5](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jweed5/32/193905_2.png) [@jweed5](https://community.hubspot.com/u/jweed5)\
**Post date:** [March 31, 2022, 3:02pm UTC](https://community.hubspot.com/t/multiple-knowledge-bases/10253/173 "2022-03-31T15:02:05Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![TheRJMB](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/therjmb/32/87988_2.png) [@TheRJMB](https://community.hubspot.com/u/TheRJMB)\
**Post date:** [March 31, 2022, 3:07pm UTC](https://community.hubspot.com/t/multiple-knowledge-bases/10253/174 "2022-03-31T15:07:35Z")

</div>

Can we get an update on this please. I’m considering moving to JIRA Service Management instead.

---

<div class="post-metadata">

**Author:** ![ABonatto](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/abonatto/32/74721_2.png) [@ABonatto](https://community.hubspot.com/u/ABonatto)\
**Post date:** [April 4, 2022, 10:11pm UTC](https://community.hubspot.com/t/multiple-knowledge-bases/10253/175 "2022-04-04T22:11:59Z")

</div>

we are moving to intercom =(

---

<div class="post-metadata">

**Author:** ![authenticlife](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/authenticlife/32/9373_2.png) [@authenticlife](https://community.hubspot.com/u/authenticlife)\
**Post date:** [April 11, 2022, 3:12pm UTC](https://community.hubspot.com/t/multiple-knowledge-bases/10253/176 "2022-04-11T15:12:14Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Iffah](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/iffah/32/31184_2.png) [@Iffah](https://community.hubspot.com/u/Iffah)\
**Post date:** [April 20, 2022, 1:34am UTC](https://community.hubspot.com/t/multiple-knowledge-bases/10253/177 "2022-04-20T01:34:11Z")

</div>

Upvoting the idea as this would be useful for companies that offer multiple products that are varied, which would need multiple KBs!

---

<div class="post-metadata">

**Author:** ![TPendergast7](https://avatars.discourse-cdn.com/v4/letter/t/ec9cab/32.png) [@TPendergast7](https://community.hubspot.com/u/TPendergast7)\
**Post date:** [April 27, 2022, 2:02pm UTC](https://community.hubspot.com/t/multiple-knowledge-bases/10253/178 "2022-04-27T14:02:00Z")

</div>

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.

Please make it happen HubSpot!

Thanks all.

---

<div class="post-metadata">

**Author:** ![CirrusAubrey](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/cirrusaubrey/32/44503_2.png) [@CirrusAubrey](https://community.hubspot.com/u/CirrusAubrey)\
**Post date:** [May 4, 2022, 6:09pm UTC](https://community.hubspot.com/t/multiple-knowledge-bases/10253/179 "2022-05-04T18:09:46Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![TheRJMB](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/therjmb/32/87988_2.png) [@TheRJMB](https://community.hubspot.com/u/TheRJMB)\
**Post date:** [May 5, 2022, 8:11am UTC](https://community.hubspot.com/t/multiple-knowledge-bases/10253/180 "2022-05-05T08:11:58Z")

</div>

Good shout – articles shared between Knowledge Bases would be crucial here.

[Previous page](https://community.hubspot.com/t/multiple-knowledge-bases/10253.md?page=8)

[Next page](https://community.hubspot.com/t/multiple-knowledge-bases/10253.md?page=10)
