# Navigate between Knowledge Bases

**URL:** <https://community.hubspot.com/t/navigate-between-knowledge-bases/123537>\
**Category:** Knowledge Base Tool\
**Tags:** professional\
**Created:** [January 8, 2025, 10:27pm UTC](https://community.hubspot.com/t/navigate-between-knowledge-bases/123537 "2025-01-08T22:27:42Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![nigeld27](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/nigeld27/32/89259_2.png) [@nigeld27](https://community.hubspot.com/u/nigeld27)\
**Post date:** [January 8, 2025, 10:27pm UTC](https://community.hubspot.com/t/navigate-between-knowledge-bases/123537/1 "2025-01-08T22:27:42Z")

</div>

Hello,

We are new to Knowledge Bases. We have some customers who have access to 2-3 different Knowledge bases.

Is there a recommended way for how the customer would navigate between them? I can’t see to create a custom navigation menu to link to a different KB.

Thanks,

Nigel

---

<div class="post-metadata">

**Author:** ![Berangere](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/berangere/32/220784_2.png) [@Berangere](https://community.hubspot.com/u/Berangere)\
**Post date:** [January 9, 2025, 10:24am UTC](https://community.hubspot.com/t/navigate-between-knowledge-bases/123537/2 "2025-01-09T10:24:22Z")

</div>

Hi @nigeld27 and Happy New Year! 🎉  
Wishing you the very best for 2025!  
Great question, thanks for asking the Community!  
First, I’d like to share these resources that might be of interest:  
- [Create and manage multiple knowledge bases](https://knowledge.hubspot.com/knowledge-base/create-multiple-knowledge-bases#use-additional-knowledge-bases-in-conversations)  
- [Customize your knowledge base template](https://knowledge.hubspot.com/knowledge-base/customize-your-knowledge-base-appearance)  
- [Customize knowledge base settings](https://knowledge.hubspot.com/knowledge-base/customize-knowledge-base-settings)  
Also, I’d love to put you in touch with some of our Top Experts and Community Members: Hi @Kalsi, @MHanneson, @evaldas, [@Nisse\_](https://community.hubspot.com/t5/user/viewprofilepage/user-id/865425), @TomM2, @JTolley, @DNeal32, @OArdila, @NamV and @danmoyle do you have suggestions to help @nigeld27, please?  
Have a wonderful day and thanks so much! ❤  
Best,  
Bérangère

---

<div class="post-metadata">

**Author:** ![danmoyle](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/danmoyle/32/91166_2.png) [@danmoyle](https://community.hubspot.com/u/danmoyle)\
**Post date:** [January 10, 2025, 7:26pm UTC](https://community.hubspot.com/t/navigate-between-knowledge-bases/123537/3 "2025-01-10T19:26:14Z")

</div>

Hey there @nigeld27. [@BérangèreL](https://community.hubspot.com/t5/user/viewprofilepage/user-id/230185) shared some great resources to help. I have a question - can you share more about customers who have access to different knowledge bases? Are the KBs able to be consolidated and you could use tags instead? With HubSpot, you can put some pages behind membership/passwords, which could keep some content protected.

I’m curious about the use case and “why” - that may help us answer the “how.” 😊

---

<div class="post-metadata">

**Author:** ![nigeld27](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/nigeld27/32/89259_2.png) [@nigeld27](https://community.hubspot.com/u/nigeld27)\
**Post date:** [January 10, 2025, 8:53pm UTC](https://community.hubspot.com/t/navigate-between-knowledge-bases/123537/4 "2025-01-10T20:53:53Z")

</div>

Hi @danmoyle

We provide customer support to organisations, and we support their use of different technology platforms. Let’s call the Platform A and B. Some customers pay for us to support them on A, and some pay for B, and some customers have both.

I understand your thinking, but consolidating them into one mega library will just result in one set of customers seeing passworded knowledge pages for guides that have absolutely no relevance for them. It would probably negatively impact their experience.