> 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/preference-management-platform-pmp/preferences-library/duplicate-preference.md).
# Duplicate preference
{% hint style="success" %}
**Access Type:** Configuration Tree - Editor
**Premium Feature**: Preference Management Platform
{% endhint %}
A preference is a data collection point regarding an end-user's intentions, decisions, motivations, and interests (e.g. their preferred method of contact). In this article, we will cover how to duplicate an existing preference within your organization's preference library.
Click **Preferences** on the left-hand panel.
Select the **Configuration Tree** tab on the subsequent page and navigate to the **Preferences Library** panel.
Navigate to a preference in your preferences library and select the **ellipsis** icon inline with the preference name. Click **Duplicate** from the menu.
The subsequent preference creation page will have the original preferences name, description, values, and selection type pre-populated in the appropriate fields.
{% hint style="info" %}
The name of the duplicated preference will be prefixed with *Copy* and then the name or the original preference.
{% endhint %}
Edit the duplicated preference as necessary and click **Save preference** when finished to add it to your preferences library.
---
# 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/preference-management-platform-pmp/preferences-library/duplicate-preference.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.
