> 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/privacy-requests/privacy-request-widgets/privacy-request-widget-status-glossary.md).

# Privacy request widget status glossary

{% hint style="success" %}
**Access Type**: Privacy request widgets - Editor or Viewer

**Premium Feature**: DSAR
{% endhint %}

Privacy request widgets configured by your organization can fall into two distinct statuses:

<table data-header-hidden><thead><tr><th width="169.5833740234375">Status</th><th>Description</th></tr></thead><tbody><tr><td><a href="#active-widgets">Active widgets</a></td><td>Privacy request widgets that are currently published or have yet to be published.</td></tr><tr><td><a href="#archived-widgets">Archived widgets</a></td><td>Privacy request widgets that were formerly published but have since been archived and no longer appear on websites where the widget was embedded.</td></tr></tbody></table>

### Active widgets

Active privacy request widgets are widgets that are published or in the process of editing by your organization and are divided into the following publication statuses.&#x20;

<table><thead><tr><th width="176">Publication status</th><th>Description</th></tr></thead><tbody><tr><td>Draft</td><td>The privacy request widget has never been published and is still being edited.</td></tr><tr><td>Published</td><td>The privacy request widget is published and may be embedded onto a website</td></tr><tr><td>Unpublished Changes</td><td>The privacy request widget is published and has edits saved that have not been published yet. These changes are not yet available on websites where the widget it embedded.</td></tr></tbody></table>

View all active privacy request widgets in you Didomi account by navigating to the Privacy requests widgets page.

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2F7b4x98QLd5Pl4DC8gaN4%2FScreenshot%202025-10-02%20at%2011.06.54%E2%80%AFAM.png?alt=media&amp;token=97de075d-a07b-4595-a8a0-0db4399f0825" alt="" width="563"><figcaption></figcaption></figure>

### Archived widgets

Archived privacy request widgets are formerly published widgets that have since been deprecated and are no longer accessible from the websites on which they were embedded.

{% hint style="info" %}
Viewing archived privacy requests widgets are not available in the Didomi console and only retrievable via API. [Click here](https://developers.didomi.io/api-and-platform/widgets/privacy-widgets/retrieve-widgets) to learn more.&#x20;
{% endhint %}


---

# 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/privacy-requests/privacy-request-widgets/privacy-request-widget-status-glossary.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.