> For the complete documentation index, see [llms.txt](https://eaclouddoc.eauditor.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eaclouddoc.eauditor.eu/eacloud-docs-en/features/tools/configuration/integrations/bluur/anonymization/documents.md).

# Documents

### Adding

Go to the Anonymization module and select the Documents tab. Files can be dragged to the upload area or added using the Select Files button.

Before processing begins, select an anonymization scheme from the list provided by the administrator. The selected scheme will be applied to all documents added in this operation.

{% hint style="warning" %}
**Important:** If you do not select another scheme, the system will apply Default and anonymize data belonging to all [32 categories](https://bluurdoc.bluur.ai/rozpoczecie-pracy/szybki-start/kluczowe-funkcje/klasyfikacja-ai#zakres-klasyfikacji)and supported by Bluur.
{% endhint %}

<figure><img src="https://3262380731-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdzip3GyvGq5q5J3qckWN%2Fuploads%2FgbMP2TG9hKjarySkMpka%2FZrzut%20ekranu%202026-09-14%20144726.png?alt=media&amp;token=aa7071e7-eb8d-491c-8f65-a35db7aef143" alt="Panel użytkownika z połączonym rozwiązaniem Bluur umożlwiający anonimizacje po API"><figcaption><p>Adding documents and selecting the anonymization scheme in the Employee Panel.</p></figcaption></figure>

### Classification and anonymization

After the files are uploaded, Bluur automatically starts classifying them. The current status and process progress are displayed for each document.

Once classification is complete, the document is automatically anonymized according to the selected scheme. The process does not require manual switching between classification and anonymization or confirming detected fields in eAuditor Cloud.

<figure><img src="https://3262380731-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdzip3GyvGq5q5J3qckWN%2Fuploads%2F47sY7cRaddV8TEMsbBO0%2Fimage.png?alt=media&amp;token=719cb29d-112d-414e-b2bf-c26675153b0b" alt="Automatyczna klasyfikacja z użyciem API Bluur dokumentów przed anonimizacją."><figcaption><p>Automatic document classification before anonymization.</p></figcaption></figure>

### Downloading&#x20;

After the process is complete, the documents receive the Anonymized status. Click Download anonymized documents to download the finished files.

The documents are available in the current view until it is refreshed. After refreshing the Employee Panel, previously processed files are no longer displayed here.

<figure><img src="https://3262380731-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdzip3GyvGq5q5J3qckWN%2Fuploads%2FRyx32XEtDYR0McmAwuIx%2FPobieranie%20dokument%C3%B3w%20(1).png?alt=media&amp;token=cb66d6f4-a598-4ef1-9bf3-20ec2bfbb5c2" alt="Pobieranie gotowych, zanonimizowanych dokumentów. Zgodnie z wybranym schematem anonimizacji. "><figcaption><p>Downloading ready, anonymized documents.</p></figcaption></figure>

### Saving

All documents uploaded by users of the Employee Panel are simultaneously saved to the Bluur account associated with the API key. The files are stored in the user's individual Quick anonymization workspace, belonging to the user who generated the API key used in the integration.

These documents are subject to the [Quick anonymization retention](https://bluurdoc.bluur.ai/funkcje/ustawienia/anonimizacja/retencja#przechowywanie-dokumentow-po-szybkiej-anonimizacji) configured on that Bluur account.


---

# 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://eaclouddoc.eauditor.eu/eacloud-docs-en/features/tools/configuration/integrations/bluur/anonymization/documents.md?ask=<question>&goal=<user_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.
