Skip to content
Help Center
Submit a request Sign in

Choose the default knowledge portal for a Division and verify shared article links

When your support team serves several product lines or brands, the address used to share knowledge matters. An equipment customer should reach the appropriate equipment support portal when an agent shares an equipment article. Default KB community lets you associate a Division with the portal address Core uses for that Division’s published articles in the Knowledge article view and list. This guide explains the complete setup, what happens when no default is selected, and how to check the experience as the intended customer.

At a glance

For: support operations administrators, knowledge owners and teams supporting multiple products or customer portals. Applies to: Supportbench Core.

Start here: Settings → Organization → Divisions → open a Division → Default KB community

Understand Division, community and article access  ·  Decide when a Division-specific portal is useful  ·  Prepare the portal and a safe test article  ·  Set or clear the Division’s default knowledge community  ·  Verify the generated link and the customer’s experience  ·  Worked B2B example: equipment and software support  ·  Resolve common problems  ·  Keep the association useful as the organization changes

Understand Division, community and article access

A Division organizes work and can participate in staff and customer access rules. A community is a configured customer portal. The label Default KB community connects the Division to a portal for the supported knowledge-link routes. The article’s assigned Division determines this association; the Division of a case linked to the article does not choose the destination.

QuestionWhat this setting does
Which portal address should the Knowledge article view/list use?Uses the selected community’s configured domain or Supportbench portal address for articles assigned to this exact Division.
Will the article become public?No. Publication, external eligibility and customer access remain separate.
Will a child Division use its parent’s selection?No. Configure each child Division that needs a specific portal.
Will every search result, template or previously sent link change?No. Other link-generation paths can use the account portal, and existing messages retain the URLs already sent.
Does this reorganize topics or copy articles?No. Maintain article placements and portal content separately.

A correct destination still needs an access check

A valid-looking article URL does not prove that a customer can read it. The destination portal applies its own access rules, including the article’s workflow status, external eligibility, Division scope, topic availability, customer roles and other restrictions.

Decide when a Division-specific portal is useful

  • Separate product lines: route an equipment article’s Knowledge link to the equipment portal while software articles use the software portal.
  • Several customer brands: keep the shared address consistent with the support experience that readers expect, after checking that the portal actually includes the article.
  • One support organization with several teams: define the portal once for each relevant Division instead of asking every agent to remember the correct domain when using the supported Knowledge links.
  • One shared portal: leaving No default community can be appropriate when the account portal is the intended destination. Do not introduce extra Divisions or portals solely to fill this optional field.

Choose the Division according to how the article should be maintained and accessed. Moving an article to another Division just to obtain a different URL can have access consequences beyond the link itself. Coordinate the decision with the knowledge owner.

Prepare the portal and a safe test article

  1. Confirm your role includes Administer divisions and gives you access to the Division you intend to edit. Ask the administrator responsible for roles if the editor is unavailable.
  2. Identify the intended active portal and its address. The community picker is filtered by active status and your allowed Division scope; different administrators may see different choices.
  3. Choose an existing published article assigned to this Division whose intended audience is already known. Avoid using a private customer record or restricted staff article to test anonymous access.
  4. Check that the destination portal is configured to offer the article and its topic to the intended reader. Prepare a permitted customer test account when sign-in is required.
  5. Record the current Default KB community value and any relevant existing article links. This gives you a clear rollback choice if the new destination is not suitable.

For portal setup, use the linked customer-portal configuration guide. This procedure changes a Division’s default association; it does not provision a domain, change DNS or create a portal.

Set or clear the Division’s default knowledge community

  1. Open Settings → Organization → Divisions. Find and open the exact Division used by the articles you want to share. When working with a hierarchy, confirm whether you opened the parent or a child.
  2. Find Default KB community in the Division editor.
  3. Choose the intended community from the list. To use the account fallback instead, select No default community. Leave unrelated routing, hierarchy and access settings unchanged unless those changes are part of your planned configuration.
  4. Select Save Changes. Resolve any displayed validation or permission message before continuing.
  5. Reopen the same Division and confirm the saved selection. A selected value before saving is not evidence that the configuration was stored.
  6. Repeat for each child or sibling Division that needs its own portal association. Saving a parent’s value does not populate its children.

For a new Division, choose New Division and complete the broader Division setup before testing. The Division configuration reference explains the other settings and their operational effects.

Verify the generated link and the customer’s experience

  1. Open Knowledge Base and locate the test article. Confirm the article itself belongs to the Division you changed; a linked case can belong to a different Division.
  2. Use the portal link offered by the Knowledge article view or list for the published article. Access to a portal link in the list depends on article-publishing permissions; ask an authorized knowledge administrator if it is unavailable.
  3. Inspect the destination address. It should use the selected community’s configured domain or Supportbench portal address, followed by the article’s stable ID route. If no Division default is selected or the community lookup returns no URL, the supported route falls back to the account community URL. A nonblank but unreachable host does not trigger an automatic fallback.
  4. Open the link as the intended reader. For public guidance, use a signed-out browser. For customer-restricted guidance, use an authorized customer account. Agent access alone is not a valid customer-access test.
  5. Confirm that the expected article title and complete procedure load, images and related links work, and the page offers the intended portal navigation. A login screen, home page or article-unavailable page is not a successful article check.
  6. Where restrictions matter, also confirm that an excluded reader cannot access the article. Record the article, Division, portal, audience and date of the check, then share the verified link with your team.

Check the actual sharing route

The separate agent article-search path can generate links using the account community URL directly. If a search result or another tool produces a different host, inspect that specific route instead of repeatedly changing the Division. Use the verified Knowledge article view/list link for this procedure.

Worked B2B example: equipment and software support

Suppose your organization has an Equipment Support Division and a child Division named Field Controllers. Equipment customers use an equipment portal, while software customers use the account’s general support portal. A maintenance article is assigned to Field Controllers.

  1. Selecting the equipment portal on Equipment Support alone does not change the child’s association. Open Field Controllers and select the equipment portal there as well.
  2. Open the maintenance article through Knowledge Base and inspect its portal link. The article’s Field Controllers assignment is the relevant one, even if a linked escalation case sits in a central escalation Division.
  3. Test the link with the intended customer account. If the customer reaches the correct portal but cannot read the article, investigate article and portal eligibility rather than changing the domain again.
  4. Tell agents which sharing route was verified. Review frequently used response templates separately, because an old URL pasted into a template or message is not rewritten by this setting.

The operational benefit is consistency: different contacts at the same customer receive the same maintained procedure through the intended support portal. Measure usefulness through successful access checks and fewer wrong-portal reports; the setting alone does not guarantee higher knowledge reuse.

Resolve common problems

ProblemLikely cause and corrective action
The community is missing from the picker.Check that it is active and available within your allowed Division scope. Ask the portal or role administrator to review the intended access; do not broaden access simply to make a name appear.
The link still uses the account portal.Reopen the Division to confirm the save, then check the article’s own Division. A child does not inherit the parent value. No default or a community lookup returning no URL falls back to the account portal. An unreachable nonblank host does not. Also confirm you are testing the Knowledge view/list route.
A link from search uses another host.Some search routes use the account portal directly. Compare the actual source of the link with the supported Knowledge view/list route; this difference is not proof that the Division save failed.
The correct portal opens, but the article does not.Check publication status, external eligibility, portal/Division scope, topic availability, customer roles, restricted tags and any applicable asset rules. Verify as the intended reader. The default community does not grant access.
A previously sent email still contains the old address.The message contains a previously generated URL. Review reusable templates and frequently shared resources separately. Plan any domain redirect with the portal owner; this Division field does not configure redirects.
The Save Changes action is unavailable or rejected.Check Administer divisions and access to the selected Division. Review the displayed error and reopen the saved record before assuming a network failure left it unchanged.
Agents expect a different portal for each linked case.The supported article link uses the article’s Division, not each linked case’s Division. Revisit the knowledge organization and sharing procedure rather than using case links as a portal-routing mechanism.

Keep the association useful as the organization changes

Include this setting in reviews when a product line moves, a portal domain changes, a Division is reorganized or customer access rules change. Check the affected parent and child Divisions individually. Maintain a small operating record with the Division, selected community, example article, expected audience and the last successful customer-access test.

Before clearing or changing a default, test the replacement destination and decide how agents should handle existing reusable links. After saving, repeat the Knowledge link and intended-reader checks. Keep the previous value available so an authorized administrator can restore the association if needed; restoring the association does not undo separately changed portal settings.

Was this article helpful?