> For the complete documentation index, see [llms.txt](https://docs.userlane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.userlane.com/changelog/2025/improvements-and-fixes-august-2025.md).

# Improvements and fixes, August 2025

Improvements and bug fixes released in August 2025.

*31 August 2025*

## Improved

* **Portal:** Added API authentication token; customers can now use a secret key with each API request for extra security.
* **Portal:** Added a filter to show all Guides with errors in the Guides list (Guide Analytics page).
* **Portal:** Introduced daily Announcement/Survey reminders, useful for urgent updates.
* **Portal:** Apps in the side navigation are now sorted alphabetically, with full names shown on hover.
* **Portal:** Minor UI and design system improvements, including improvement on the stacked vertical bar chart in analytics.
* **Assistant:** Improved how the position of Tooltip icons is calculated such that there is no longer a delay on user scroll.

## Fixed

* **Portal:** Fixed an issue where some AI-based functionality in the Portal did not load due to a backend service not restarting properly.
* **Portal:** Fixed incorrect texts in the Announcement builder.
* **Portal:** Fixed a bug where Announcement pins sometimes caused a 409 error.
* **Editor:** Fixed multiple issues where Tooltips could not be saved after manual changes were made to the code selector for a given Tooltip.
* **Assistant:** Fixed an issue where the AI Assistant chat was visible in the classic Assistant for Managers after closing the Editor.


---

# 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://docs.userlane.com/changelog/2025/improvements-and-fixes-august-2025.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.