> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/settings/configuration/brand-elements.md).

# Brand Elements

Set your public account name, account URL slug, logo, favicon, and default brand colors in Settings > Configuration > Brand to shape how donors see you.

**Brand elements** set how your organization appears to donors on Action Pages, receipts, notifications, reports, and browser tabs. You manage them in **Settings > Configuration > Brand**. This article covers each brand field and how to save your changes.

## Before You Begin

* To save brand settings, you need **Account Management: Edit Account Details and Configuration** permissions.
* To upload a logo or favicon, you also need **Action Pages: Edit** permissions.

## Update Your Brand

To update your brand:

1. Go to **Settings > Configuration > Brand**.
2. Update the fields you want to change. Each field is described below.
3. Click **Save brand**.

The **Brand preview** on the right shows how your changes will look.

## Public Account Name

Your **Public account name** appears on Action Pages, notifications, receipts, and reports. Use your full organization name or the version donors recognize best. It must be between 5 and 255 characters.

## Account URL Slug

Your **Account URL slug** appears after the Anedot domain in your Action Page links, for example `secure.anedot.com/your-url-slug`.

* Use letters, numbers, dashes, and underscores. Use dashes instead of spaces, for example `city-food-pantry`.
* Each slug must be unique across Anedot.

{% hint style="warning" %}
Changing your slug changes the web address of your Action Pages. Update any links you've shared, such as on your website, in emails, and in ads.
{% endhint %}

## Logo

Your **Logo** appears on Action Pages and receipts. Choose an image from your media library or upload a new file. You can use a different logo on a specific page in the Page Builder. See [Branding](/action-pages/page-builder/branding.md).

## Favicon

Your **Favicon** is the small icon in the browser tab on your Action Pages. Choose an image from your media library or upload a new file. A simplified version of your logo works well. Without a favicon, Anedot uses its default logo.

## Brand Colors

**Primary color** and **Secondary color** set the accent colors for your account's default Action Page design. Enter a hex code, for example `#1662F5`. The leading `#` is optional.

{% hint style="info" %}
If your account doesn't have a default Action Page design yet, brand colors can't be saved. Your other brand settings still save. Contact our Support team at <help@anedot.com> for help.
{% endhint %}

## Related Articles

* [Configuration](/settings/configuration.md)
* [Custom Domain & Email Branding](/settings/configuration/custom-domain-and-email-branding.md)
* [Branding](/action-pages/page-builder/branding.md)
* [Share an Action Page](/action-pages/action-page-basics/share-an-action-page.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.anedot.com/settings/configuration/brand-elements.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.