> 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/2026/improvements-and-fixes-june-2026.md). # Improvements and fixes, June 2026 Improvements and bug fixes released in June 2026. *30 June 2026* ## Improved * **Portal:** Added the AI Assistant and Contextual Actions as starting points in the Guide overview analytics, so you can see how users reach your Guides. * **Portal:** Added the application user ID to survey and NPS result downloads, so responses can be matched to users in your own systems. * **Portal:** Improved "Translate to all languages" for Announcements so that images and links are now carried over along with the text. * **Portal:** Simplified the Guide list by removing chapter subtitles and the Customize Guide promotion page. * **Editor:** Made it possible to rename a newly recorded Guide directly in the Editor header before saving it for the first time. * **Editor:** Renamed the Archive option for Guides in the Editor to Delete, to reflect what the action does. * **Editor:** Updated the Editor sidebar so the Userlane logo now opens the analytics overview in the Portal. * **Assistant:** Improved single sign-on with the browser extension so that sign-in windows open less often. This improvement is enabled per company. ## Fixed * **Portal:** Fixed an issue where Moderators could not add an application URL. * **Portal:** Fixed an issue where the All time date range in engagement analytics showed data for the current day only. * **Portal:** Fixed an issue where the date picker in Content Analytics displayed incorrectly for some customers in the US. * **Portal:** Fixed an issue where the segment builder did not show the content that uses a segment. * **Portal:** Fixed an issue where texts on the File transfers and Customize Guides pages were not translated. * **Editor:** Fixed an issue where the Editor crashed when opening certain Guides. * **Editor:** Fixed an issue where a Guide title could not be changed and saved in the Editor. * **Editor:** Fixed an issue where text could not be entered in the Editor on some applications because the application took focus away. * **Editor:** Fixed an issue where publishing a chapter in the Editor was not saved. * **Editor:** Fixed an issue where a chapter title could not be updated in a language other than the default language. * **Editor:** Fixed an issue where selectors containing several options separated by commas were rejected when saving content. * **Editor:** Fixed an issue where a connection error message from your application was shown in the Editor. * **Editor:** Fixed an issue where saving a user inactivity context with a very long duration caused an error. * **Editor:** Fixed several display issues in the Editor, including icons shown in the wrong color and missing custom scrollbars. * **Editor:** Fixed an issue where Guide PDF exports stayed in the Waiting status and never completed. * **Assistant:** Fixed multiple issues with Contextual Actions: element click and user inactivity contexts did not trigger their action, an "element is present" context blocked other Contextual Actions, and a Message shown after a Guide was completed disappeared after a moment. * **Assistant:** Fixed an issue where Tooltips inside an iframe were not displayed. * **Assistant:** Fixed an issue where Userlane caused errors in some applications that load content in an iframe. * **Assistant:** Fixed an issue where links in Guide and Tooltip text that start with "www" opened the wrong address. * **Assistant:** Fixed an issue where some new users were not recognized because of upper and lower case differences in their user ID, so the Welcome Slide was not shown. * **Other:** Fixed multiple backend stability and performance issues, including faster loading of content for end users and fewer unnecessary requests after a Guide is completed. --- # 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/2026/improvements-and-fixes-june-2026.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.