> 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-12.md).

# 8.11.0 — 12 August 2026

What changed in Dispel in the release of 12 August 2026.

**Dispel Zero Trust Engine 8.11.0**, including Orchestrator 1.20.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

* Dates and times throughout the console now show in your own time zone by default, with the UTC value on hover. (DIS-22988)
* File transfers no longer appear in the Topology tree view. They remain in the list view. (DIS-22948)
* The base color palette has been refreshed. (DIS-22779)
* The appearance and color mode picker has moved into the user menu, and is reachable from Quick Actions. (DIS-22745)
* Stacks no longer appear in Topology's tree view. They remain in the list and on the map. (DIS-21812)
* Wickets in a dedicated cloud region use a default MTU that suits the path they actually take. (DIS-20708, DIS-21362)
* A wicket's host firewall is off by default, since access is already governed by the rules Dispel applies to it. (DIS-21354)
* Wicket patching reads the fleet once a day rather than on every sweep, so a large deployment is not kept busy checking itself. (DIS-22826)

## Bug fixes

* Stacks could stay in a building state after a bridged region was upgraded. (DIS-22240)
* A region with more than 200 facilities showed none of them, and an advanced filter drew only the first 20. (DIS-22891)
* Sign-ins through Microsoft and SSO could be recorded in the logs as failures. (DIS-22731)
* A CSV uploaded in an encoding other than UTF-8 rendered accented characters as replacement glyphs. (DIS-22717)
* A stopped wicket could hold up the fleet sweep behind it. (DIS-22815)
* **General bug and security fixes** across access window and group permissions, Topology's search and rendering, Browser Connect session indicators, virtual desktop dialogs, access request errors, and device search pagination.

## Closed Beta

Switched on for selected organizations while we finish it.

* **Consolidated session and recording chrome.** Browser Connect sessions and recording playback share one window frame: a single action bar, a collapse-everything control, picture-in-picture, and per-protocol keyboard shortcuts. (DIS-23001)


---

# 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-12.md?ask=<question>&goal=<user_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.