> 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-29.md). # 8.4.0 — 29 April 2026 What changed in Dispel in the release of 29 April 2026. **Dispel Zero Trust Engine 8.4.0**, including Orchestrator 1.11.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 * [Compliance](https://docs.dispel.com/secure-and-govern/overview) is a section of its own. Dispel holds the framework as a catalog of controls, evaluates each one against what the system records, and shows the result per control. NIS2 (Implementing Regulation EU 2024/2690) is included. (DIS-18653, DIS-19930) * [Billing](https://docs.dispel.com/integrate-and-administer/billing) has a page of its own, showing your plan and what you are using against it. (DIS-19438, DIS-19439) * The Browser Connect utilization report filters by facility and by date range, and lists the recordings for the period. (DIS-19658) * Users and virtual desktop users can upload and download files on a device they have access to, and a facility can set how long a transferred file is kept. (DIS-19752, DIS-19755) * File transfers in progress moved from a floating widget into stacked picture-in-picture panels that sit alongside a session. (DIS-19835, DIS-19995) * Hovering the Participants column on the Active Connections table shows who is actually in the session. (DIS-19843) * The session timer reads in a clearer format, and the [maximum session age](https://docs.dispel.com/integrate-and-administer/settings/session-length) can be configured. (DIS-19638) * [High-contrast and colorblind-assistive themes](https://docs.dispel.com/integrate-and-administer/settings/account/themes) are available. (DIS-19881) * A third-party system can call the Dispel API with OIDC client credentials, which is how the [ServiceNow](https://docs.dispel.com/integrate-and-administer/integrations/service-now) integration authenticates. (DIS-19006) ## Bug fixes * Administrators and custodians at the destination facility could not see or approve a file transfer addressed to them. (DIS-17741) * Downloading a file transfer from the logs could fail. (DIS-19654) * A permissions report could be truncated when the dataset was large. (DIS-19031) * New stacks using on-demand virtual desktops could intermittently fail to build. (DIS-17802) * A popped-out Browser Connect session could stay on "Reconnecting…". (DIS-19285) * An integration that failed to sync or connect did not say why. (DIS-19632) * Accepting the terms during OIDC onboarding could loop. (DIS-20021) * **General bug and security fixes** across permission handling, session termination and notifications, the Active Connections table, Topology's list view and side panels, integration site mapping, Session Forensics scoring, the devices tab, and file transfer scanning. --- # 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-29.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.