Skip to content

Theming & appearance

The DioscHub chat widget’s appearance (colors, fonts, radius, light/dark mode, the launcher label) is configured per Assistant on the server and delivered with the widget. You author the theme once in the admin portal; every page that embeds that Assistant picks it up. There is no theme object you pass to diosc() on the host: colors, fonts and radius always come from the server.

What you do control from the host is the launcher’s position, which of the Assistant’s two color sets (light or dark) is active, and one CSS variable for stacking.

Position the launcher and stack it above your UI

Section titled “Position the launcher and stack it above your UI”

The one style hook you set from your own page is --diosc-fab-z, the launcher’s z-index — raise it to keep the launcher above your own overlays such as a sticky header or a cart drawer. The launcher corner is set on the Assistant’s appearance config in the admin portal:

diosc-chat {
/* Lift the launcher above a sticky header or cart drawer */
--diosc-fab-z: 1000;
}

The launcher corner is bottom-left or bottom-right, set on the Assistant. It is the one appearance value that is not gated. It stays in effect regardless of licensed tier, because it’s a layout concern, not branding.

  1. Open the Assistant in the admin portal and go to its appearance settings.

  2. Set the color set, corner radius, font, shadow, and launcher corner. You set a light and a dark color set; the active one is selected by the Assistant’s theme mode.

  3. Save. The next time a page loads the widget for that Assistant, it serves the new theme.

The Appearance tab: Identity, Layout (radius, font, shadow, border, launcher corner), and Colors controls on the left, with a live chat-widget preview on the right that updates as you edit.

The Appearance tab. The Live Preview on the right re-renders as you change colors, radius, font, and layout — and it toggles between the FAB, the open chatbot, and popups, in light or dark mode.

The Assistant’s theme mode is the default. If your page has its own theme switch, the host can choose which of the Assistant’s two color sets is active, and change it at any time:

<diosc-chat theme-mode="system"></diosc-chat>
// From your theme switch:
diosc('setThemeMode', 'dark'); // 'light' | 'dark' | 'system'
diosc('setThemeMode', null); // back to the Assistant's own setting
  • light or dark picks that color set.
  • system follows the visitor’s operating-system preference (prefers-color-scheme) and updates live when it changes.
  • Not set, or null: the Assistant’s theme mode decides, as before.

The widget re-themes in place (launcher, open panel and dialogs) without reconnecting. A setThemeMode call made before the widget loads is queued, and a call wins over the attribute.

Custom appearance is a licensed capability. Two entitlements govern what ships:

  • visualTheming: your custom colors, default theme mode (the host can still switch light/dark, see Follow your page’s light or dark mode), radius, font, shadow, and launcher label.
  • customBranding: the Assistant’s branding watermark, and whether the server delivers your custom styles to the widget at all.

On the FREE tier both are off. A FREE Assistant renders the default DioscHub theme and shows a non-removable Powered by DioscHub link in the widget; the custom styles aren’t even sent to the page. On PRO and ENTERPRISE, both are on: your authored theme is delivered and applied, and the attribution link is replaced by your own branding.

TierCustom themePowered by DioscHub
FREEDefault theme onlyShown, non-removable
PROYour authored themeReplaced by your branding
ENTERPRISEYour authored themeReplaced by your branding

Next: position the launcher and pass page context in Widget placement.