> 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/projects/project/documents/status.md).

# Status

The status informs you which stage of processing the document is at.

The status informs you which stage of processing the document is at.

**Classified**\
This means that the system has performed AI classification and identified fields requiring verification. The user can open the document, check the classification result, and proceed to anonymization.

**Anonymized**\
This means that the user has anonymized the document. Until archiving, the saved changes can be undone in the system and you can return to the classification stage. This does not affect files previously downloaded, in which anonymization is permanent and irreversible.

**Archived**\
This means that the source document has been deleted and only its anonymized version remains in the system. The document can no longer be edited or restored to the classification stage.

#### Archiving a document

A document can be archived after anonymization is completed. Archiving is available from the view of the anonymized document.

After confirming the operation, the system deletes the source document and leaves only its anonymized version.

{% hint style="danger" %}
**Important:** Archiving cannot be undone. Once it is done, it is not possible to return to classification or further edit the document.
{% endhint %}

<figure><img src="https://572977165-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKPbZABdmwpFq6bAJuwUC%2Fuploads%2Fvh5YyZSyVhrCUk9Nx8w7%2Fimage.png?alt=media&amp;token=cf94e337-cc62-4021-9358-da107c046a60" alt="Statusy dokumentów w projekcie"><figcaption><p>Document statuses.</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 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/projects/project/documents/status.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.
