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

# Manage widgets

Widgets are interface templates that are surfaced to end-users in a consent flow in order to collect consent and/or refusal actions. Utilizing the component library your organization can create fully customized and modular interfaces that can be deployed across multiple consent flows. 

Your organization's widgets are accessible by clicking **Widgets** on the left-hand panel.

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FtWKJ2dvlyuFjfxJO9g7r%2FScreenshot%202026-02-17%20at%201.20.07%E2%80%AFPM.png?alt=media&amp;token=d094d08b-0b08-4254-af3c-7ad912995777" alt="" width="563"><figcaption></figcaption></figure>

The subsequent page will list all widgets that have been created for your organization's Didomi account. Each widget will have the following information listed:

<table><thead><tr><th width="190">Field</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>The name configured for the widget. The widget's ID is also provided directly under the widget name.</td></tr><tr><td>Type</td><td>The widget's type that was selected when the widget was created (Standard Consent, Consent or Pay, etc...)</td></tr><tr><td>Consent flows</td><td>Consent flows where the widget is currently applied</td></tr><tr><td>Last edit</td><td>Last recorded edit that was saved for the widget</td></tr><tr><td>Status</td><td>Draft | Active. Designates whether the widget is currently used in a consent flow that is actively published.<br><br><mark style="background-color:$warning;"><strong>Note</strong>: Widgets with Active status cannot be deleted.</mark></td></tr></tbody></table>

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FSf5RbjXGJSIOSmFFwEKk%2FScreenshot%202026-02-17%20at%201.25.50%E2%80%AFPM.png?alt=media&amp;token=179ec2f2-7e70-4ee3-971f-e4f3b932eb35" 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/manage-widgets.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.