> 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/consent-management-platform-cmp/frameworks-regulations/general-data-protection-regulation-gdpr/create-required-purpose-for-necessary-cookies.md).
# Create required purpose for necessary cookies
The ePrivacy directive allows certain cookies to be exempted from the requirement of consent, provided that they satisfy one of the following criteria:
* The cookie is used “for the sole purpose of carrying out the transmission of a communication over an electronic communications network”.
* The cookie is “strictly necessary in order for the provider of an information society service explicitly requested by the subscriber or user to provide the service”.
{% hint style="info" %}
Note, this is not an exemption from the obligation of information, and your Privacy/cookies Policy must inform users about the use of such cookies .
{% endhint %}
Didomi enables you to create a **required** purpose for these necessary cookies that the user cannot refuse. Steps for creating a **Required** purpose:
#### **1. Create a custom purpose for necessary cookies.**
To create a purpose, please refer to [our documentation.](https://support.didomi.io/create-a-custom-purpose-new-flow)
#### **2. Link your purpose to a vendor**
To create a vendor, please refer to [our documentation](https://support.didomi.io/create-a-vendor-new-flow).
#### **3. Mark your purpose as "required"**
1. Select your notice.
2. Go to the section called **1.** **Regulations** and the **Regulations** tab . **(2)**
3. Click on **Edit Vendors & Purposes** in the blue box next to each regulation **(3)** :
Select the vendor you created earlier in the vendors list.
Scroll down to the **Purposes** section and look for the custom purpose you created earlier.
Check the box "**Define as essential**" to make your purpose **Required**.
Your purpose will be **REQUIRED** in the Preferences view (i.e., Purposes layer) of your consent notice, and the user will not be able to reject the vendor linked to this purpose.
Don't forget to click on **SAVE & PUBLISH** when you are done!
---
# 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 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/consent-management-platform-cmp/frameworks-regulations/general-data-protection-regulation-gdpr/create-required-purpose-for-necessary-cookies.md?ask=
```
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.
.png?width=554&name=downloads.intercomcdn.comio213052423c8709f06ab34b09ec5917a6crequiredddd+(1).png)