> 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-03-20.md).

# 8.1.0 — 20 March 2026

What changed in Dispel in the release of 20 March 2026.

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

* [Browser Connect](https://docs.dispel.com/connect-to-your-systems/connection-methods/browser-connect) reaches HTTP and HTTPS targets, streams the session to everyone watching, and lets the owner hand control to another participant and take it back. (DIS-17790)
* The devices table sorts by Connect, so the devices you can reach can be brought together. (DIS-18234)
* Choosing a facility on an access request is a searchable list rather than a dropdown. (DIS-18557)
* Devices show the manufacturer's logo in the table. (DIS-18297)

## Bug fixes

* A Browser Connect session could fail to open in Safari, and enabling or deleting a connection could load indefinitely. (DIS-18788, DIS-18840, DIS-18517)
* **General bug and security fixes** across permission handling, Browser Connect sessions and ports, the devices list's search, sorting and editing, the facilities and groups lists, File Transfer, the members page, Session Forensics scoring, stack builds, and light mode contrast.


---

# 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-03-20.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.