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

# 8.0.16 — 6 March 2026

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

**Dispel Zero Trust Engine 8.0.16**, including Orchestrator 1.6.8.

{% 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

* [Integrations](https://docs.dispel.com/integrate-and-administer/integrations/asset-discovery) are a section of their own, and Dispel can read your asset inventory from Nozomi Networks, Dragos and Forescout eyeControl. Devices found that way arrive with the vendor's own detail attached, and each integration syncs on a schedule. (DIS-17804, DIS-17899, DIS-18595)
* The [devices list](https://docs.dispel.com/build-your-environment/infrastructure/device-management) has been rebuilt: filterable columns, a detail panel that opens beside the table, and the fields an integration contributed shown on the device itself. (DIS-17817)
* [Session Forensics](https://docs.dispel.com/monitor-and-investigate/risk-factor-analysis) scores each sign-in on the behavior behind it and keeps a baseline of what is normal for the account, so an unusual session stands out from a routine one. (DIS-17433)
* A Browser Connect utilization [report](https://docs.dispel.com/monitor-and-investigate/reports) covers historical connections and the highest number of concurrent sessions reached each day. (DIS-17455, DIS-17352)
* Facilities appear on a map, with their wickets and health beside them. (DIS-17723)
* A wicket can belong to more than one facility. (DIS-15569)

## Bug fixes

* Access request approvers who had turned email off still received it. (DIS-17997)
* Quick Connect settings were not always applied. (DIS-17879)
* A wicket firewall rule would not accept a port range. (DIS-17355)
* Importing devices in bulk, and deleting them, could fail. (DIS-18182)
* Creating a device could fail, including from the facilities page, and opening Remote Access on a newly created device could close the page. (DIS-18803, DIS-18256)
* The Topology tree could take a long time to load, or leave devices out. (DIS-17985)


---

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