> 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/working-with-a-document/stages/ai-classification/saving.md).
# Saving
At the top of the view there is a gold floppy disk icon, which is used to save changes made while working with the document.
After changing the position or size of the detected fields and after adding tags, click the floppy disk icon. Leaving the view without saving may result in the loss of the changes made.
Saving the document enables the user and other users assigned to the same project to continue working later.
The icon for saving changes on the top bar of the document view.
{% hint style="info" %}
**Important:** Saving changes applies only to the stage **Classification**, including editing the position and size of the detected fields. The anonymization performed does not need to be additionally saved using the floppy disk icon.
{% 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/working-with-a-document/stages/ai-classification/saving.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.
