> For the complete documentation index, see [llms.txt](https://wiki.lucysecurity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.lucysecurity.com/release-notes/6.0.1.md). # 6.0.1 ## Release Notes #### July 2026 This patch release includes fixes for training link rendering, campaign statistics, and filter dropdown visibility. Key updates include: * Fixed Training Link Content: Resolved an issue where End User campaigns using SSO, direct login, separate subdomains, and multiple awareness groups loaded the same training content for every awareness link. * Portable Media Campaign Tracking: Resolved an issue where executing a "Console POST" or other EXE file template in a Portable Media Attack campaign was not recorded in campaign statistics. * Campaign Filter Presets: Resolved an issue where Campaign Filter Presets assigned to all clients were not displayed in the "Load Pre-defined Filters" dropdown within campaign settings. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://wiki.lucysecurity.com/release-notes/6.0.1.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.