> 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/widgets/widget-editor.md).

# Widget editor

{% hint style="success" %}
**Access Type**: Widgets - Editor
{% endhint %}

Widgets are configurable UI templates that help your organization collect and manage end-user consent and privacy preferences across your applications. Utilizing the component library your organization can create fully customized and modular interfaces that can be deployed across multiple consent flows.

Widgets can be customized with different texts, buttons, and behaviors to match your specific use cases like age verification (underage) or Global Privacy Control (GPC) compliance.&#x20;

Access the editor for a widget by clicking **Widgets** on the left-hand panel and selecting the **Edit** icon inline with the widget name

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FLNskAXYz2CSiH6tC7SwI%2FScreenshot%202026-02-17%20at%202.43.35%E2%80%AFPM.png?alt=media&amp;token=7fb2e209-808f-49c8-a655-ea2486dd1cda" alt="" width="563"><figcaption></figcaption></figure>

Review the table below on the available resources Didomi provides regarding different elements of the widget editor:

<table><thead><tr><th width="220">Edit</th><th>Description</th></tr></thead><tbody><tr><td>Widget name</td><td>Name of the widget. To change the name of the widget, click the <strong>Edit</strong> icon inline with the name and use the provided field to configure a new name</td></tr><tr><td><a href="https://docs.didomi.io/widgets/widget-editor/manage-widget-layers.md">Widget layers</a></td><td>Enables your organization to customize multiple layers that an end-user can interact with. </td></tr><tr><td><a href="https://docs.didomi.io/widgets/widget-editor/widget-components.md">Components</a></td><td>Modules that are added to widget layers to customize the end-user interface. </td></tr><tr><td><a href="https://docs.didomi.io/widgets/widget-editor/widget-preview.md">Preview</a></td><td>Toolbar that allows your organization to adjust the widget preview window (e.g. brand, screen size, translation, etc...)</td></tr><tr><td><a href="https://docs.didomi.io/widgets/widget-editor/widget-translations.md">Translation</a></td><td>Manage multiple translations for the widget</td></tr></tbody></table>

Regardless of whichever template (pop in, top banner, bottom banner) you start your widget from, Didomi will provide pre-configured layers with components to help your organization get started.

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2Fr95Bh3fpCIdNJZJjcdM8%2FScreenshot%202026-02-17%20at%203.59.31%E2%80%AFPM.png?alt=media&amp;token=563e805e-5440-4cc9-8b57-14f39b885a5a" alt="" width="563"><figcaption></figcaption></figure>


---

# 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/widgets/widget-editor.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.
