question How can we help users easily identify the knowledgebase each article belongs to? in Community Central forum

How can we help users easily identify the knowledgebase each article belongs to?

jschnoll — Thu, 09 Oct 2025 20:05:24 GMT

Within our instance, we have two knowledgebases that house content with similar titles. Some users have access to both knowledgebases. I'm curious if there's a sustainable way to clearly indicate which knowledgebase an article resides in when users conduct a search or click into a knowledge article. I am part of an organization that has 35k employees so in an ideal world, I'd like something attention-grabbing like a tag or banner at the top of the article.

Re: How can we help users easily identify the knowledgebase each article belongs to?

Rafael Batistot — Fri, 10 Oct 2025 09:12:40 GMT

Hi @jschnoll

Are you using the Employer Center? Because this information already came

Re: How can we help users easily identify the knowledgebase each article belongs to?

jschnoll — Fri, 10 Oct 2025 15:56:52 GMT

Hi Rafael - Thanks for your response! That screenshot is helpful for considering how we can reformat what information shows in our search results.

Our organization would benefit from there being a visual indictor on knowledge articles. Do you happen to use or know of any possible solutions? Currently, the only way that a user can discern which knowledgebase an article is a part of is through the breadcrumb path.

Re: How can we help users easily identify the knowledgebase each article belongs to?

jschnoll — Fri, 10 Oct 2025 16:15:23 GMT

Hi Rafael - thanks for the response! Your screenshot is helpful in considering how we can reformat our search results. The screenshot below is how our search results are currently formatted:

Our users will benefit from the knowledgebase being more visually prominent when they click into a knowledge article. Currently, they rely on the breadcrumb path to understand context, which isn’t always intuitive to our users or visible, depending on how the article is accessed. Do you currently have a solution in place?