> 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/set-regulation-as-default.md).
# Set regulation as default
{% 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.
Your organization can set an existing regulation that it has configured as the default regulation that is automatically used when creating new privacy flows.
{% hint style="info" %}
Only one regulation can be set as your organization's default regulation.
{% endhint %}
In order to set a regulation as the default, click **Regulations Manager** on the left-hand panel.
Navigate to a regulation on the subsequent list and click the edit icon inline with the regulation name.
Enable the **Set regulation as default** setting on the regulation builder page.
The regulation will be set as the default regulation used when creating new privacy flows.
---
# 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/set-regulation-as-default.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.
