> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/owners-playbook/data-and-security/autonomous+-monitoring/door-access-providers.md). # Door Access Providers ### Overview Door Access Providers control how Customers physically enter your facility and courts. Each court (pod) is assigned an access provider that unlocks the correct doors when a Customer checks in to a Reservation or Event. PodPlay supports several providers so you can use the door lock system already installed at your venue. ### Available Providers PodPlay integrates with the following door access systems: * [**KISI**](https://www.getkisi.com/?utm_term=kisi%20locks\&utm_campaign=Google_Paid_Brand\&utm_source=adwords\&utm_medium=ppc\&hsa_acc=5069622900\&hsa_cam=9513822431\&hsa_grp=96009779694\&hsa_ad=426109625709\&hsa_src=g\&hsa_tgt=kwd-2390056415914\&hsa_kw=kisi%20locks\&hsa_mt=p\&hsa_net=adwords\&hsa_ver=3\&gad_source=1\&gad_campaignid=9513822431\&gbraid=0AAAAACeNmF6uUxy47wJKgvvmswmLMp6m6\&gclid=Cj0KCQjw77bPBhC_ARIsAGAjjV_wWqBHJd5EgwVqNul_wIZMv6hxuDVItZoVr1tHFItQwpD-SC8EAQ4aArIpEALw_wcB) – A cloud-based access control system. Available for all venues by default. * [**Remote Lock**](https://remotelock.com/direct/?creative=649694770050\&keyword=remotelock\&matchtype=b\&network=g\&device=c\&utm_source=ppc\&utm_medium=ppc\&utm_campaign=remotelock_branded\&utm_content=649694770050\&utm_term=remotelock\&hsa_acc=1510685209\&hsa_cam=16182827238\&hsa_grp=135842544440\&hsa_ad=649694770050\&hsa_src=g\&hsa_tgt=kwd-11735204945\&hsa_kw=remotelock\&hsa_mt=b\&hsa_net=adwords\&hsa_ver=3\&gad_source=1\&gad_campaignid=16182827238\&gbraid=0AAAAACado1nssNl7nZLg2Aizi3Or12X0L\&gclid=Cj0KCQjw77bPBhC_ARIsAGAjjV-_-Wgr4mDccfTI-LTVlk7WdD8Y_kUBgwtl-LflfKOkQcGLwvJB1y0aAv0TEALw_wcB) – A smart lock management platform. Available for all venues by default. * **OpenPath** – A mobile-first access control system. Appears as an option once your OpenPath organization is configured in Company Settings. * [**PDK**](https://www.prodatakey.com/) – A cloud-based access system commonly used for perimeter and interior doors. Appears as an option once your PDK system is configured in Company Settings. * [**Verkada**](https://www.verkada.com/l/cloud-access-control/?utm_h1=\&utm_source=aw\&utm_medium=search\&utm_campaign=701Uu00000ePBu5IAG\&utm_content=NA-Search-Brand\&utm_term=verkada%20door%20access\&gad_source=1\&gad_campaignid=12979026470\&gbraid=0AAAAADH5oQ5puDOWDrHbv7TgpYOz8DKjw\&gclid=Cj0KCQjwr4jSBhCSARIsAOX1E-JfAqjg8qtWgwMlqJ2gdsjs-uNX7TgQsUy5F7qQls6Ji2Iqjt9diWAaAopAEALw_wcB) – An access control platform with cloud-managed door locks. Appears as an option once your Verkada region and API key are configured in Company Settings. **PLEASE NOTE:** KISI and Remote Lock are always available as options. OpenPath, PDK, and Verkada only appear in the provider list after an administrator has configured the integration in **Company Settings > Integrations**. ### Assigning an Access Provider to a Court Each court needs an access provider and at least one lock ID so that PodPlay knows which doors to unlock when a Customer checks in. * Open **Venues** in the Dashboard * Select the **Venue** that contains the court you want to configure * Select the **Court** (pod) you want to edit * Go to the **Access** tab * Under **Locks**: * Select the **Access Provider** from the dropdown * Enter or select the **Lock IDs** for the doors associated with this court ### How Lock IDs Work The Lock IDs tell PodPlay exactly which doors to unlock. How you enter them depends on the provider: * **KISI and Remote Lock** – Enter lock IDs manually as a comma-separated list (for example: `lock-123,lock-456`). * **PDK** – A device picker appears that lists all available PDK devices. Select one or more devices from the list. * **Verkada** – A door picker appears that lists all available Verkada doors. Select one or more doors from the list. * **OpenPath** – Enter lock IDs manually as a comma-separated list. ### Access Instructions Below the Locks section on the Access tab, you can set **Access Instructions HTML**. These instructions are included in the RSVP emails sent to Customers, telling them how to enter the facility (for example, "Use the PodPlay app to unlock the front door" or "Enter code 1234 on the keypad"). * Enter your instructions in the HTML editor * Save the court settings ### Configuring Verkada Integration Before Verkada appears as an access provider option, an administrator must set up the integration: * Open **Company Settings** * Go to the **Integrations** tab * Find the **Verkada** section * Select your **Region** (US, Europe, or Australia) * Enter your **Verkada API Key** * Save the configuration Once configured, **Verkada** will appear in the Access Provider dropdown when editing courts, and a door picker will show all available Verkada doors for easy selection. {% hint style="info" %} If you need to set up OpenPath, PDK, or other integrations, please contact the Customer Success team for assistance. {% endhint %} ### Tips * Make sure every court has an access provider and at least one lock ID configured before going live * Test door unlocks after initial setup to confirm everything is working * If you change door hardware or lock systems, remember to update the access provider and lock IDs for affected courts * Verkada and PDK offer convenient door/device pickers — use them to avoid entering IDs manually --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.podplay.app/owners-playbook/data-and-security/autonomous+-monitoring/door-access-providers.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.