> 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/earlier-releases/2024-09-05.md).
# 5 September 2024
Enhanced Access Window Management: Simplified Setup and Efficient Membership Tracking
## 5 September 2024
{% hint style="info" %}
Published on dispel.com.
{% endhint %}
## Enhanced Access Window Management: Simplified Setup and Efficient Membership Tracking
Coming October 8th, we've made several improvements to simplify the creation, organization, and ongoing management of Access Windows and their memberships.
Assigning the right people to Access Windows they need is now quicker and easier than ever. Each Access Window can accommodate multiple users. You can add individual users, entire Dispel groups or a combination of both to each Access Window. To balance access control and setup convenience, administrators can toggle access on and off for individual users within a group while preserving access for all other group members.
To make finding, understanding, and managing your Access Windows incredibly quick and simple, you can give Access Windows meaningful names and track their membership on Access Window details pages, in individual user settings pages, and in group settings pages.
### Fixes & Improvements
* Fixed an issue affecting Bastion Link generation
* Enabled Bastion connections through the RDP client (Windows Only)
* Improved clarity of error messages throughout the Dashboard
* Added ability to specify email addresses in addition to domains for Vendor Self Onboarding links
* Fixed bugs and addressed usability issues in the Vendor Self Onboarding workflow
* Improved MAC address identification and handling during device import
* Updated query performance and accuracy of the Nozomi Networks device import integration
---
# 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/earlier-releases/2024-09-05.md?ask=&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.
