> 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/create-privacy-widget.md).
# Create privacy widget
{% hint style="success" %}
**Access Type**: Widgets - Editor
{% endhint %}
Widgets are interface templates that are surfaced to end-users in a consent flow in order to collect consent and/or refusal actions. In this article, we will cover how to create a new widget in your organization's Didomi account.
Click **Widgets** on the left-hand panel and select **Create a widget** on the subsequent page.
Use the following modal to select a type for your widget and click **Go to next step** when finished.
{% hint style="info" %}
Additional premium widget types are available (e.g. consent or pay). Please speak to your account representative for more information.
{% endhint %}
Next, select the style of template for the widget (pop in, top banner, bottom banner) and click **Create a widget**.
Your new widget will be created and added to your organization. Further customize the widget if necessary by utilizing the [widget editor](/widgets/widget-editor.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.didomi.io/widgets/manage-widgets/create-privacy-widget.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.
