> 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-08-26.md). # 8.12.0 — 26 August 2026 What changed in Dispel in the release of 26 August 2026. **Dispel Zero Trust Engine 8.12.0**, including Orchestrator 1.21.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 * The main sidebar has been reorganized. Every labeled section now collapses and remembers how you left it, Dashboard, Access Windows and Settings sit together under **Control**, and Regions and Facilities under **Sites**. (DIS-23400) * Documentation now appears inside the console. Help marks beside a control preview the relevant article on hover, the Help panel opens the full article beside your work, and the articles follow the language you have set. (DIS-23364) * Devices now record where Dispel learned about them. Source is a sortable column on the devices list and a filter in [Topology](https://docs.dispel.com/monitor-and-investigate/topology), so devices discovered by an integration can be told apart from ones added by hand. (DIS-19849) * Recording playback runs through idle stretches instead of stopping at them, and the timeline stays inside the panel. (DIS-23250) * File transfers to a target that expects a domain now accept one, including for transfers that do not use the password vault. (DIS-23181, DIS-23179, DIS-23180) * The recovery codes screen has been redesigned. (DIS-23365) * A wicket that fails to upgrade now says so, instead of leaving you to notice it had not moved. * A wicket reports its device inventory again after a reboot, so the list reflects what is actually on it. * The Japanese, Chinese, French, German, Dutch, Portuguese and Spanish translations have been updated across the console. (DIS-23399) * An organization can now nominate its own [points of contact](https://docs.dispel.com/integrate-and-administer/settings/points-of-contact), so the lockout notice a user receives names an administrator they can reach instead of an unmonitored address. (DIS-23025) * Apple devices can now be configured from the device page. (DIS-22509) ## Bug fixes * Deleting a region or facility that still held file transfers could fail part-way and leave it half removed. The delete is now refused up front, with the reason. (DIS-16144) * The password history field rejected 0, although its own hint offered it as the way to track every previous password. (DIS-21503) * Building a stack inside an existing network could build the desktops twice. (DIS-23316) * [Compliance](https://docs.dispel.com/secure-and-govern/overview) PDF exports could download corrupt, and in some cases could fail outright. (DIS-23457) * Opening an HTTP Browser Connect target in a new window might return Forbidden, while the other protocols worked. (DIS-22885) * Remote Access on a device could open a blank page. (DIS-22396) * A device could not be deleted while orphaned Browser Connect sessions still referenced it. (DIS-21367) * Members could not be removed from an organization while the user list was filtered. (DIS-19157) * The inactivity lockout email told users to reply to a do-not-reply address. (DIS-23024) * An OpenVPN wicket could fail to build while wicket patching was turned on. (DIS-23208) * A wicket's tunnel could discard traffic under sustained load. (DIS-19202) * Building a region could stall part-way and need starting again. * **General bug and security fixes** across wicket and region deletion, session end messages, notifications and Browser Connect windows, stack builds, facility permission levels, access window details, device list pagination, Quick Connect styling, file transfer and recording errors, Topology rendering, and translations. --- # 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-08-26.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.