> 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-february-2025.md). # Improvements and fixes, February 2025 Improvements and bug fixes released in February 2025. *28 February 2025* ## Improved * **Portal:** Improved wording in some areas of the Portal to increase clarity. * **Portal:** Improved the UI in the header and Snippet setup page to unify design. * **Portal:** Improved readability by updating colors in the UI. * **Assistant:** Improved how Tooltips with linked Guides display the Guide title for multi-language use cases. * **Other:** Updated the IdP for Managers to a more recent version to improve authentication and avoid vulnerabilities. ## Fixed * **Portal:** Fixed an issue where users were unable to successfully configure the Confluence knowledge base integration. * **Portal:** Fixed an issue on the Happiness page where the "Users Reached" count was showing incorrectly. * **Editor:** Fixed an issue where the "test successful" banner after testing a Tag would result in an undesired animation. * **Assistant:** Fixed an issue where data in the event of a Guide Error was not being sent to Userlane content analytics if the error occurred on a step with a skip condition applied. * **Assistant:** Fixed an issue where text in the Guide Error modal was not showing line breaks correctly. * **Assistant:** Fixed an issue where global CSS affected the text formatting in Userlane content for some customers. * **Other:** Fixed an issue with cloning a property where all Guides were incorrectly moved to the Unsorted folder. * **Other:** Fixed an issue where Guides would break after a page reload on the underlying application. --- # 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-february-2025.md?ask=&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.