> 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/regulations-manager/manage-regulations/duplicate-regulation.md).
# Duplicate regulation
{% hint style="success" %}
**Access Type**: Regulations Manager - Editor
{% endhint %}
A regulation is a configuration of data collection practices by your organization which includes aspects such as vendors and purposes used, applicable regions, industry and legislative frameworks, etc... The regulation is used in conjunction with a widget when publishing a privacy flow to your website or application.
In this article, we will cover how to duplicate an existing regulation in order to apply minor changes .
Click **Regulations Manager** on the left-hand panel.
Navigate to a regulation on the subsequent list and click the ellipsis inline with the regulation name. Select **Duplicate** from the drop-down menu.
Your organization will be taken to the regulation builder with all of the settings duplicated from the source regulations.
{% hint style="info" %}
The name of the duplicated regulation will be the source regulation name appended with **(copy)**.
{% endhint %}
Apply the necessary changes to the duplicated regulation and click **Save** when finished.
---
# 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/regulations-manager/manage-regulations/duplicate-regulation.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.
