> 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/get-started/key-terminology.md). # Key Terminology ### Access Window A scheduled time frame during which authorized users are permitted to remotely access authorized end devices at a specified facility. Outside of this window, access is automatically denied. *** ### Browser Connect Session Clientless Browser Connect Sessions allow for direct access to devices within facilities. Browser Connect Sessions allow for rapid access downstream. *** ### ACL (Access Control List) Rules Granular access policies that specify which users can access which end devices, and through which ports and protocols. *** ### Dashboard Dispel’s administrative web portal found at [app.dispel.com](https://app.dispel.com), where administrators can manage user access and permissions. Users can also reserve and launch Virtual Desktops or Browser Connect sessions to securely connect to remote end devices. *** ### Facility A physical or virtual location—such as a factory, plant, or network site—that is accessed and managed through Dispel’s platform. Facilities are remotely accessed through Dispel via a Wicket. *** ### Golden Image A pre-configured Windows image used to create Virtual Desktops. It can include specific applications, security settings, and system configurations. *** ### Region An individual remote access network hosted by Dispel. Each Region contains the infrastructure needed to support secure connections to end devices and is where Facilities connect via a Wicket. Regions are geographically distributed to improve performance and support compliance requirements. *** ### Stack A collection of Virtual Desktops built from a golden Windows image. *** ### Virtual Desktop (VDI) A temporary, cloud-hosted Windows machine provisioned through the Dispel Dashboard. Virtual Desktops provide users with secure, isolated environments to remotely access authorized end devices. Each VDI is non-persistent—it is created for a specific session duration and automatically destroyed afterward, ensuring a clean and secure workspace for every use. *** ### Virtual Desktop Reservation A temporary assignment of a Virtual Desktop to a specific user. When a reservation is made, the user’s unique access profile is applied, and the desktop is locked for use by that user only. The Virtual Desktop remains available for the duration of the reservation, after which it is deleted. A new desktop is then automatically rebuilt and added back to the Stack. *** ### Wicket A virtual or hardware appliance that links a Facility to a Dispel Region. It acts as a bridge between on-site networks and Dispel’s remote access infrastructure, allowing users to reach end authorized devices via Dispel. --- # 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/get-started/key-terminology.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.