> 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/configuration.md).

# Configuration

Before configuring the integration, prepare a Bluur account. A person with the appropriate permissions should register the account, complete the organization details, and purchase a subscription plan.

{% stepper %}
{% step %}

### Registration

Create an account [**Bluur**](https://app.bluur.ai/register)**,** complete [the required organization details and select the appropriate plan.](https://bluurdoc.bluur.ai/rozpoczecie-pracy/szybki-start) After activating the paid subscription, the account can be used for integration with eAuditor Cloud.
{% endstep %}

{% step %}

### API key

To connect eAuditor Cloud with Bluur, an API key is required. [Generate a separate key for this integration](https://bluurdoc.bluur.ai/funkcje/ustawienia/klucze-api) and save its full value in a secure location. The full key is visible only during creation.

<figure><img src="https://3262380731-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdzip3GyvGq5q5J3qckWN%2Fuploads%2FNxz4EeAKsdD6wbcGB941%2Fimage.png?alt=media&amp;token=6d546317-8cc0-409d-a156-2ea2085ae684" alt="Widok zarządzania kluczami API z przyciskiem Add API key."><figcaption><p>Starting creation of a new API key.</p></figcaption></figure>

{% hint style="danger" %}
**Important:** Treat the API key as credentials. Do not share it with others, do not place it in messages, public repositories, or screenshots. If the key may have been exposed, deactivate or delete it and generate a new one.
{% endhint %}
{% endstep %}

{% step %}

### Connection to the Bluur account

1\.       Go to the Bluur integration settings in eAuditor Cloud.

2\.       Enter the API key previously generated in Bluur.

3\.       Save the integration configuration. The system will connect eAuditor Cloud with the Bluur account assigned to the specified API key.

After a successful connection, eAuditor Cloud can send documents and text for processing by Bluur and use the schemas shared in the integration configuration.

{% endstep %}

{% step %}

### Anonymization schemas

In Bluur, you can prepare [anonymization schemas that define](#schematy-anonimizacji), which categories of data are to be hidden by default. During integration configuration, a person with the appropriate permissions selects via checkboxes which of the created schemas are to be available to eAuditor Cloud users.

The schema does not change how the document is classified. It defines the scope of data that will be applied during automatic anonymization.

<figure><img src="https://3262380731-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdzip3GyvGq5q5J3qckWN%2Fuploads%2F0A48KOMUTT7j2kGYApxf%2Fimage.png?alt=media&amp;token=c3b0e478-c05c-45d9-baa1-7a4e9916883c" alt="Udostępnanie schematów animizacji do API Bluur."><figcaption><p>Sharing anonymization schemas to the API.</p></figcaption></figure>

{% hint style="info" %}
**Important:** The selected schema is applied to all documents added within a given operation. If the user does not select a schema, the Default configuration will be applied, covering all [32 data categories](https://bluurdoc.bluur.ai/funkcje/praca-z-dokumentem/etapy/klasyfikacja-ai/kategorie).
{% endhint %}
{% endstep %}

{% step %}

### Document retention

Documents sent from eAuditor Cloud are stored in Bluur in the Fast anonymization space of the API key owner. Therefore, before starting the integration, it is worth configuring retention policies for this space.

[Retention setting](#retencja-dokumentow) determines whether documents after Fast anonymization remain available in the system and how long they are retained. The same policies apply to documents transferred from eAuditor Cloud.

<figure><img src="https://3262380731-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdzip3GyvGq5q5J3qckWN%2Fuploads%2FQvzD0BdgmDrgcaWvcbpd%2Fimage.png?alt=media&amp;token=1f2858cb-78fe-438b-b1ec-3c7e27daea3f" alt=""><figcaption><p>Document retention settings.</p></figcaption></figure>
{% endstep %}
{% endstepper %}

## Useful links:

{% content-ref url="/spaces/KPbZABdmwpFq6bAJuwUC/pages/JR7DIo0Ypg2xkcOpnsO6" %}
[Rozpoczęcie pracy](https://bluurdoc.bluur.ai/rozpoczecie-pracy/szybki-start)
{% endcontent-ref %}

{% content-ref url="/spaces/KPbZABdmwpFq6bAJuwUC/pages/Tp5u5YQtQxi9OTQ5YDMd" %}
[Klucze API](https://bluurdoc.bluur.ai/funkcje/ustawienia/klucze-api)
{% endcontent-ref %}

{% content-ref url="/spaces/KPbZABdmwpFq6bAJuwUC/pages/xvvaTCJ6FzGOQpEhboFe" %}
[Schematy](https://bluurdoc.bluur.ai/funkcje/ustawienia/anonimizacja/schematy)
{% endcontent-ref %}

{% content-ref url="/spaces/KPbZABdmwpFq6bAJuwUC/pages/BXOSQSUoxbOyq5MN2yJP" %}
[Retencja](https://bluurdoc.bluur.ai/funkcje/ustawienia/anonimizacja/retencja)
{% endcontent-ref %}


---

# 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/configuration.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.