> 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/2024/improvements-and-fixes-april-2024.md).

# Improvements and fixes, April 2024

Improvements and bug fixes released in April 2024.

*30 April 2024*

## Improved

* **Portal:** Improved line chart animations in analytics (bottom-up instead of top-down, smoother line segment connections).
* **Portal:** Added a "Last Updated" icon to the Tooltip views over time chart.
* **Portal:** Updated old message and notification boxes to align with new design components.
* **Portal:** Improved the Company Attributes page to ensure long attributes can be fully read.
* **Portal:** Added a helpful note regarding SAML certificates to the User Single Sign-On page.
* **Portal:** Added pagination to the User Segment preview so all users belonging to that segment can be found.
* **Portal:** Implemented new error messages for invalid integration URLs.
* **Portal:** Added validation to the name and email fields of the Team Member invite modal.
* **Portal:** Resolved an issue so that Team Members can be re-added or edited in the team as expected.
* **Editor:** Updated the Guide Completion check icon animation.
* **Editor:** Language settings in the Editor now update button texts like "Let's Go" immediately when switching languages.

## Fixed

* **Portal:** Fixed an issue where the Announcement interaction over time graph showed Views and Users on the incorrect Y-axes.
* **Portal:** Fixed an issue where the search in the User or Page Segments dropdown on the Guide edit page was broken.
* **Portal:** Fixed an issue where some admins could see a blank App URLs page.
* **Editor:** Fixed language switching issue where Step UI language was not updated when switching languages in a Guide.
* **Other:** Corrected access restrictions in the API, ensuring only Admin users can reach certain sensitive 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://docs.userlane.com/changelog/2024/improvements-and-fixes-april-2024.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.