Now you can create separate knowledge bases / live chat widgets for different products or brands within a single Featurebase workspace. Each Help Center is fully featured and can be customized independently
This would be amazing. Our use case would be to have one “Help center” for internal use and one for external, clearly separated (not segmenting parts or pages).
Internal would be documenting support processes, FAQ’s, guides on how to resolve types of issues etc.
Sonia De Menditte
•
Sep 24, 2025
when is this going to be implemented? I’ve been waiting for so long, and I don’t want to postpone our project further in time again. Time’s ticking… :)
Stephanie Fannin
•
May 21, 2025
Even if they weren’t separate I would love to see a third categorization option so I could break the help center into, training collections & articles, knowledge base collections & articles and sales collateral collections and articles.
Divjot Singh
•
Jul 23, 2025
We have two sets of users: admins and end users. Both have different types of help articles. Right now we can only surface help articles to admins. It would be great to be able to have a separate help center for a different type of users.
Erik Kaljumäe
Team•
Jul 24, 2025
Hi @Divjot Singh!
This functionality is possible with Business plan - changing article access to Team members or Segments.
The objective is not just to surface help articles. Admins and end users have different priorities. So the default settings on Chatbot on the Messenger for admins would not be relevant for the end user.
In our current setup, can I have different settings on this default page: - one for admins (showing the image) - other for end users
For example, Course Enrolment Management: Admin Guide is not relevant for learners at all. But I we expose Messenger to a user, they would click on these featured articles that are not even relevant to them.
Are you able to see the problem now? Happy to explain further.
Erik Kaljumäe
Team•
Nov 10, 2025
Hey @Divjot Singh , thanks for the detailed explanation.
We have a similar feature request for showing different content within the Messenger based on user segments.
Would creating different home screen cards based on user roles (like "admin" or "end-user") solve this for you?
Feel free to give it an upvote if it fits your needs and/or add your thoughts as comments when deemed necessary.
Karin Olde Keizer
•
Aug 12, 2025
This would help us as well, if this means that the AI indexes these help centers separately. We’re adding a takeover product that has a slight overlap with our existing products, but in our use case it is essential for the two documentation sets to be kept separate.
Geon George
•
Aug 13, 2025
We have multiple products managed by the same team. Each product has overlapping articles so collections is not working for us.
Is there a way to create a help center per product?
Product team
•
Aug 29, 2025
Just to understand the product here, why would you not just use segments for this? Use API to auto tag users and choose what users see with segments? @Geon George@Karin Olde Keizer@Divjot Singh
Log in to comment and vote
Comments14
Feb 16
PinnedHey everyone! Super excited to introduce Multi-brand Help Center and Messenger widget support! 🎨
Now you can create separate knowledge bases / live chat widgets for different products or brands within a single Featurebase workspace. Each Help Center is fully featured and can be customized independently
Get started here: Create & manage multiple Help Centers
Patrik B
Nov 7, 2025
This would be amazing.
Our use case would be to have one “Help center” for internal use and one for external, clearly separated (not segmenting parts or pages).
Internal would be documenting support processes, FAQ’s, guides on how to resolve types of issues etc.
Sonia De Menditte
Sep 24, 2025
when is this going to be implemented? I’ve been waiting for so long, and I don’t want to postpone our project further in time again. Time’s ticking… :)
Stephanie Fannin
May 21, 2025
Even if they weren’t separate I would love to see a third categorization option so I could break the help center into, training collections & articles, knowledge base collections & articles and sales collateral collections and articles.
Divjot Singh
Jul 23, 2025
We have two sets of users: admins and end users. Both have different types of help articles. Right now we can only surface help articles to admins. It would be great to be able to have a separate help center for a different type of users.
Erik Kaljumäe
Jul 24, 2025
Hi @Divjot Singh!
This functionality is possible with Business plan - changing article access to
Team membersorSegments.https://help.featurebase.app/articles/6624453-help-center-privacy-controls#ffmaabb6krq
Divjot Singh
Nov 8, 2025
Sorry for the late reply @Erik Kaljumäe
The objective is not just to surface help articles. Admins and end users have different priorities. So the default settings on Chatbot on the Messenger for admins would not be relevant for the end user.
In our current setup, can I have different settings on this default page:
- one for admins (showing the image)
- other for end users
For example, Course Enrolment Management: Admin Guide is not relevant for learners at all. But I we expose Messenger to a user, they would click on these featured articles that are not even relevant to them.
Are you able to see the problem now? Happy to explain further.
Erik Kaljumäe
Nov 10, 2025
Hey @Divjot Singh , thanks for the detailed explanation.
We have a similar feature request for showing different content within the Messenger based on user segments.
You can check it out here:
Messenger widget configuration based on user segments (e.g., Users vs. Organizations) - Home Cards based on segments
Would creating different home screen cards based on user roles (like "admin" or "end-user") solve this for you?
Feel free to give it an upvote if it fits your needs and/or add your thoughts as comments when deemed necessary.
Karin Olde Keizer
Aug 12, 2025
This would help us as well, if this means that the AI indexes these help centers separately. We’re adding a takeover product that has a slight overlap with our existing products, but in our use case it is essential for the two documentation sets to be kept separate.
Geon George
Aug 13, 2025
We have multiple products managed by the same team. Each product has overlapping articles so collections is not working for us.
Is there a way to create a help center per product?
Product team
Aug 29, 2025
Just to understand the product here, why would you not just use segments for this? Use API to auto tag users and choose what users see with segments?
@Geon George @Karin Olde Keizer @Divjot Singh
Floris van Eck
Dec 18, 2025
This would be a great feature to have.
Would like to use it for:
Internal Help Center
External Help Center
And combined with segmentation also
Customer Help Center
Partner Help Center