> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/brand-manager/manage-brands/edit-brand.md).
# Edit brand
{% hint style="success" %}
**Access Type**: Brand Manager - Editor
{% endhint %}
A brand is a centralized configuration of your brand identity and theme that is then disseminated to all widgets within a consent flow. In this article, we will cover how to edit an existing brand in your organization's Didomi account.
{% hint style="warning" %}
**Note**: Any saved brand edits will need to be reviewed and published from within the consent flow to be reflected in widgets on your websites and/or apps.
{% endhint %}
Click **Branding** in the left-hand panel.
Navigate to a brand profile card on the subsequent page and click the ellipsis in the upper right-hand corner of the card.
Select **Edit** from the drop-down menu.
Utilize the [brand editor](/brand-manager/brand-editor.md) to configure the details of the brand and click **Save** when finished.
---
# 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.didomi.io/brand-manager/manage-brands/edit-brand.md?ask=&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.
