> 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/dashboard/quick-anonymization.md).
# Quick anonymization
The Quick anonymization section allows you to anonymize a single document without having to create a project.
The user adds a file directly from the dashboard, selecting it from the drive or dragging it to the appropriate field. The system automatically creates a technical workspace and assigns the document to the user who uploaded it.
Documents added in this mode are visible in the tab [**Projects**](/en/features/projects.md), but remain separated from other users' documents and are not automatically shared with them.
Quick anonymization works well for individual documents and for situations in which the user wants to start the process without configuring an additional workspace.
Adding a document by dragging it into quick anonymization.
{% hint style="info" %}
The system supports the following file formats:
PDF, JPG, JPEG, JPE, JIF, JFIF, JFI, PNG, TIFF, TIF, TXT, DOC, DOCX.
The maximum size of a single document is **10 MB**.
In the case of [project work](/en/features/projects.md) the total size of uploaded documents cannot exceed **100 MB**.
{% endhint %}
---
# 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/dashboard/quick-anonymization.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.
