Help center Customer portals Build product-specific knowledge portals with Topics, Divisions and customer roles Updated Thursday, October 29, 2026 · Marcel Gravelle A B2B support team may support several products for the same organization, different brands with separate help centers, or customers entitled to different guidance. Supportbench customer portals let you present an appropriate knowledge experience for each audience while maintaining articles centrally. A portal selects from shared knowledge; creating another portal does not create an isolated copy of every article. This guide walks through a two-product example and the access checks that make the separation meaningful. At a glanceFor: knowledge managers, support operations leads and administrators serving multiple products, brands or customer audiences. Applies to: Supportbench Core.Start here: Settings → Self-Service → Customer portal; Settings → Knowledge Base → Topics Understand what is shared and what is separate · Choose the smallest structure that solves the customer’s problem · Plan a two-product audience matrix · Prepare access, Topics and representative articles · Create the first customer portal · Select knowledge coverage and customer access · Create the second portal and reuse suitable knowledge · Test the complete reader journey in both portals · Troubleshoot missing content and unexpected visibility · Give the structure an operating owner Understand what is shared and what is separate ElementPurposeOperational consequenceArticleThe maintained answer, procedure or reference.Keep one canonical article when the same instructions genuinely apply to several audiences. Its own publication and access rules still apply.TopicA grouping of related articles. Older controls can call it a container.Organize articles into useful product or task paths. A single article can belong to more than one appropriate Topic.Customer portal / CommunityA separately configured customer entry point, with its own identity, design and content selections.Choose the Topics and scope that this audience should use. A second portal does not automatically isolate the underlying articles.DivisionAn organizational scope that can affect article and portal visibility.Portal article scope includes a selected Division’s ancestors and descendants. Align article assignments and hierarchy deliberately; selecting one name is not an exact-ID isolation rule.Customer roleA customer-facing access grouping used by the supported portal/topic/article rules.Use it for intended customer audiences; verify the actual customer assignments.Agent RoleA staff permission and access grouping.Use it for internal agent access and administration. Do not give customers staff roles to control portal access.Selection and access are separateChoosing a Topic for a portal does not publish its drafts or override article restrictions. A branded portal address does not grant access. Test both a reader who should see an article and a reader who should not. Choose the smallest structure that solves the customer’s problem Use separate Topics within one portal when customers share the same entry point, branding and access model and simply need clearer navigation. Use separate portals when the intended customer experience differs: for example, distinct product branding, addresses, landing pages or access requirements. An internal staff-only knowledge collection usually needs internal article and Topic permissions, not a customer portal created for a staff role.Avoid copying every article into every portal. Copies can drift: an agent corrects one procedure while another customer keeps receiving the old answer. Reuse a canonical article when its prerequisites, steps and intended audience are the same. Create distinct articles when product behavior or permitted content genuinely differs, and link the relationship. Plan a two-product audience matrix Write down the intended structure before changing live settings. The example below is a recommendation, not a set of automatically created defaults.DecisionEquipment portalSoftware portalPortal identityEquipment HelpSoftware HelpArticle/portal Division scopeEquipment Support and specifically approved relevant DivisionsSoftware Support and specifically approved relevant DivisionsProduct TopicsEquipment setup; Maintenance; Equipment troubleshootingSoftware setup; Integrations; Software troubleshootingShared Topic, if suitableA reviewed common onboarding or support-process TopicThe same reviewed common Topic, with compatible Division and audience rulesCustomer audienceContacts entitled to equipment guidanceContacts entitled to software guidanceAllowed-reader checkEquipment customer opens an intended maintenance articleSoftware customer opens an intended integration articleExcluded-reader checkA contact without the required equipment access cannot read restricted maintenance contentA contact without the required software access cannot read restricted integration contentA customer who owns both products may legitimately need access to both portals. Record that case explicitly rather than interpreting all cross-portal access as a defect. Likewise, public product articles may be intentionally readable by everyone; selection into a product portal is useful navigation, not necessarily a confidentiality rule. Prepare access, Topics and representative articles Confirm the portal administrator has Administer communities and the necessary Division access. Identify the knowledge administrator who can manage Topics, article placement and publication.Open Settings → Knowledge Base → Topics. Create or review the product Topics and their hierarchy. Give them recognizable names that describe customer tasks.Review Public portal topic for Topics intended for a customer portal. The Core Topic Access editor exposes that flag and Agent Roles. That selector lists staff roles, but the stored Topic role restriction also participates in customer-portal audience checks and can cascade to child Topics. Do not assume it affects only staff or treat it as a Customer roles picker. Configure the intended customer entitlement through the portal and article controls described below, then test every applicable gate.Place the existing articles in the appropriate Topics and confirm their own Division, workflow status, external eligibility and customer restrictions. Keep drafts, internal troubleshooting notes and customer-specific material within their intended audiences.Choose a small representative article set for testing: one product-specific article, one shared article if applicable, and one article that an excluded customer must not be able to read.Prepare authorized test customers with known Company, Contact and customer-role relationships. Include a customer entitled to both products if that is part of your operating model.Before exposing a new entry point, review the articles themselves for customer suitability. Topic placement cannot make private case correspondence appropriate for a public knowledge article. Existing Topic-level customer-role rules created through earlier configuration can still affect reading even though the current Core Topic editor does not expose that control. Ask the responsible administrator to investigate such an inherited restriction rather than searching for a Customer roles field that is not present. Create the first customer portal Open Settings → Self-Service → Customer portal. Check the existing portal list so you do not create a duplicate of a portal that already serves this audience.Select New Community. In the creation dialog, enter a clear Name and an available Alias. Choose a theme when appropriate for your planned design.Select Create portal. Open the created portal and inspect its settings before distributing its address.Check the portal’s Division scope explicitly. Creation can initialize scope from the creating staff user’s profile. Do not assume that a new portal is blank, isolated, or already limited to the audience in your matrix.Blank scope is consequentialThe Visible divisions help describes a blank selection as global visibility. Set and verify the intended scope; do not leave the field blank because you expect blank to mean no access. Global portal scope still does not override independent article and customer restrictions. Select knowledge coverage and customer access In the portal’s Setup pane, turn on Enable knowledge base when this portal should offer knowledge. Disabling knowledge removes the knowledge experience; a design change alone does not re-enable it.Set Visible divisions to the intended scope from your matrix. Include the hierarchy in your decision: selecting a parent includes its descendants, and selecting a child includes its ancestors. Sibling Divisions are not included merely because the selected child shares their parent. Check the actual Division of each test article.Review Customer roles for the intended customer audience. Use the customer roles your organization maintains; do not substitute an Agent Role such as Tier 2 Support.Turn off Show all containers when this portal should display a curated product selection. In Knowledge base containers, select the corresponding existing Topics. The control’s container terminology refers to knowledge Topics.Review the portal’s sign-in requirements and customer access settings using the customer-portal configuration guide. Decide whether the intended knowledge is public or requires customer sign-in before testing access.Select Save Changes. Reopen Setup and verify the stored knowledge enablement, Division scope, customer roles and selected Topics.Review the portal’s landing page, branding, contact details and enabled languages. Design/page drafts use their own save and publication controls; saving portal settings is not proof that a design draft was published.Test the hierarchy as part of product separationIf Equipment and Software are children of a common Support Division, selecting Support includes both products. Selecting Equipment also includes articles assigned to its Support ancestor. A parent-level article can therefore be eligible in more than one child portal. Use the appropriate customer audience restrictions where entitlement matters, and test a parent article, a matching child article and an unrelated product article.An article must pass the applicable portal, Topic and article checks to appear. If a shared article disappears after you narrow Visible divisions, inspect its assigned Division and audience. Do not automatically broaden the portal to every Division to restore a single link. Create the second portal and reuse suitable knowledge Repeat the creation and Setup procedure for the second product, using its own matrix column. Select its product Topics rather than copying the first portal’s entire content selection. Add the shared Topic only when its articles and restrictions are appropriate in both experiences.For a common procedure such as requesting an account review, maintain one article and place it in the relevant shared or product Topics as needed. For procedures with different screens, prerequisites or product versions, keep the instructions distinct and use descriptive related links. Reuse should reduce maintenance mistakes without forcing unlike procedures into a vague universal answer.When agents need Knowledge article-view/list links to use the corresponding product portal address, configure the article Division’s Default KB community using the related guide. That link selection is separate from portal coverage and access, and it does not inherit from a parent Division. Test the complete reader journey in both portals Open each portal as a signed-out visitor. Confirm the intended branding, navigation and public knowledge behavior. If sign-in is required, verify that the anonymous experience matches that decision.Sign in as an allowed customer for the first product. Browse the selected Topics, search for a representative procedure and open its full article. Confirm its images, related links and language are useful.Open the same restricted article as a customer who should be excluded. Test the direct article link as well as navigation and search; hiding a navigation entry alone does not prove access is denied.Repeat the allowed/excluded tests in the second portal. Also test the customer entitled to both products when that scenario is intentional.Open a shared article from each portal. Confirm the same current instructions are available to the intended audience and that related links lead to an appropriate accessible destination.Check a narrow/mobile viewport and a second enabled language when applicable. Make sure customers can reach an answer without relying on a desktop-only menu or untranslated label.Record the portal, customer role, article, expected outcome, actual outcome and date. Resolve differences before announcing the new help center or replacing existing customer-facing links.Agent preview is useful for content review, but an agent’s broad permissions are not evidence of customer access. An article that an administrator can read may still be unavailable to an ordinary contact, and a customer allowed to see public guidance may correctly see the same answer in more than one portal. Troubleshoot missing content and unexpected visibility SymptomChecks and corrective actionThe portal has no knowledge navigation.Check Enable knowledge base, the saved portal settings and the published design. Confirm you are opening the intended portal address.Both portals show all product Topics.Check Show all containers and the selected Knowledge base containers in each portal. Confirm the changes were saved to the intended portal, then test with the intended customer.The Topic appears, but an article does not.Check the article’s publication status, external eligibility, Division assignment, language and customer restrictions. Also review the Topic’s portal visibility and access requirements.The administrator can read an article but a customer cannot.Compare customer-facing portal/Topic/article rules and the actual Contact’s customer roles. Agent Roles and staff Division access do not establish customer access.A customer sees a restricted product article unexpectedly.Check whether the article was actually intended to be public, the reader’s customer roles, any broad portal scope, selected Topics and article restrictions. Correct the intended access rule; removing only a menu link is not sufficient.Shared guidance disappears after narrowing the portal scope.Review the shared article’s assigned Division and its compatibility with each portal. Make a deliberate knowledge-organization decision instead of broadly opening unrelated Divisions.The portal looks unchanged after Save Changes.Determine whether you changed configuration, a design/page draft or language wording. Use the relevant surface’s save/publication controls and recheck the intended page and locale.Agents send a link to the wrong product portal.Inspect the link-generation route and the article’s Division default community. Previously pasted URLs and some search paths can use another address; verify the actual sharing workflow. Give the structure an operating owner Assign someone to maintain the audience matrix, shared Topics and portal tests when a product launches, an entitlement changes or a team reorganizes. Review article ownership so a shared answer receives one coordinated update rather than competing copies. Include customer-role assignment and excluded-reader tests in onboarding for administrators who manage portal access.For a weekly account review, note recurring reports such as “I can sign in but cannot find the maintenance guide” or “the software link opens equipment help.” Investigate the actual Contact, portal, Topic and article path. Those details lead to a useful correction; a broad request to “fix knowledge permissions” does not. Continue learning Configure customer portal settings and publicationOrganize Topics and article accessChoose the Division’s default knowledge portalConfigure DivisionsConfigure customer rolesCreate, review and publish an articleMaintain reusable knowledge with KCS Was this article helpful? Yes No Thank you for your feedback.