> 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.2.md).

# Bluur 1.0.2

(30.08.2024)

**New features:**

* Highlighting new documents and projects, including the “Fast anonymization” project.
* Added automatic subscription creation.
* Downloading articles from WordPress when an instance starts.

**Improvements and fixes to system functionality:**

* The new document status disappears after viewing the document or after 24 hours.
* Changed log read permissions: ADMIN can see all logs, USER can only see their own logs.
* Fixed anonymization and downloading of rotated PDF files.
* Improved the quality of PDF-to-JPG conversion when downloading PDF files.

**User interface appearance improvements:**

* Default log sorting by creation date.
* Improved data display and pagination in the invoice table
* Fixed the display of the tax country in settings.


---

# 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.2.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.