> 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-december-2025.md).

# Improvements and fixes, December 2025

Improvements and bug fixes released in December 2025.

*31 December 2025*

## Improved

* **Portal:** Updated some double-axis analytics charts for better readability and clearer comparisons.
* **Portal:** Improved Task Trends by implementing new simpler signals on the Tasks page.
* **Portal:** Refined the donut chart styling with updated strokes and a smaller heading for a cleaner look.
* **Assistant:** Updated the expiration status for Task sessions.

## Fixed

* **Portal:** Fixed company user sorting so users are now listed in the correct order.
* **Portal:** Removed the misleading tooltip for created users to reduce visual noise and keep the UI cleaner.
* **Editor:** Fixed an issue where the Editor was not sending the correct name to the Portal for Task Actions.
* **Editor:** Fixed an issue where a customer could not create new Chapters in the Editor.
* **Assistant:** Fixed an issue where the Tooltip icon would detach from the selected element on tables when CSS anchoring was in use.
* **Other:** Fixed an issue where Userlane caused a certain page on the underlying application to crash.


---

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