> 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-a-category-for-purpose.md).
# Create a category for purpose
You can create your own categories of purposes for your web or app consent notices.
This will make the 2nd layer of your banner, dedicated to the purposes, easier to read, as they will be grouped into large purpose families
Go to the **Consent Notices (1)** section and step **1.** **Regulations (2).**
Go to GDPR regulation then click on **Edit Vendors & Purposes (3)**
{% hint style="info" %}
Category management is only available for GDPR. CPRA offers default mandatory categories that cannot be customized.
{% endhint %}
1. Scroll down to the **Purposes** section and click on **Add category** (for example, perhaps you'd like to create a category called "Personalised Ads").
2. Add a language,
3. Add a name and description.
4. Click on **Save**.
You can also click on "Expand category when showing the list of purposes" if you want the category to be by default 'unfolded' on the 2nd layer of the banner.\
\
In order for the category to be displayed in the preferences view (i.e., second layer of the notice) it must contain at least one purpose.
To add a purpose, drag and drop the purpose under the desired category. Purposes available for drag and drop will appear according to the vendors selected.
As mentioned, your category will appear on the second layer of your notice or"preferences view". Users will be able to accept all the purposes included in this category in a single click. They can also make more granular choices by accepting/refusing purpose by purpose.
---
# 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/consent-management-platform-cmp/frameworks-regulations/general-data-protection-regulation-gdpr/create-a-category-for-purpose.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.
