> 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/getting-started/quick-start/key-features.md).

# Key features

The Key features section presents the most important areas of the system and how it supports secure work with documents.

[**AI classification**](/en/getting-started/quick-start/key-features/ai-classification.md)\
Automatic recognition and marking of data requiring protection.

[**AI model security**](/en/getting-started/quick-start/key-features/ai-model-security.md)\
Information about how the model works and the protection of users' documents.

[**Irreversible anonymization**](/en/getting-started/quick-start/key-features/irreversible-anonymization.md)\
Permanent removal of specified data from the resulting version of the document.

[**Project-based work**](/en/getting-started/quick-start/key-features/project-work.md)\
Organizing documents and user collaboration within projects.

[**Access control and teamwork**](/en/getting-started/quick-start/key-features/access-control-and-team-collaboration.md)\
Managing user roles and access to projects.

[**Event log and auditability**](/en/getting-started/quick-start/key-features/event-log-and-auditability.md)\
History of actions performed on documents and in the system.

[**Document retention and deletion**](/en/getting-started/quick-start/key-features/document-retention-and-deletion.md)\
Rules for storing and automatically deleting files.


---

# 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/getting-started/quick-start/key-features.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.