> 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/system/change-log/bluur-1.0.1.md). # Bluur 1.0.1 (15.08.2024) **New features:** * Anonymization logs added * System logs added * System notifications added * Email notifications added * Added the ability to confirm editing the project/document name by pressing the "Enter" key * The selected document list mode has been saved in the URL * Added a side scrollbar to the project/document list * Highlighted the Quick Anonymization project * Added translation of the Quick Anonymization project name * Added translations of the content of emails sent to users (English language) **Improvements and fixes to system functionality:** * Improved article fetching in the dashboard * Fixed a bug related to the ability to read sensitive data after anonymizing documents in PDF format * Fixed a bug in the classification of the "Letter" feature * Fixed a bug with fetching document history for users * Fixed key capture in windows * Improved document search in the document table * Removed the unnecessary date icon from the document table * Improved the highlighting of side navigation panel buttons when entering subpages, * Typographical errors fixed **User interface appearance improvements:** * Changed the size and shape of anonymized fields * Changed the placement and size of elements in the document preview view (enlarged buttons, moved pagination to the top of the view) --- # 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/system/change-log/bluur-1.0.1.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.