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

# Bluur 1.0.6

(23.10.2024)

**New features:**

* Adding user validation based on a blacklist.
* Enabling a button that redirects to the payment page on the dashboard.
* Adding combobox elements for entering country selection data in settings.
* Dynamic updating of active subscription information.
* Dynamic updating of current page information and user counters.
* Adding a notification about no active subscription before performing anonymization or inviting a new user if there is no purchased subscription.
* Adding a confirmation prompt for anonymization and inviting a new user when active subscription limits are reached.

**Improvements and fixes to system functionality:**

* Fixed a bug causing tax information to be deleted when modifying company data in settings.
* Fixed a bug preventing some tax countries from being displayed in the combobox element in the tax information form in settings.
* Fixed a bug preventing entry of the tag name after double-clicking the "Add tag" button.
* Fixed a bug redirecting to the knowledge base and support page.
* Fixed a bug when inviting new users to the system.

**User interface appearance improvements:**

* Removing the option to set shipping information to match billing information in settings.
* Fixed a bug displaying the project name while editing it.
* Removing the duplicate "Handwriting" category in anonymization functions.


---

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