> For the complete documentation index, see [llms.txt](https://docs-conversational-ai.syntphony.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-conversational-ai.syntphony.com/syntphony-messaging-portal/messaging-tools/administration/source-theme.md).

# Source Theme

## Purpose

Configure the visual style and behavior of WebChat widgets used by your sources.

## Who this is for

Administrators and supervisors who manage WebChat branding and embed scripts.

## Prerequisites

* Administrative permissions in the Messaging Portal.
* At least one WebChat source will use the theme (configured in [Source Configuration](/syntphony-messaging-portal/messaging-tools/administration/source-configuration.md)).

## Assigning Source Theme to WebChat sources

To apply a Source Theme to your WebChat channels, assign the configured theme in **Source Configuration**. The selected visual style is reflected in all web widget interactions for that source.

* When creating or editing a WebChat source in [Source Configuration](/syntphony-messaging-portal/messaging-tools/administration/source-configuration.md), open the theme or widget appearance settings.
* Choose the desired Source Theme from the available options.
* Save your changes so conversations initiated via the WebChat channel use the configured theme.

## Steps

1. Open **Administration** and go to **Source Theme**.
2. Create or edit a theme configuration.
3. Set branding, colors, and display options (logo, primary colors, widget position, and other exposed fields).
4. Preview the widget and publish changes.
5. Copy the generated embed script when you need to install the widget on a website.
6. In [Source Configuration](/syntphony-messaging-portal/messaging-tools/administration/source-configuration.md), assign this theme to the relevant WebChat source and save.

<figure><img src="https://3261478287-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXHkoH2WwcemdqskPI0KI%2Fuploads%2F8DXPXp33W13blytUQT14%2Fimage.png?alt=media&amp;token=64558180-e98d-46c9-94c9-513a07531e67" alt=""><figcaption><p>Source theme configuration</p></figcaption></figure>

## Validation

* The preview reflects your branding choices before publish.
* The WebChat source shows the assigned theme after save.
* The widget script from Source Configuration matches the published theme.

## Expected outcome

The widget matches brand guidelines, can be embedded in owned channels, and is linked to the correct WebChat sources.

## Related pages

* [Administration](/syntphony-messaging-portal/messaging-tools/administration.md)
* [Source Configuration](/syntphony-messaging-portal/messaging-tools/administration/source-configuration.md)
* [Settings](/syntphony-messaging-portal/messaging-tools/administration/settings.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs-conversational-ai.syntphony.com/syntphony-messaging-portal/messaging-tools/administration/source-theme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.