> 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-04-01.md).

# 8.2.0 — 1 April 2026

What changed in Dispel in the release of 1 April 2026.

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

* Organization admins have a dashboard of activity and usage across the organization. (DIS-18507)
* Browser Connect sessions are recorded, and the recordings are listed with thumbnails and played back in the [console](https://docs.dispel.com/monitor-and-investigate/logs) — as a grid, a list, or a timeline with expandable rows and a zoom brush. (DIS-17977, DIS-19523)
* Browser Connect sessions render through a new viewer for RDP, VNC and SSH. (DIS-18984)
* Participants in a session are grouped by who owns it, who is controlling it and who is watching. (DIS-18978)
* Wicket ISO downloads no longer expire after 30 days. (DIS-18668)

## Bug fixes

* A facility could be left without an administrator. (DIS-16083)
* An HTTP Browser Connect session did not open on the target address. (DIS-18989)
* Session controls could disappear after the session had been interacted with, the owner could be asked to take control of a device they had just connected to, and taking control could fail outright. (DIS-18843, DIS-18987, DIS-19128)
* A Browser Connect session could open the previous version of the viewer. (DIS-19162)


---

# 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-04-01.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.