> 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-march-2024.md). # Improvements and fixes, March 2024 Improvements and bug fixes released in March 2024. *31 March 2024* ## Improved * **Portal:** Implemented a new date range picker in both the HEART and Content Analytics pages as well as the Survey and NPS builder pages. * **Portal:** Improved how the "Guides started over time" graph on the Guide's Performance page is calculated so that archived Guides are not included. * **Editor:** Added the option to use CTRL to (un)pause Recording mode. ## Fixed * **Portal:** Fixed an issue where the BypassSSO setting was not consistently shown as set for Admins. * **Portal:** Fixed an issue where the self-hosting download was not available for self-hosting customers. * **Other:** Fixed an issue that prevented the Guide from starting automatically when opened through a direct link. * **Other:** Fixed a problem ensuring moderators now reliably receive email notifications about Guide errors. * **Other:** Strengthened protection against Server-Side Request Forgery (SSRF) attacks in the HelpDesk integration. --- # 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-march-2024.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.