> 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-07-27.md). # 8.10.0 — 27 July 2026 What changed in Dispel in the release of 27 July 2026. **Dispel Zero Trust Engine 8.10.0**, including Orchestrator 1.18.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 * Quick Actions is a command palette: press ⌘K (Ctrl+K on Windows) anywhere in the console, type what you are looking for, and go straight to it. The shortcut works regardless of keyboard layout. (DIS-22343, DIS-22589) * An organization can set how long a gap in a [recording](https://docs.dispel.com/monitor-and-investigate/logs) counts as idle. (DIS-21697) * The SFTP download form mirrors the upload form — source folder and file name as separate fields — and the SMB share directory field says what format it expects. (DIS-22160, DIS-22336) * Module access continues for 30 days after a service period ends, rather than stopping on the day. The account team link on [Billing](https://docs.dispel.com/integrate-and-administer/billing) is now **Your Dispel Team**. (DIS-22710, DIS-22706) * Browser Connect shows a dedicated notice when a session is being recorded, and an organization can turn that notice on or off. (DIS-21793) * A Session Forensics event and the baseline it was scored against can be [exported as JSON](https://docs.dispel.com/monitor-and-investigate/data-exports). (DIS-21961) ## Bug fixes * A deleted device could still appear in Topology and in device details. (DIS-22214) * A Browser Connect session over RDP could stay on a black screen rather than reporting the error behind it, and the credential prompt could hang when the domain field was left empty. (DIS-21858, DIS-21857) * Quick Actions could leave an invisible layer over the page after navigating from a page with a panel open, and expanding an item in it could trap the keyboard. (DIS-22372, DIS-22401) * The Claroty xDome connection test could report a working integration as unreachable. (DIS-22301) * Billing could show line items from another order, miss Browser Connect counts against the quota, attach a service period to hardware, name the wrong account manager, and lag behind a newly linked record. (DIS-22711, DIS-22712, DIS-22714, DIS-22713, DIS-22715) * A device whose address was entered in an invalid form could stop access changes from propagating, and changing a device's address might not update the Browser Connect connection to it. (DIS-21810, DIS-21923) * The **Resend invite** button did nothing. (DIS-21845) * **General bug and security fixes** across group management, Session Forensics organization linking, OIDC group synchronization, invitations, session lifecycle, virtual desktop logging, translations, branded favicons, Nozomi sync limits, and Topology's save controls. --- # 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-07-27.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.