> 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.md). # Schemes Anonymization schemes allow you to define which data categories should be selected by default when working in the stage **Anonymization**. This means that in repetitive processes, the user does not have to manually set the same categories every time. The scheme does not affect the operation **AI Classification** or the scope of detected data. The document is always classified in the standard way, and after moving to the stage **Anonymization** the system automatically sets the toggles according to the global scheme or the scheme assigned to the project. If the project has its own scheme, it takes precedence over the global setting. #### Example 1 – one scheme for the entire organization The company uses Bluur mainly to anonymize CVs, and in each document it wants to hide the same set of data by default, for example first name, last name, email address, phone number, and address details. The administrator creates a schema **CV** and sets it as the global schema. There is no need to assign it separately to each project. Documents are classified by default. After moving to the stage **Anonymization** the system automatically sets the category sliders according to the schema **CV**. #### Example 2 – different schemes for different projects The organization uses Bluur to work with different types of documents, for example resumes and contracts. The administrator creates separate schemes **CV** and **Contracts**. The scheme **CV** can be set as global, while the scheme assigned to the project intended for handling contracts **Contracts**. Documents in the contracts project will use the scheme **Contracts**, because the scheme assigned to the project takes precedence over the global scheme. The remaining projects without their own scheme will continue to use the scheme **CV**. --- # 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.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.