> For the complete documentation index, see [llms.txt](https://support.emsigner.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emsigner.com/apis/embedded-signing/getting-started/setting-up-your-brand-and-colors.md).

# Setting up your brand and colors

emSigner allows you to co-brand the signing experience for your users with your brand color and company logo.

You can subscribe to an API plan using the following steps:

1. To subscribe, please visit emSigner.com API plans page.
2. Navigate to settings (under your name, on the top right of the dashboard).
3. Go to co-branding in the Admin Section of the Settings page
4. Go ahead and change the brand colors, add a company logo as shown in the screen below:

<figure><img src="/files/kQPTUqiSolc7Hcln0LH7" alt=""><figcaption></figcaption></figure>

**Note:** Changing the brand color and logo will also apply these to the email templates used by the application.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.emsigner.com/apis/embedded-signing/getting-started/setting-up-your-brand-and-colors.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.