> 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/working-with-a-document/stages/anonymization/adding-fields.md).

# Adding fields

At the stage of **Anonymization** the user can manually add their own area intended to be hidden if the required data was not previously detected by the classifier.

Click the selected spot in the document, hold down the left mouse button, and drag the selection over the area to be anonymized.

Before performing anonymization, the manually added area can be moved, resized, or deleted. To do this, go to the stage of **Classification.**

Manually added areas are not assigned to categories detected by the classifier. They are taken into account during anonymization regardless of the category slider settings.

<figure><img src="/files/45b01ad8bcd56e82fa69d127b90dcf5c5b152578" alt="Ręczne zaznaczanie obszaru dokumentu na etapie anonimizacji."><figcaption><p>Manually adding an area intended for anonymization.</p></figcaption></figure>


---

# 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/working-with-a-document/stages/anonymization/adding-fields.md?ask=<question>&goal=<endgoal>
```

`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.
