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

# 8.0.11 — 8 January 2026

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

**Dispel Zero Trust Engine 8.0.11**, including Orchestrator 1.6.2.

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

* The console has a light mode and a dark mode, and an organization can set the [colors and logo](https://docs.dispel.com/integrate-and-administer/settings/branding) its members see. Each person chooses the [mode](https://docs.dispel.com/integrate-and-administer/settings/account/themes) they prefer. (DIS-16664)
* [Signing in with SAML](https://docs.dispel.com/secure-and-govern/identity-providers) has been rebuilt. The identity provider is configured on a form with a **Test Connection** button that tells you whether it works before anyone relies on it, the sign-in button reads **Sign in with Single Sign-On**, and Dispel accepts whichever authentication method your provider used rather than requiring a password. Sign-in and the provider's callback are recorded in the logs. (DIS-16195, DIS-16846, DIS-16196, DIS-16984, DIS-16473)
* Onboarding emails carry the organization identifier the recipient needs to sign in. (DIS-16474)

## Bug fixes

* Invitation links could time out. (DIS-16916)
* The documentation link could open the wrong site. (DIS-16926)

## Closed Beta

* **Firewall rules on a wicket.** Active Rules lists what a [wicket](https://docs.dispel.com/build-your-environment/infrastructure/deployment-infrastructure/wickets) is enforcing, the add-rule form writes a new one against the interfaces that wicket actually has, and a rule that failed to apply can be retried or deleted without starting over. Reordering a rule no longer rewrites the ones around it. (DIS-16326, DIS-16463, DIS-17008, DIS-17229, DIS-17078)


---

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