> For the complete documentation index, see [llms.txt](https://ticketking.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ticketking.xyz/docs/customization-and-branding/server-embed-color.md).

# The server embed color

The accent color used across every Ticket King embed in your server.

Settings, "Server Settings & Logging", **Main Embed Color**.

This is the accent stripe down the left side of every Ticket King embed in your server. It applies to panels, ticket welcome embeds, log embeds, and application embeds.

## Default

`#d4af37` (gold).

## Changing it

1. Click the colored swatch next to the field.
2. The color picker opens. Type a hex color code, or click on the color wheel.
3. The setting saves automatically.

<figure><img src="https://1268186137-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrnuG1qjzbOoh0efVpoK8%2Fuploads%2Fgit-blob-653d02617fabd4f30e30553eeeef00a4d5d9cdc4%2Fserver-embed-color-picker.png?alt=media" alt="Settings page → Main Embed Color section with the color picker popover open"><figcaption></figcaption></figure>

## How embeds use it

Most embeds use this color automatically:

* Panel embeds (when the panel's embed Color field is left blank). Set a color on a panel embed to override it there.
* The welcome embed inside new ticket channels.
* Open and close log embeds.
* Application embeds.

Error embeds use a fixed red instead, so the color you set here does not change them.

## Picking a good color

Match your server's existing color scheme. Most servers pick the color of their main branded role or their server icon's main color.

Avoid:

* **Pure black or pure white.** These are hard to see on Discord's themes.
* **Colors close to Discord's own interface.** Discord blurple (`#5865F2`) can blend in.

## Related

{% content-ref url="/pages/987R9qKqqc69cNg6Jakh" %}
[Edit the embed](https://ticketking.xyz/docs/panels/edit-the-embed.md)
{% endcontent-ref %}


---

# 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://ticketking.xyz/docs/customization-and-branding/server-embed-color.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.
