> For the complete documentation index, see [llms.txt](https://docs.dispel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dispel.com/changelog/releases/2026-05-14.md). # 8.5.0 — 14 May 2026 What changed in Dispel in the release of 14 May 2026. **Dispel Zero Trust Engine 8.5.0**, including Orchestrator 1.12.0. {% hint style="info" %} [**Customer Impact Score: 2**](https://legal.dispel.com/support/maintenance-windows#customer-impact-scores) — visible changes and new features, without a substantial change to the workflows most people use. {% endhint %} ## New features and improvements * Uploads and downloads run [inside a Browser Connect session](https://docs.dispel.com/connect-to-your-systems/connection-methods/browser-connect/use-a-browser-connect-session), in a panel beside the screen, and progress as the session continues. (DIS-19754) * File Transfer is a column on the devices table, so the devices set up for it can be found from the list. (DIS-20076) * Setting up a [file share](https://docs.dispel.com/build-your-environment/infrastructure/device-management/file-share) has been reworked: the fields are grouped by what they configure, and the form tells you what it needs. (DIS-19753) * A recording that is still being made is marked **Live** in the recordings list. (DIS-20127) * An organization can turn [kiosk mode](https://docs.dispel.com/integrate-and-administer/settings/browser-connect) on or off for Browser Connect. (DIS-19621) * [Compliance](https://docs.dispel.com/secure-and-govern/overview) adds IEC 62443-3-3, and the frameworks it already carries report against a consolidated view. (DIS-20135, DIS-20266) * Active access sorts ahead of everything else on a device's Remote Access tab, in buckets rather than one alphabetical run. (DIS-20106) * Notification emails show times in the recipient's own time zone. (DIS-17436) * An invitation can be sent in any language the console supports. (DIS-20140) ## Bug fixes * Under certain conditions, sign-in could fail while Session Forensics recorded the event. (DIS-20358) * A Browser Connect session could go black if the side panel was closed while it was running. (DIS-20149) * A retention period of 0 days could delete a transferred file before the recipient had collected it. (DIS-20233) * A device discovered by an integration could be imported into the wicket's own facility rather than the mapped one, and Nozomi zones could not be filtered at the mapping step. (DIS-20009) * A virtual desktop reservation that failed to start could leave the desktop in a reserving state. (DIS-18111, DIS-17310) * A single connection could be recorded twice in the logs. (DIS-20126) * **General bug and security fixes** across permission and password handling, the devices table and its ordering, facility device actions, the session window, Active Connections, recordings navigation, integration error reporting, and Topology's grouping and filters. ## Closed Beta Switched on for selected organizations while we finish it. * **Saved views in Topology.** Build a filter from the fields on the list, group and sort the result, save it as a view, and set one as the view Topology opens on. (DIS-19956) --- # 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.dispel.com/changelog/releases/2026-05-14.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.