> 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/functions/settings/anonymization/schemes/project.md).
# Project
If the organization uses different anonymization ranges for different types of documents, the appropriate scheme can be assigned directly to the selected project.
Documents in such a project are classified as usual. After moving to the stage **Anonymization** the system automatically sets the category sliders according to the scheme assigned to the project.
This makes it possible to use different anonymization settings in individual workspaces without the need to change the global scheme.
{% hint style="danger" %}
**Important:** The scheme assigned to the project takes precedence over the global scheme. If the project has its own scheme, its settings will be applied during anonymization of documents in that project.
{% endhint %}
#### Assigning a scheme to a project
The anonymization scheme can be assigned to a project during its configuration.
1. Go to project creation.
2. In the field **Anonymization scheme** choose one of the previously created schemes.
3. Create a project.
Assigning an anonymization scheme to a project.
From now on, documents in the project will use the selected scheme after proceeding to the stage **Anonymization**.
If no custom scheme is assigned to the project, the system will use the currently set global scheme.
{% hint style="info" %}
The system selects anonymization settings in the following order:
1. **Scheme assigned to the project** – if set, it takes precedence.
2. **Global scheme** – is used if the project does not have its own scheme.
In both cases, the scheme affects only the category setting at the stage **Anonymization**. It does not change the way the document is classified.
{% endhint %}
---
# 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, and the optional `goal` query parameter:
```
GET https://bluurdoc.bluur.ai/en/functions/settings/anonymization/schemes/project.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.