Help center Core configuration Knowledge base Configure shared article styles and callouts Updated Thursday, October 29, 2026 · Marc Staine Shared styles make important guidance recognizable across the knowledge base. Callouts format a paragraph or block, while text styles emphasize selected words using a centrally managed appearance. Applies to: Supportbench Core. Location: Settings → Knowledge Base → Styles & Callouts. Access and available controls depend on your role and account capabilities. Before you begin You need editing access to Styles & Callouts. Review the impact of a shared style before saving.Identify whether the style is a Callout or Text style and which existing articles use it. Editing a shared style can change published articles immediately.Reopen the saved result and test a representative consuming workflow. A successful save alone does not verify every reader, assignment or rendered result. Configure and verify Open Settings → Knowledge Base → Styles & Callouts. Choose Create style or select an existing style.Enter Name, select Type and review Available in editor. This form has no Description, Division scope or parent-hierarchy control.Configure the offered icon, size, foreground/background/accent colors, spacing, text treatment and Display order using the field reference.Inspect the light Preview and any Contrast warning. The current form does not expose the separately named dark-color settings; do not invent a dark-preview workflow.Choose Save style and read the shared-style impact confirmation when editing. Reopen the style and verify its saved settings.Apply or inspect the style in a controlled article and check the intended saved reader. Review representative already-published articles that use a changed shared style. Settings reference Settings and actionsSettingWhat it controlsHow to chooseNameShared style name, up to 80 characters.Use a purpose such as Tip or Important rather than a color name.TypeCallout or Text style; locked after creation.Choose a callout for a complete paragraph and a text style for selected words.Available in editorMakes the style available for author selection.Retire unused choices without creating competing replacements unnecessarily.Icon / Icon sizeNone, Information, Tip, Warning or Important; 16, 20, 24, 32 or 40 pixels.Match the icon to the message and keep it proportionate to the text.Foreground / Background / Accent colorsControls readable text, surface and accent presentation.Check contrast in the live preview.Accent width / Padding / Corner radiusWidth 0–8, padding 0–32 and radius 0–24.Use consistent spacing across related callouts.Text weight / Underline / ItalicRegular, medium or semibold weight plus optional emphasis.Avoid combining every emphasis option.Display orderOrdering from 0 through 999.Place frequently used styles first.Preview / Contrast warningShows sample article rendering and flags contrast problems.Review before saving and check an actual article afterward. Behavior to knowChanging a shared style affects all articles using it, including published content. Read the impact confirmation.Dark-palette values can exist in stored configuration, but this form does not offer separate dark-color controls. Recommended use Use a small consistent set for meaningful content such as prerequisites, examples and consequential behavior.Keep text readable and understandable without color or an icon alone.Review shared usage before a visual change; a shared style is not an isolated per-article draft. Worked example: improve a shared Tip callout without degrading existing articles A knowledge team uses a shared Tip callout across installation procedures. Authors report that its pale text is difficult to read. Identify representative existing articles before opening that shared style; changing it can affect already-published content.In Styles & Callouts, open Tip. Review the existing Type, Foreground, Background, Accent, padding and text treatment. Keep a meaningful name and use color and the icon to support the message rather than convey essential instructions alone.Adjust the supported light appearance controls and inspect Preview and any Contrast warning. Do not look for a separate dark-color editor that this form does not expose. Choose Save style and review the impact confirmation before completing the shared change.Inspect the same representative articles in the agent reader and intended portal. Check text contrast, spacing, small-screen wrapping and whether the callout still reads clearly among numbered steps. Include an article already published before the style change.If an existing procedure becomes difficult to read, correct the shared style and recheck its users. Changing only one article’s wording will not fix a shared appearance problem. Keep any unfinished visual acceptance work recorded. Troubleshooting ProblemWhat to checkA style is missing from the editorCheck Available in editor, the saved Type and the editor context.An existing published article changed appearanceShared style updates can affect articles already using it. Review the change and representative readers.There are no dark-color controlsThe current form exposes the light appearance controls and preview only.Text is difficult to readReview foreground/background contrast, text weight and spacing rather than relying on the color alone.I cannot save a styleCheck editing access and the actual validation message. Related configuration Knowledge Base → Organize knowledge-base topics and accessKnowledge Base → Configure article templates and AI authoring guidanceKnowledge Base → Manage knowledge-base tags and audiencesKnowledge Base → Configure shared article styles and calloutsCreate, review, schedule, and publish a knowledge articleOrganize knowledge-base topics and access Was this article helpful? Yes No Thank you for your feedback.