> For the complete documentation index, see [llms.txt](https://docs.harmony.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.harmony.io/settings/customizing-the-self-service-portal-and-ai-bot-branding.md).

# Customizing the Self-Service Portal and AI Bot Branding

Harmony lets you shape how both the self-service portal and the AI bot appear to your end users. From a single **Branding** section in Settings, you can align the portal's visual style with your organisation's identity and give the AI bot a name and avatar that feel native to your team's Slack or Microsoft Teams environment.

***

### Customising the Self-Service Portal

#### Accessing Portal Branding Settings

1. Open **Settings** from the main navigation.
2. Go to **Portal Preferences** (or the **Branding** section, depending on your view).
3. Look for the portal appearance options described below.

#### Available Options

**Accent Colour**

Set a portal accent colour to match your brand palette. This colour is applied to key interactive elements across the self-service portal, giving users a consistent branded experience.

To set the accent colour:

1. Click the colour picker or enter a hex value in the accent colour field.
2. Select your desired colour.
3. Save your changes - the new colour takes effect immediately for anyone accessing the portal.

**Background Image**

Upload a background image to personalise the visual experience of your self-service portal. This image appears behind the main portal interface, giving you further control over the look and feel.

To upload a background image:

1. Click **Upload** next to the background image option.
2. Select an image file from your device.
3. Save your changes - the image is applied instantly.

{% hint style="info" %}
Branding changes to the portal take effect immediately. No republishing or cache-clearing is required.
{% endhint %}

***

### Customising the AI Bot's Name and Avatar

You can personalise how the Harmony AI bot presents itself to your team in Slack or Microsoft Teams. These settings are managed from the **Branding** section of the Settings page.

#### Accessing Bot Branding Settings

1. Open **Settings** from the main navigation.
2. Select the **Branding** section.
3. Configure the options described below.

#### Available Options

**Custom Bot Name**

Rename the bot from the default "Harmony AI" to any name that fits your organisation or team culture.

To set a custom name:

1. Click the bot name field under **Branding**.
2. Clear the existing name and type your preferred bot name.
3. Save your changes.

**Custom Avatar**

Upload your own logo or image to replace the default bot avatar.

**Requirements for the avatar image:**

* Minimum size: **512 x 512 pixels**
* The image must be **square**

To upload a custom avatar:

1. Click **Upload** next to the avatar field.
2. Select an image file that meets the size and shape requirements.
3. Save your changes.

**Channel or Team Scoping**

Rather than applying customisations globally, you can target specific Slack channels or Microsoft Teams teams. This lets different groups see a differently branded bot if needed.

To apply a scoped customisation:

1. In the **Branding** section, locate the scope selector.
2. Choose the specific Slack channel or MS Teams team you want to target.
3. Configure the bot name and avatar for that scope.
4. Save your changes.

**Multiple Scopes**

You can configure different bot appearances for multiple channels or teams simultaneously.

To add another scope:

1. Click the **Add scope** button.
2. Select the additional channel or team.
3. Set the desired bot name and avatar for that scope.
4. Save your changes.

Each scope is managed independently, so you can maintain distinct branding configurations side by side.

{% hint style="info" %}
If no scope is specified, the bot name and avatar settings apply globally across all connected channels and teams.
{% endhint %}

***

### Summary of Branding Options

| Setting                 | Where to Configure            | Applies To                                |
| ----------------------- | ----------------------------- | ----------------------------------------- |
| Portal accent colour    | Settings - Portal Preferences | Self-service portal                       |
| Portal background image | Settings - Portal Preferences | Self-service portal                       |
| Bot name                | Settings - Branding           | Slack / MS Teams bot                      |
| Bot avatar              | Settings - Branding           | Slack / MS Teams bot                      |
| Channel or team scope   | Settings - Branding           | Specific Slack channels or MS Teams teams |


---

# 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.harmony.io/settings/customizing-the-self-service-portal-and-ai-bot-branding.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.
