> 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/getting-started-with-dispel/facility-admin-quick-start-guide.md). # Facility Admin Quick Start Guide The core tasks for a Facility Admin: manage members, set device ACLs, grant and manage access windows, apply changes in bulk with groups, and connect to devices. A Facility Admin manages everything inside a single facility: its members, the devices those members can reach, and the access windows that let them connect. This guide covers those tasks in the order you'll usually do them, from adding your first member to connecting to a device yourself. Each step links to a full how-to. ## Add and manage facility members Everyone who needs a device ACL or an access window has to be a member of the facility first. From [**Facilities**](https://app.dispel.com/facilities), open the facility and go to its **Groups and Members** tab to add a member, change a member's facility role, or remove someone from the facility. To add a member, select **Add members**, enter the person's email, and select **Add this user**. If the email matches someone who already has an account in your organization, they're added to the facility right away. If it doesn't, the person receives an email invitation, creates their Dispel account from it, and is added to the facility once that account exists. {% content-ref url="/pages/P0f4nzcWV4u7gdw79WBK" %} [Add a User to a Facility](/build-your-environment/infrastructure/deployment-infrastructure/facilities/add-a-user-to-a-facility.md) {% endcontent-ref %} ## Grant device access with ACLs A device ACL gives a user access to specific protocol-and-port combinations on a device. Assign ACLs from a device's **Remote Access** tab when you're granting many users access to one device, or from a user's **Devices** tab when you're granting one user access to many devices. Each combination shows as a pill, for example TCP (443), that turns green once it's granted. A user appears in a device's access list after they join the facility that contains the device, and the device's protocols and ports have to be configured before you can grant access to them. {% content-ref url="/pages/ec3x27h3lkamFyKUKIiP" %} [Device access (ACLs)](/build-your-environment/infrastructure/device-management/device-access-acls.md) {% endcontent-ref %} ## Create and manage access windows Depending on your organization's settings, users may need an active access window before they can connect. From [**Access Windows**](https://app.dispel.com/access-windows), select **Create Access Window**, then choose a facility, a schedule, the members or groups it covers, and the devices, protocols, and ports they can reach. Because you're creating the window rather than requesting it, it opens in **Approved** status right away instead of waiting for approval, and its members get access for the scheduled period. Open a window later to rename it, change its schedule, add or remove the users and groups it reaches, or revoke it to end access. {% content-ref url="/pages/mOV62fiPGAficJuFZowP" %} [Create an approved access window](/connect-to-your-systems/access-windows/create-an-approved-access-window.md) {% endcontent-ref %} {% content-ref url="/pages/1tR2u1XiD7bgnFrXSUdk" %} [Manage an access window](/connect-to-your-systems/access-windows/manage-an-access-window.md) {% endcontent-ref %} ## Apply changes in bulk with facility groups When several people need the same facility role, the same device ACLs, or the same access window, a facility group lets you set it once and apply it to everyone in the group. From [**Member Groups**](https://app.dispel.com/groups), select **Add Group**, then **Add Facility Group**. Add members by selecting organization members or pulling in an organization group, then assign the group's facility role, device ACLs, and access windows from its **Permissions**, **Access**, and **Access Windows** tabs. {% content-ref url="/pages/pYM9olmPFPvSKeeSykat" %} [Facility Groups](/manage-users-and-access/groups/facility-groups.md) {% endcontent-ref %} ## Connect to a device yourself You can reach devices the same way your users do. Reserve a virtual desktop from a stack and connect with the RDP file or in the browser, or start a Browser Connect session from a device. Depending on your organization's settings, reserving a desktop or opening a session can require an active access window. {% content-ref url="/pages/F5VR2ahbR8RlmFvqxNfv" %} [Reserve a Virtual Desktop (Admin)](/connect-to-your-systems/connection-methods/virtual-desktops/reserve-a-virutal-desktop-admin.md) {% endcontent-ref %} {% content-ref url="/pages/UzR1OhUnxYiRGGaCbnnu" %} [Connect to a Browser Connect Session (Admin)](/connect-to-your-systems/connection-methods/browser-connect/connect-to-a-browser-connect-session-admin.md) {% endcontent-ref %} --- # 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/getting-started-with-dispel/facility-admin-quick-start-guide.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.