> For the complete documentation index, see [llms.txt](https://bluurdoc.bluur.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bluurdoc.bluur.ai/en/features/settings/anonymization/schemes/creation.md).
# Creation
To create a new anonymization schema:
1. Go to **Settings → Anonymization**.
2. In the section **Anonymization schema** click **Add new**.
3. Enter a schema name that will make it easy to recognize its purpose, e.g. `CV`, `Contracts` or `HR documentation`.
4. Select the data categories to be included by the schema.
5. Using the available toggles, specify the specific types of information to be detected.
6. Click **Save schema**.
Creating a new schema.
While creating a schema, the user specifies which **data categories** should be enabled by default during anonymization.
Turn the appropriate category sliders on or off, then save the schema. These settings will be used when moving the document to the stage **Anonymization**.
### API
Option **Share via API** allows the anonymization schema to be shared with integrated systems using the API. Once enabled, the schema will be available in integrations and can be selected when anonymizing documents outside Bluur.
Sharing the anonymization schema via API.
---
# 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://bluurdoc.bluur.ai/en/features/settings/anonymization/schemes/creation.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.
