Skip to content
Help Center
Submit a request Sign in

Organize knowledge-base topics and access

Knowledge-base topics group related articles into a browseable library. Use them to help a customer find a task, help an agent find a procedure, and give a knowledge owner a maintainable area of responsibility. Older Supportbench screens and articles may call these groupings containers; current Core calls them Topics. A topic organizes articles but does not publish them or automatically grant customers access.

Applies to: Supportbench Core. Location: Settings → Knowledge Base → Topics. Creating and editing topics requires Administer article topics and access to the affected Division. The choices available to an administrator can differ from those visible to another role.

Before you begin

  • Decide who needs the topic and what they should accomplish. For B2B customers, Account onboarding, Troubleshooting and Product administration are usually clearer than internal department names. These are examples, not required topic names.
  • Search existing topics before creating another. Prefer a short, understandable hierarchy; separate genuinely different tasks rather than duplicating the same article under slightly different labels.
  • Identify the articles to include and their current publication, external/internal visibility, language, customer-role and restricted-tag rules. A topic change is not permission to expose their contents.
  • Check the administrator’s Administer article topics permission and Division scope. All divisions is available only when the administrator’s Division scope permits it.
  • Choose automatic tag grouping, independent article placement where enabled, or an intentional combination. Agree a vocabulary before adding broad tags that could include unrelated articles.
  • Before changing an existing parent, inspect its descendants. Division, role selections and deactivation can affect the child branch; this is more consequential than changing one navigation label.

Configure and verify

  1. Open Settings, then Knowledge Base → Topics. Search the existing list and open the intended topic, or choose Create topic. The new-item editor is headed Create topic.
  2. In Content, enter the English/default Name and Description. The name is required and should describe a task or subject the reader recognizes. Use the description to explain the topic’s scope to the people maintaining it.
  3. Use Add translation for the languages your portal actually supports. Enter meaningful localized names rather than assuming an English label is sufficient in every portal language.
  4. Review Article Tags. Any one matching article tag can include an article automatically. Select only the agreed tags; do not enter several tags expecting an article to match all of them. Where independent placements are enabled, you can leave topic tags empty and manage article placement directly.
  5. Open Organization. Choose Parent topic for a child, or leave the topic at the root. A selected parent supplies the child’s Division. For a root, choose the permitted Division or All divisions when available.
  6. Choose Display order from 0 through 25. Lower values appear earlier among siblings of the same active state. New topics start at 0; use a deliberate sequence for common customer tasks.
  7. Open Access & Visibility. Review Active topic, Public portal topic and the Agent Roles selector. A new topic starts active and nonpublic. Public portal topic is the portal-browse setting; it is separate from whether an agent can use the topic in the Knowledge Base workspace.
  8. Review role selections with the person responsible for portal access. The control is labeled Agent Roles, but the stored topic role restriction also participates in customer-portal audience checks. Empty means no stored topic role restriction; it does not bypass article or portal restrictions. Changes to the selected roles cascade to child topics.
  9. Optionally use Appearance to choose Upload Icon for an approved JPG, JPEG, PNG or GIF up to 25,600 bytes, or Clear Icon to remove the existing custom icon. Choose an icon that is understandable at a small size and avoid putting essential instructions in it.
  10. Choose Save Changes. Look for Knowledge base topic saved and the refreshed list. Reopen the topic and confirm the name, parent, Division, tags, order and access settings.
  11. Verify the intended articles in the agent Knowledge Base and the appropriate customer portal. Use the checklist below, including an excluded or signed-out reader where relevant. A successful configuration save alone does not prove that the customer can find or open every article.

Arrange topics and articles without changing their legacy priority

Use Arrange content when readers should encounter procedures in a deliberate sequence, such as onboarding before advanced troubleshooting. An arrangement is an article's position inside one topic, or a subtopic's position beside its siblings. It does not change the article itself. The same article can appear first in Onboarding and later in Troubleshooting.

Before you start

Your Core release must include Arrange content and its optional storage must be available. You need Arrange knowledge base content and access to the topic’s Division. When the separate permission is unavailable or still inherited, existing Edit topics access applies; an explicit denial blocks arrangement even when Edit topics is enabled. The organizer checks access again when you save. It does not grant article editing, publishing or pinning permissions. If it reports that a database update is needed, ask your Supportbench administrator to complete the release prerequisites; existing browsing continues to work.

Each topic has independent Subtopics and Articles settings. At All topics, the list controls top-level topics. Custom order does not flow down into child topics. A topic's arrangement is shared across Core communities and languages using that topic. Legacy views retain their existing order.

Use the breadcrumb or the highlighted topic navigation to move through the hierarchy. On a narrow screen, choose Browse topics to show or hide navigation. Find a subtopic searches the current topic's complete subtopic list; at All topics, use Find a topic. Opening another topic still asks you to discard unsaved changes. The publication and visibility badges identify each entry; the footer shows Saved order, Unsaved changes or Review required.

Move article 80 to the top in one action

  1. Open Knowledge Base and select Arrange content. From an existing topic's editor, use Arrange this topic’s content to start at that topic.
  2. Select the topic in the left navigation. Use the breadcrumb to return to its parent or All topics. On narrow screens, use the breadcrumb and Open topic actions in Subtopics.
  3. In Articles, change Existing order to Custom order. The first arrangement starts from the normal browse sequence.
  4. Find the article. Each page contains up to 100 available entries. For a later page, choose Find in this list (the magnifying-glass button), enter its title or ID, and choose Go to position. This locates the entry in the full arrangement; it does not replace the arrangement with search results.
  5. Open the article's Move menu and choose Move to top of unpinned articles (or Move to top of pinned articles for a pinned entry). For example, move “Connect your first integration” from position 80 to the beginning of Other articles. The other articles move around it automatically; you do not edit their priority numbers.
  6. Review the new position, then choose Save order. Until the save succeeds, the reader-facing sequence remains unchanged.
  7. Reload the same topic in the agent Knowledge Base and a Core reader view. Confirm the article appears in the expected group. Clear any explicit grid column sort before evaluating normal browse order.

Place an item between specific neighbors

  1. Enable Custom order for the relevant list.
  2. Drag the item's handle to another row. The insertion line shows whether it will land before or after that row. Dragging changes position within this list; it does not change the topic hierarchy or article membership.
  3. For a destination on another page, open Move and choose Before / after…. Search by title or ID, then choose Move before or Move after beside the destination. Search returns up to 30 matching destinations in the same pin group; narrow the search if necessary.
  4. Open Move and choose Move to bottom of unpinned articles (or the corresponding pinned-group command) to reach the end of the entire group, including later pages.
  5. Choose Save order when the staged sequence is correct.

Keyboard users can Tab to a move handle and press Enter to choose a destination. Alt+Home moves to the top of the group; Alt+End moves to its bottom. Alt+Up and Alt+Down move relative to adjacent rows on the displayed page. For a neighbor on another page, use the searchable destination picker. Position changes are announced. Touch users can drag the handle or open its Move menu. In the menu, use Up/Down or Home/End to choose an action, Enter to activate it, and Escape to close it and return to the Move button.

Understand pinned and unpublished articles

Pinned articles remain above Other articles. Top and Bottom act within the item's current group. You cannot drag across groups or change pinning in this workspace. Use the existing article pin action if you have the required permission. When an article is later pinned or unpinned, it keeps its saved placement value and moves to the corresponding group.

Status and visibility badges distinguish published articles, unpublished articles and division restrictions. Arranging an existing published article with an unpublished revision does not require opening, editing or publishing that revision. Saving creates no article revision and sends no subscription notification. The organizer shows only entries you can access and preserves other entries on the server.

Undo, discard, disable and reset

ActionWhen to use itResult
UndoThe last staged move or setting change was incorrect.Restores the previous unsaved draft. It does not undo an earlier successful save.
DiscardAbandon the unsaved draft.Reloads the saved arrangement after confirmation.
Existing order, then Save orderRestore the original sorting rules.Stops using custom positions while retaining the saved arrangement for reuse.
Custom order, then Save orderResume a previous arrangement.Reuses saved positions. New entries append within their group using normal browse order.
Open the list options (three dots), choose Reset custom arrangement, then Save orderRebuild current positions from today's existing order.Rebuilds the draft from the current baseline. Reset does not itself switch Existing order to Custom order; choose the desired mode before saving.

Moving to another topic or closing the organizer prompts about unsaved changes. Save at most 500 pending moves at a time. One save commits the selected topic's changed Subtopics and Articles settings together.

A B2B onboarding example

Acme's Getting started topic contains 180 procedures. Keep “Service availability” pinned so it always precedes Other articles. Move “Create your administrator account” to the top of Other articles, place “Connect your identity provider” immediately after it, and move “Advanced audit exports” near the bottom. Make all three placements in one draft, then save once. An article also listed in Security retains Security's separate arrangement. To organize child topics, select Custom order in Subtopics and arrange them independently; their own article lists keep their previous settings.

Verify and recover

If Save reports a conflict, another administrator, a membership change, a pin change or a permission change may have made the draft stale. The draft remains visible and is not silently written over newer work. Review the intended moves, choose Discard to load the current saved order, then reapply the necessary moves. If access was removed, ask an authorized topic administrator to continue. If a request fails, do not assume it saved: reload and inspect the current order before repeating the action.

If the reader shows a different sequence, verify that the list is set to Custom order, the save succeeded, you are viewing the same topic in Core, and the article belongs to the expected pin group. Search relevance, AI retrieval, latest/popular lists and explicit grid column sorts do not use this arrangement. A saved Liquid theme that explicitly sorts a collection also controls its own presentation. Arrangement does not change audience access or publication, so a customer may see fewer articles than an administrator.

Positions survive tag-driven membership reconstruction and removal followed by relinking. Reset intentionally rebuilds the current arrangement. See the Knowledge Base browsing guide to distinguish browsing from searching, and the Liquid topic navigation reference when maintaining a custom portal theme.

Open Arrange content and assign access

In Settings, select Knowledge Base, then Arrange content. Choose Arrange content to open the workspace at All topics. Select a topic, choose Custom order for Articles or Subtopics, move an item, and choose Save order. Existing order keeps the original sorting rules.

Under Organization, open Roles and the relevant role. In Knowledge Base, use Arrange knowledge base content to grant or remove arrangement access separately from Edit topics. This permission does not allow article editing, publishing, pinning or subscriber management. Existing topic editors retain access when the new permission has not been set. Saving an unchanged permission preserves that inheritance; changing the checkbox sets an explicit grant or denial. An explicit denial blocks arrangement even if Edit topics remains enabled.

If the permission is missing, the optional database update has not been applied. Existing topic-editor access continues. If the section is missing, check Knowledge Base availability and the role permission. After a permission change, reopen Settings; a stale open organizer cannot bypass a fresh save check.

Settings reference

Content and article membership

SettingWhat it controlsHow to choose
Name / DescriptionEnglish/default Name is required, up to 50 characters; Description is up to 1,000 characters.Use the customer’s task language and explain the boundaries of the topic.
Add translationAdds localized topic names and descriptions. A new topic starts with English. Removing a locale removes it from the saved translation set.Review the portal in each supported language; a missing localization can affect discovery.
Article TagsAutomatic membership uses any matching article tag. Combined topic tags are limited to 250 characters. Empty tags are allowed when independent placement is enabled.Use a focused vocabulary. Tags group content; they do not authorize access.
Saved placement and tag-derived placementArticles can be included by saved placement and, where configured, by matching topic tags. Changing a topic’s tags can rebuild matching membership.If an article remains after removing one placement, inspect its remaining placement or matching tags before assuming the save failed.

Organization and inherited effects

SettingWhat it controlsHow to choose
Parent topicNests the topic below a permitted parent. Self/descendant parenting is not allowed. A child inherits its parent’s Division.Choose the root’s Division first and inspect the intended branch before moving a topic.
DivisionScopes the topic. All divisions is offered only to an unrestricted administrator. Changing a root Division cascades to descendants.Review both customer-portal scope and the administrators/agents who need to maintain or use the branch.
Display order0–25; default 0. Lower values sort first among siblings with the same active state.Keep the most useful entry points prominent without relying on an arbitrary alphabetical arrangement.

Access, visibility and supporting controls

SettingWhat it controlsHow to choose
Active topicDefault on for a new topic. Deactivating a parent also deactivates its descendants.Check the whole branch before deactivation; inspect individual descendants when restoring availability.
Public portal topicDefault off. Makes the topic eligible for public portal navigation, subject to the portal’s topic selection and audience rules.Review included articles and portal access before enabling it. It does not make an internal article external.
Agent RolesExact editor label for selected role IDs. Empty means no stored topic role restriction; selected roles are also evaluated in the portal audience path and cascade to descendants.Verify with representative customer identities. Do not assume the label means this setting only affects staff navigation.
Icon / Upload Icon / Clear IconOptional topic icon. The Icon field is read-only; upload JPG, JPEG, PNG or GIF up to 25,600 bytes, or clear the existing custom icon.Use approved imagery and check the result at the size shown in the portal.
SubscribersSelect a portal, search Contacts and manage the subscribed list. Subscription actions are saved independently of the main topic form.A subscription is not an access grant. Manage the intended contact and portal deliberately; do not assume Cancel reverses an already completed subscription action.
AuditShows creation and modification information.Use this to investigate a recent change together with the saved topic fields and affected branch.

Behavior to know

  • Portal discovery has several gates: the topic must be active and public, included by the portal configuration, within the applicable Division and role scope, and available for the relevant locale. A visible parent does not prove that every child is eligible.
  • The article has its own gates: Published workflow status, external eligibility, an eligible topic link, and the applicable article/customer-role/restricted-tag or other visibility rules. Verify the actual intended customer view, not only an administrator’s preview.
  • The agent Knowledge Base tree uses active topics and authorized Division scope; it can include nonpublic topics. Public portal topic controls portal eligibility rather than making a topic disappear from every agent workspace.
  • Turning a parent inactive deactivates descendants. Saving parent role selections also applies them to children, and root Division changes cascade down the branch. Review these changes as a branch update.
  • Moving or renaming a topic does not replace an article’s canonical URL. Preserve useful article identities and test existing links separately from the new navigation.

Recommended use

  • Organize around what readers are trying to do. A customer facing a failed SSO setup is more likely to look under Account onboarding → SSO than an internal team acronym.
  • Keep configuration references distinct from everyday procedures, and link them. An agent needs to work the customer’s issue; an administrator needs to know which settings control the workflow.
  • Use precise tags for automatic grouping. A broad tag such as support may unintentionally pull almost every article into a specialist topic. Inspect the result after saving a tag rule.
  • Give each topic a clear knowledge owner and review its empty, duplicated and outdated entries during regular knowledge maintenance. Topic ownership is an operational responsibility; naming a topic does not automatically assign case or article ownership.
  • Make an access change only after checking the actual contents and intended audience. Keeping a topic nonpublic is useful for organization, but article visibility and portal rules remain necessary controls.
  • Avoid creating an elaborate hierarchy before there is useful content. A few complete, recognizable paths are easier to maintain than many nearly empty categories.

Worked example: build a B2B account-onboarding path

  1. The support team repeatedly answers SSO setup and provisioning questions for different Contacts at the same customer organizations. It wants a public path that customers can browse and an internal runbook path for staff investigation.
  2. Review existing topics and choose Account onboarding as the root, with SSO and Provisioning as children. Set the intended Division on the root before choosing it as the children’s parent.
  3. Create each topic through Create topic. Add concise descriptions, meaningful translations and deliberate display orders. Use focused tags such as onboarding-sso and onboarding-provisioning on the appropriate articles if automatic grouping is intended.
  4. Check that the customer procedures are published and external and that their article restrictions suit the intended customer audience. Keep staff-only diagnostic material under its intended internal article restrictions.
  5. Enable Public portal topic only for the reviewed customer topics and ensure the target portal includes them. Save Changes and confirm the actual resulting hierarchy.
  6. Open the portal as an intended customer and browse from Account onboarding to SSO. Open a procedure, follow its prerequisite link and confirm that the article is relevant to that customer’s setup.
  7. Check signed-out or excluded access where the knowledge should be restricted. If an article is absent or too broadly visible, inspect the specific topic and article gates rather than widening several settings at once.
  8. Finally, have an agent locate the same customer procedure and the internal runbook in the Knowledge Base workspace. Record the expected difference so later editors do not mistake intentional restrictions for broken navigation.

Troubleshooting

ProblemWhat to check
A customer cannot see the topicCheck Active topic, Public portal topic, the portal’s included topics, Division scope, role eligibility and selected language. Compare an intended customer session with the administrator’s view.
The topic is visible but an article is missingCheck the article’s published status, external visibility, topic placement/tag match and article audience restrictions. Publishing a topic does not publish an article.
An internal topic still appears for an agentThat can be expected. The agent tree uses active topic and Division access; the public switch controls portal eligibility.
An article appears in an unexpected topicInspect matching Article Tags as well as saved placement. The tag rule matches any selected tag; remove or refine the unintended grouping only after checking other affected articles.
The Division changes after choosing a parentA child inherits its parent’s Division. Review the parent or choose an appropriate root instead of repeatedly forcing a conflicting child value.
A parent, Division or All divisions is unavailableCheck the administrator’s Division scope and the permitted hierarchy. Self/descendant parenting is blocked; scoped administrators cannot use every global option.
Child topics changed after editing their parentParent Division, role and deactivation changes have cascading effects. Inspect the whole branch and restore only the intended reviewed settings.
A translation does not appearConfirm the translation was saved and that the portal is using that language. Review the locale-specific name and the article’s language/visibility separately.
Save is rejectedRead the specific validation message. Check required English Name, 50/1,000-character name/description limits, tag limits, order 0–25, parent validity and Division permission.
A subscribed Contact cannot open an articleSubscription controls delivery preferences, not authorization. Check that Contact’s portal and article audience rules; do not subscribe another identity as an access workaround.
  • Knowledge Base → Organize knowledge-base topics and access
  • Knowledge Base → Configure article templates and AI authoring guidance
  • Knowledge Base → Manage knowledge-base tags and audiences
  • Knowledge Base → Configure shared article styles and callouts

Was this article helpful?