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

# 8.0.12 — 26 January 2026

What changed in Dispel in the release of 26 January 2026.

**Dispel Zero Trust Engine 8.0.12**, including Orchestrator 1.6.4.

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

* An administrator can [reset a user's multi-factor authentication](https://docs.dispel.com/secure-and-govern/reset-multifactor-authentication) for them.
* [Access windows](https://docs.dispel.com/connect-to-your-systems/access-windows) send email notifications.
* Searching the devices, members, regions and facilities lists returns faster on large organizations. (DIS-15369, DIS-16872, DIS-15370, DIS-15366)

## Bug fixes

* A user with a pending invitation could not be added to a stack. (DIS-17023)
* Members could not be removed from a group. (DIS-1686)
* The virtual desktop reservation indicator could stop refreshing. (DIS-16942)
* Log filters were applied but not shown in the interface. (DIS-16944)
* In dark mode the accept-terms field and the reserved-desktop list could be unreadable, and notifications lost their color coding. (DIS-16943, DIS-16945, DIS-16935)
* A member's permissions page could show none of their facilities. (DIS-17249)
* The custom virtual desktop type list showed only one entry. (DIS-17301)
* **General bug and security fixes** across permission handling, the wicket health report, file share settings, and page padding on the overview screens.

## Closed Beta

Switched on for selected organizations while we finish it.


---

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