> 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-06-10.md).

# 8.7.0 — 10 June 2026

What changed in Dispel in the release of 10 June 2026.

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

* A [recording](https://docs.dispel.com/monitor-and-investigate/logs) carries an activity timeline beside the player: every event in the session in order, with the idle periods marked. (DIS-20315, DIS-20563)
* The settings navigation collapses to a rail on its own, opens on hover or with a keystroke, and becomes a dropdown on a small screen. (DIS-21017)
* A device set up for Browser Connect over RDP can be configured to connect in administrative console mode, under the device's advanced settings. (DIS-20873, DIS-20852, DIS-20856)
* Building a [stack](https://docs.dispel.com/connect-to-your-systems/connection-methods/virtual-desktops/stacks) uses a single form, whichever page you start from. (DIS-20895)
* Importing devices reports the duplicates and the multiple addresses it found rather than dropping them, and reads ports and protocols from every integration. (DIS-20933)
* [Compliance](https://docs.dispel.com/secure-and-govern/overview) now sits under Security, with the framework views consolidated into one place. (DIS-20797)
* The [Topology](https://docs.dispel.com/monitor-and-investigate/topology) map carries its basemap, perspective and health-legend controls on the canvas. (DIS-20919)

## Bug fixes

* A registered security key was not always recognized as a second factor in the console. (DIS-20801)
* A Browser Connect session over RDP could hang for about a minute when connecting with a domain account. (DIS-20718)
* Releasing control of a session could leave the owner unable to take it back, and releasing it could leave you still holding it. (DIS-20945, DIS-20935)
* An SFTP download could fail to find its own file. (DIS-20908)
* Creating a stack could reject a valid schedule. (DIS-20241)
* The Topology map could render with no facility pins, the tree could leak stacks into it, and the list view could fail to load. (DIS-21075, DIS-20932, DIS-20902)
* The dashboard did not lay out correctly on a phone for organizations with no access windows. (DIS-20507)
* **General bug and security fixes** across permission handling, session control updates, MFA exemptions, organization settings, transfer indicators, device subnet prompts, compliance evaluation, log delivery, and the groups page.


---

# 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-06-10.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.