> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/prepay-car-parking/configuring-the-prepay-car-parking-feature/configuring-doors.md).

# Configuring Doors

This topic describes how to configure an entry Door and exit Door for the Car Park. The entry Door will report entry events and the exit Door will report exit events.

Once assigned to a Car Park, these Doors will provide full traceability of Cardholder access in and out of the Car Park.

**Notes:**

* A Door is required at each access point to operate the barrier arm.
* If required, a special Door (i.e. VIP Entrance) can be configured that allows access for specific Cardholders only. Create the Door. Assign a separate Access Zone as the entry zone for the Door. Allow only specific Cardholders access to this zone.

#### Configuring the entry Door

To configure the entry Door, perform the following procedure:

1. Click **Configure** from the menu bar, then **Doors**.

   The Door List Window opens.
2. Right click and select **New\...Door**.

   By default the **General** tab displays.
3. Type in the **Name**, **Description** and select the **Division**.
4. Click the **Event Response** tab, and assign a primary Alarm Zone for all events.
5. Click the **Connections** tab, and select the Controller that will host this Door.

   **Note:** Select the Controller with the majority of Door hardware assigned to it. It is preferable to have all Door hardware on the same Controller.
6. Click the **Devices** tab, and assign the appropriate Inputs and Outputs for the Door.

   For a description of each of the devices that can be assigned to the Door, refer to the topic [Creating Doors](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/doors/creating-doors.md).
7. Click the **Entry Zone** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-823d21f3bbabfd6923ff948189eee4ae7fe6b086%2Fdoor_entryzonetab1.png?alt=media)
8. Select the the 'Staff Car Park 1 Access Zone' from the **Access Zone** drop-down list.

   Cardholders will enter into this Access Zone.
9. Select the **Reader(s)** radio button, to ensure entry is controlled by a reader.
10. Select the 'Door 1 Entry Reader' from the **Reader(s)** drop-down list.

    Entry will be controlled by this reader.
11. Click the **Icons** tab, and select the Standard Barrier Arm Icons Icon Set.
12. Click **OK** to exit and save your changes.

    Click **Apply** to save your changes and stay in this window.

    Click **Cancel** to exit without saving your changes.

#### Configuring the exit Door

To configure the exit Door, perform the following procedure:

1. Repeat Steps 1-6 of the procedure above.
2. Click the **Entry Zone** tab and select the 'Staff Car Park 1 Access Zone' from the **Access Zone** drop-down list.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-cffecda8d72e18931385b3bb1f17642528446faf%2Fexitdoor_entryzonetab.png?alt=media)
3. Click the **Exit Zone** tab and assign the 'Door 2 Exit Reader' as the exit reader for the Door, by selecting it from the **Reader(s)** drop-down list.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-4691f518d71e5a0052bfcf3c426f3b9e6df5a940%2Fexitdoor_exitzonetab.png?alt=media)

   **Note:** An Exit Zone Access Zone is not required.


---

# 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://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/prepay-car-parking/configuring-the-prepay-car-parking-feature/configuring-doors.md?ask=<question>&goal=<user_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.
