# Archive preferences widget

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

**Premium Feature**: Preference Management Platform
{% endhint %}

Archiving a preferences widget will remove the widget from any websites where that widget was embedded/deployed. In this article, we will cover how to archive an existing preferences widget.

{% hint style="warning" %}
**Note**: Once a preferences widget is archived it can no longer be edited, re-published, or duplicated.
{% endhint %}

To start, click **Preferences** on the left-hand panel and ensure the **Widgets** tab is selected on the subsequent page. 

<figure><img src="/files/17JmQ8d4KZTEK2lpnaTp" alt="" width="563"><figcaption></figcaption></figure>

Navigate to a preferences widget with a publication status of **Published** on the list and click the **ellipsis** inline with the preferences widget name.

Select **Archive** from the menu.

{% hint style="info" %}
Only preferences widgets with a [publication status](/preference-management-platform-pmp/preferences-widgets/preferences-widget-status-glossary.md) of **Published** or **Unpublished Changes** can be archived.
{% endhint %}

<figure><img src="/files/zOZvrM9wDVjjgw5P1MjR" alt="" width="563"><figcaption></figcaption></figure>

Confirm the decision to archive the widget in the subsequent modal and click **Got it, archive!**

<figure><img src="/files/qTYUBosNzRtfYY6WbiSe" alt="" width="375"><figcaption></figcaption></figure>

The preferences widget will be archived and the widget will no longer be available on websites where the widget was embedded/deployed.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.didomi.io/preference-management-platform-pmp/preferences-widgets/archive-preferences-widget.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.