> For the complete documentation index, see [llms.txt](https://docs.alloyaccess.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alloyaccess.com/introduction.md). # Introduction Get an overview of Alloy Access's features, integrations, and how to use them. Welcome! Our documentation includes guides, examples, and references to help you use Alloy Access. If you have any questions, feel free to contact our [support team](mailto:alloyaccesssupport@smartrent.com). ## Most popular
Start guide Learn how to start using the app and best practices for access controlplayRectangle 1logo.jpgSign In
Import MembersQuickly move members from your existing access control system to Access AccessimportUntitledlogo121.pngImport Members
EventsInvestigate your sites access historyUntitledfilterlogo121.pngACTIVITY
ElevatorsConfigure an elevator with Managed Floor AccessUntitledelevatorfilterlogo121.pngElevator Setup Guide
## Alloy Access Basics Start setting up your site by learning about Alloy Access's basic features.
ControllersConfigure controller hardware to build out your siteConfigure Controllers
Access ReadersMake sure your access readers are up to date on the latest firmwareAccess Readers
Panel I/OAdd I/O to controller additional doors onsiteConfigure I/O Panels
Cloud BridgesCheck to ensure the network requirments are meetCloud Bridge
SchedulesCreate schedules to validate access during specific periods Schedules
Access LevelsGroup members to define unique access permissionsAccess levels
--- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.alloyaccess.com/introduction.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 `build a script that syncs our docs to a CMS` 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.