Skip to content
Help Center
Submit a request Sign in

Manage knowledge-base tags and audiences

Knowledge-base tags help organize and find articles, support topic rules and provide reusable authoring labels. Their audience and lifecycle settings let administrators keep the vocabulary useful without exposing internal terminology.

Applies to: Supportbench Core. Location: Settings → Knowledge Base → Tags. Access and available controls depend on your role and account capabilities.

Before you begin

  • Management requires Manage knowledge-base tags. Using allowed existing tags while authoring an article is a separate capability.
  • Search for an existing term and review usage before renaming, merging or deleting. Tag Audience controls can affect labels visible on customer-readable articles.
  • Review the saved result and a controlled example in the consuming workflow. Configuration, customer access and actual delivery or processing are separate checks.

Configure and verify

  1. Open Settings → Knowledge Base → Tags. Use Search to inspect the existing catalog and usage before creating a new term.
  2. Choose Create, enter the reviewed tag and use Apply in the dialog. Recheck the resulting row. This screen has no generic Name/Description detail form.
  3. For a row change, use its Rename, Merge, Retire or Restore action, review the dialog and choose Apply. Inspect the affected usages before consequential changes.
  4. Where enabled, change Audience through the row’s inline selector. This saves immediately; there is no single Save Changes action for the entire tag catalog.
  5. Before merging, review the destination tag’s Audience. Articles using the merged tag inherit the destination tag’s audience behavior, so External or Both can make the label visible on customer-readable articles.
  6. Choose Delete on the intended row, inspect the dialog’s impact and confirmation, then choose Apply only for the intended deletion. The operation saves immediately after Apply; it does not wait for a separate Save Changes.
  7. Verify a representative article in the agent reader and as the intended customer. A tag-audience change is distinct from an article access grant; check both rather than assuming the tag makes a restricted article public.

Settings reference

Settings and actions

SettingWhat it controlsHow to choose
Search / CreateFinds tags or creates a new name, up to 100 characters without commas.Search first to avoid duplicate concepts.
Restrict tag creation and managementWhen enabled, only agents with Manage knowledge-base tags can create/manage tags; article editors can still use existing tags.Enable when a curated vocabulary is important. The setting does not grant permissions.
AudienceInternal, External or Both.Choose whether the tag may appear on readable customer articles or remain internal.
RenameChanges the shared tag name, subject to impact and workflow-reference checks.Review all affected article, topic-rule and template references.
MergeMoves usage into an existing active target tag.Choose the canonical term and inspect the impact before confirming.
Retire / RestoreRetirement keeps existing assignments but prevents new assignment; restore makes it available again.Retire obsolete vocabulary when history should remain intact.
DeleteAllowed only when relevant usage counts are zero.Check article, topic-rule, workflow and template counts first.
Usage countsShows where a tag participates in articles, topic rules, workflows or templates.Use these counts to plan a vocabulary change.

Behavior to know

  • Rename and merge can be blocked by workflow references. Resolve those dependencies deliberately.
  • External and Both tags can be customer-visible on articles the customer can read.
  • A merge adopts the destination tag’s Audience for affected article tag usage. Review External/Both before confirming; tag visibility does not independently authorize reading restricted article content.

Recommended use

  • Maintain a small recognizable vocabulary and review existing usage before creating synonyms.
  • Choose a destination tag and its audience deliberately before a merge.
  • Use Retire/Restore for the supported tag lifecycle instead of looking for an Active checkbox.

Worked example: consolidate a product tag without exposing internal labels

  1. A controller-support team wants one recognizable tag for its customer setup articles. Search for controller-setup and existing spellings first; this is an illustrative label, not a required built-in tag.
  2. Choose the existing canonical tag or create it through Create and Apply. If the label is appropriate on customer-readable articles, choose External in Audience when that control is available. Keep diagnostic-only terminology on an Internal tag. Audience changes save immediately.
  3. Inspect usage before merging an old spelling: articles, topic rules, templates and workflows can depend on it. Confirm the destination tag and its Audience before Apply; the merge adopts that destination audience behavior. Resolve a blocking workflow reference deliberately rather than deleting the tag to avoid the check.
  4. Read a representative article as an agent and as an intended customer. Confirm that the appropriate product label appears and the internal diagnostic label does not. Also confirm that article access itself is still correct: an External tag is not permission to read an internal article.
  5. If the old term still has a legitimate distinct meaning, keep it separate instead of merging. If it is obsolete but history matters, consider Retire and verify that existing assignments remain while new assignment is prevented.

Troubleshooting

ProblemWhat to check
I can use tags but cannot manage the catalogCheck Manage knowledge-base tags; authoring use and catalog management are separate.
Audience editing is unavailableThe required account setup and search indexing may still be pending. Follow the displayed availability state rather than assuming a save succeeded.
A merged tag appears to customersInspect the destination tag’s Audience and the articles where the label is used.
There is no Save Changes buttonExpected. Dialog operations use Apply; inline Audience and Delete have their own immediate save behavior.
A retired term is absent from normal choice listsReview its Retire/Restore state and intended usage before restoring it.
  • 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?