> 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-09-14.md). # 8.13.0 — 14 September 2026 What changed in Dispel in the release of 14 September 2026. **Dispel Zero Trust Engine 8.13.0**, including Orchestrator 1.22.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 * You can now search [Settings](https://docs.dispel.com/integrate-and-administer/settings) from the top of its navigation or with ⌘K. (DIS-23658) * The sidebar and page have a new card layout. (DIS-23438) * In organizations that record unique device identifiers, [Topology](https://docs.dispel.com/monitor-and-investigate/topology) shows them as the first column of the list and beneath each device in the tree, and you can sort and search by them. (DIS-23963, DIS-23969) * A device set up for Browser Connect over RDP can turn off the offscreen graphics cache under its advanced settings, for older Windows hosts whose display arrives corrupted or frozen. (DIS-23734) * The device in a recording's details panel opens in Topology. (DIS-19690) * Credential fields on a file transfer have a control to show the password you typed. (DIS-23378) * The Chinese and Japanese translations have been updated. (DIS-23497, DIS-23611) ## Bug fixes * The dashboard could show a facility as healthy while its wicket was offline. (DIS-22648) * Recording playback could jump to the end and then refuse to rewind, and Skip on the idle banner paused the recording instead of skipping. (DIS-23618, DIS-23444) * After an idle timeout ended a Browser Connect session, the Reconnect button might do nothing, and a user who had reconnected could be disconnected for inactivity while still working. (DIS-23819, DIS-23750) * An approved access window could show 0 groups and 0 members to custodians and administrators, and a window could read Passed while giving an end date in the future. (DIS-23597, DIS-23595) * Devices and findings from Armis, Claroty and Tenable OT Security had no link back to the vendor's console, and Tenable OT Security was labeled "Tenable". (DIS-23616, DIS-23475) * In some cases, a user who signs in with single sign-on and belongs to more than one organization could not switch between them. (DIS-23676) * Syncing devices from an integration could fail on a very large site. (DIS-23965) * **General bug and security fixes** across the Browser Connect session-ended screen, device settings and notifications, recording errors and live-session status, file transfer alerts, deleting reserved desktops, group permission levels, identity provider user sync, sign-in and session handling, logs, integration credentials, wicket port forwarding, email language, 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-09-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.