> 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-23.md). # 8.14.0 — 23 September 2026 What changed in Dispel in the release of 23 September 2026. **Dispel Zero Trust Engine 8.14.0**, including Orchestrator 1.23.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 * **Beta Features**, in the account menu, lets you try features before they reach everyone. (DIS-23092) * The [Topology](https://docs.dispel.com/monitor-and-investigate/topology) list can show any stored device detail as a column, including serial number, firmware, MAC address and source, along with counts and created dates, and sort and search by any of them. (DIS-23982) * Topology renders faster on sites with 10,000 or more devices. (DIS-24097) * Opening a recording puts its link in the address bar, so you can copy it directly, and Back closes it. (DIS-24109) * The Browser Connect [idle timeout and recording idle sensitivity](https://docs.dispel.com/integrate-and-administer/settings/browser-connect) accept 0: no idle timeout, so sessions run until the maximum session duration, or no idle time marked on recordings. (DIS-23821) ## Bug fixes * A Browser Connect session that recorded nothing could still be listed as a complete recording and open in the normal player, and a recording's duration could show how long the session lasted rather than the length of the video. (DIS-23682, DIS-23684, DIS-23681) * In some cases, a Browser Connect session that stalled while starting could stop the user reconnecting, and after a reconnect the credential prompt could refuse typing. (DIS-23228, DIS-23933) * Under certain conditions, a user might not receive Browser Connect access they had been granted, or could lose access to a device that another of their grants still covered. (DIS-22011, DIS-23864) * For a user in more than one organization, the organization switcher could do nothing. (DIS-23827) * The average risk score in Session Forensics averaged the midpoints of each session's risk band instead of the sessions' actual scores. (DIS-23947) * Saving organization branding failed with "Response error" when the primary color was left on its default. (DIS-24138) * The in-app Help panel could list changelog releases instead of documentation, and showed a "This page requires authentication" notice on articles you were already signed in to read. (DIS-24087, DIS-24088) * **General bug and security fixes** across facility deletion, the dashboard's Customize menu, facility search, file transfer scanning and cancellations, access updates to regions, wicket reboot notices, multi-factor authentication, and virtual desktops. --- # 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-23.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.