> For the complete documentation index, see [llms.txt](https://docs.skyone.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skyone.cloud/english/admin/branding.md).

# Branding

In **Branding and visual identity**, you change the product's name, logos, colors, and links without changing its structure. Changes apply to every user in the environment.

The page is organized into the **Interface** and **Domain** tabs.

### Interface <a href="#interface" id="interface"></a>

#### Preview <a href="#preview" id="preview"></a>

The preview shows how your brand appears in the sidebar, on the home screen, and in emails Astro sends (welcome messages, alerts, and reports). The following actions are available at the top of the section:

* **Style with AI:** suggests a visual identity with AI assistance.
* **Restore defaults:** returns to Astro's original branding.
* **Save branding:** applies your changes for all users.

> Administrators and partners can change the branding. Changes appear for everyone once saved.

#### Names <a href="#names" id="names"></a>

Names appear in the browser tab title, on the sign-in screen, on the home page, and in interface text:

* **App name:** the product's full name (e.g., **Skyone Astro**).
* **Short product name:** the name used in short text (e.g., **Astro**).
* **Company:** the company name.
* **Legal name:** the company's registered legal name.

> Turn on **Hide the icon next to the name on the chat home screen** to show the name only.

#### Logos and icons <a href="#logos-and-icons" id="logos-and-icons"></a>

To change a logo or icon, follow these steps:

1. Find the item you want: **Logo (light background)**, **Logo (dark background)**, **Symbol (light background)**, **Symbol (dark background)**, or **Favicon**.
2. Enter the image address (`https://...` or `/path`) or click **Upload file**.
3. Check the result in the preview and click **Save branding**.

> SVG, PNG, JPEG, WebP, and ICO files up to 2 MB are supported. Dark background versions appear in the sidebar; without them, Astro uses the light version.

#### Colors <a href="#colors" id="colors"></a>

Enter colors in hexadecimal format (e.g., **#0018EE**):

* **Primary color:** buttons, links, and highlights.
* **Deep color:** dark backgrounds and headings.
* **Accent color:** accents.

#### Links <a href="#links" id="links"></a>

Enter your company's **Website** and **Documentation** addresses.

### Domain <a href="#domain" id="domain"></a>

In the **Domain** tab, you set up a custom domain for accessing Astro (e.g., **ai.yourcompany.com**).

#### Configure DNS <a href="#configure-dns" id="configure-dns"></a>

Before you register the domain, follow these steps with your DNS provider:

1. Open your DNS provider's management console (e.g., Cloudflare, GoDaddy, Namecheap).
2. Create an **A** record with the subdomain you want as the name (e.g., **ai**) and the IP address shown in the **Domain** tab as the value.
3. Use a low TTL (300) so future changes propagate quickly.
4. Save and wait for propagation.

> Propagation usually takes a few minutes, but it can take 24 to 48 hours.

> Root domains with no subdomain (e.g., **yourcompany.com**) work the same way: just create the A record at the root of the domain.

#### Register the domain <a href="#register-the-domain" id="register-the-domain"></a>

To register your custom domain, follow these steps:

1. In the **Domain** field, enter the address you configured in DNS.
2. Click **Register domain**.
3. Click verify to confirm the setup.


---

# 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.skyone.cloud/english/admin/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.
