> 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-04-15.md). # 8.3.0 — 15 April 2026 What changed in Dispel in the release of 15 April 2026. **Dispel Zero Trust Engine 8.3.0**, including Orchestrator 1.10.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 * Files can be uploaded to and downloaded from a device [from the device page](https://docs.dispel.com/build-your-environment/infrastructure/device-management/device-file-upload-download). (DIS-17853) * Browser Connect works on a phone: the toolbar, the timeline and recording playback are all laid out for a small screen. (DIS-19309) * The Active Connections table refreshes as sessions start and end, rather than when the page is reloaded. (DIS-19229) * Logs record the device a session connected to, by name, and note the moment an HTTP or HTTPS session first connects. (DIS-19449, DIS-19209) * Dispel reads asset inventory from TXOne StellarOne and [Armis Centrix](https://docs.dispel.com/integrate-and-administer/integrations/asset-discovery/armis), with a mapping step for sites. (DIS-18973, DIS-18594) * Administrators and Dispel engineers can cancel a file transfer started by someone else. (DIS-19498) * The Groups and Users tabs on a facility load faster. (DIS-19301) * Connecting to a device and reserving a virtual desktop show their progress step by step. ## Bug fixes * Turning on **Require two-factor authentication** for an organization could interfere with signing in, the MFA prompt itself could reload the page before sign-in completed, and exempting SSO users from MFA might not take effect. (DIS-19580, DIS-19496, DIS-19148) * Recording thumbnails could fail to load, the recordings list could reload unexpectedly, the viewer might not resize, and a recording could not be pulled back out of full screen the way a live session could. (DIS-19529, DIS-19530, DIS-19531, DIS-19261, DIS-19238, DIS-19231) * **General bug and security fixes** across access and permission handling, session lifecycle and participant controls, recording playback, the logs filters, invitation email, device ordering, the members and regions pages, the dashboard, Nozomi site mapping, and Session Forensics scoring. --- # 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-04-15.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.