> ## Documentation Index
> Fetch the complete documentation index at: https://docs.raum.am/llms.txt
> Use this file to discover all available pages before exploring further.

# Widgets

Open **Chatbot → Widgets** to configure the versioned website widget your visitors actually see.

A widget has a **draft** configuration and, after publication, an immutable **published version**.

## Draft versus Published

Editing a widget changes the draft only.

Your live website does not change until you click **Publish**.

This lets you prepare several changes together, preview them, and release one coherent version rather than turning production into a sequence of half-saved settings.

> [!WARNING]
>
> Publish is blocked while the draft has unsaved changes. Save the draft first, then publish the saved version.

## The five widget tabs

The current widget editor contains:

1. **Appearance**
2. **Languages**
3. **Experience & CSAT**
4. **Installation**
5. **Preview**

Each tab edits a different part of the same draft.

## Organization defaults

The Widgets page also contains organization-level defaults.

Current controls include:

* **Show Built with RAUM by default**
* **Conversation retention days**
* **Request retention days**
* **Action-audit retention days**

Current supported ranges are:

| Setting | Range |
| - | -: |
| Conversation retention | 7–365 days |
| Request retention | 30–730 days |
| Action-audit retention | 30–730 days |

New widgets can inherit the organization branding preference.

Conversation content, longer-lived human-support Requests, and public-action audit records intentionally have separate retention controls.

[Retention and deletion →](https://docs.raum.am/chatbot/retention.md)

## Appearance

Configure:

* widget name;
* primary and surface colors;
* corner radius;
* launcher position;
* launcher shape;
* desktop window size;
* light/dark/automatic theme;
* mobile full-screen or bottom-sheet behavior;
* header logo;
* assistant avatar; and
* whether the widget inherits the organization branding setting.

[Appearance →](https://docs.raum.am/chatbot/widget-appearance.md)

## Languages

Choose which centrally published RAUM interface languages the widget enables.

English is always available.

You can also configure:

* default locale; and
* an organization-specific welcome message per enabled language.

Leaving a welcome message blank falls back to RAUM's published copy for that locale.

[Languages →](https://docs.raum.am/chatbot/widget-languages.md)

## Experience & CSAT

Configure customer-facing behavior including:

* visitor attachments;
* allowed upload types;
* maximum upload size;
* forms available to this widget;
* Shared Knowledge Collections;
* CSAT enabled/disabled;
* CSAT style;
* optional comment; and
* sampling percentage.

[Experience & CSAT →](https://docs.raum.am/chatbot/widget-experience.md)

## Installation

Configure exact allowed origins and obtain installation examples for:

* plain HTML;
* JavaScript / npm;
* React;
* Next.js;
* Node/Express-hosted pages; and
* Android/iOS WebViews.

The publishable key is browser-visible and origin-bound. It is not an organization API token.

[Installation →](https://docs.raum.am/chatbot/installation.md)

## Preview

Preview renders the same published widget stylesheet used by the visitor runtime.

You can inspect:

* open and closed launcher states;
* desktop and mobile layouts;
* current draft colors;
* radius/theme/layout;
* artwork;
* localization; and
* branding.

Preview does **not** create a real chat session or send messages to the Assistant.

[Preview →](https://docs.raum.am/chatbot/widget-preview.md)

## Archive a widget

Archiving is stronger than merely editing a draft.

Archiving a widget stops public chat for that widget and starts the product's dependent-data cleanup/deletion lifecycle.

Do not use Archive as a styling toggle. Use it when the deployment itself should stop serving visitors.

## Recommended publish workflow

1. Edit the draft.
2. Save it.
3. Review Preview in desktop and mobile modes.
4. Verify enabled languages.
5. Verify forms and Collections.
6. Verify attachment/CSAT settings.
7. Check exact allowed origins.
8. Run Chatbot Simulation.
9. Publish.
10. Test the published widget from a real allowed website origin.

> **[Channels](https://docs.raum.am/chatbot/channels.md)**
>
> Configure the web-channel security and handoff boundary behind widgets.

> **[Install](https://docs.raum.am/chatbot/installation.md)**
>
> Get the browser loader or framework integration and required CSP directives.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.