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

# Bluur 1.0.8

**New features:**

* A new subscription type has been added: **“custom”** – skips synchronization with Stripe.
* Automatic counter reset at the beginning of each subscription month has been implemented.
* User role tags have been added **“Administrator”** and **“Invited”** in the users table.

**Improvements and fixes in system operation:**

* The method for counting invited users has been improved – now only users who have actually registered are counted.
* Fixed the incorrect behavior of the user counter in the invitation modal window.
* The version number has been removed from the login screen.
* Improved system authentication mechanisms related to changes in PZ.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://bluurdoc.bluur.ai/en/system/change-log/bluur-1.0.8.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.