> 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/integrated-systems/aperio-integration/gallagher-command-centre-site-configuration/creating-an-aperio-door.md).

# Creating an Aperio Door

### Introduction

This procedure describes how to create an Aperio Door in Gallagher Command Centre.

***

### Configuration

To configure an Aperio Door, perform the following procedures in Gallagher Configuration Client:

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

   The **Hardware** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
2. **Right click** and select **New\...Aperio Bus Devices** > **Aperio Door.**

   By default the **General** tab displays.
3. Complete the fields as required.

   For further detail see [General tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.md).
4. Click the **Event Response** tab, and configure as required.

   For further detail see [Event Response tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/event-response-tab.md).
5. Click the **Alarm Instructions** tab, and configure as required.

   For further detail see [Alarm Instructions tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/alarm-instructions-tab.md).
6. Click each tab in turn to configure the door:

<details>

<summary>Connections tab</summary>

1. Click the **Connections** tab.

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

   These fields are "read-only" and will be populated once you assign this door to a device, which is explained later in this procedure.

</details>

<details>

<summary>Configuration tab</summary>

1. Click the **Configuration** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-abf00b0847cbf2ac61b342d42e5b0161f58f078b%2Fdoorproperties_configuration.png?alt=media)
2. The following checkboxes are available:

   <table><thead><tr><th width="168">Option</th><th>Function</th></tr></thead><tbody><tr><td>Door has keypad</td><td><p>It is recommended that this checkbox is ticked whenever the associated door has a keypad.</p><p>If the door has a keypad and this is not ticked, then Command Centre may deny access without waiting for a PIN to be entered, when the Access Zone is in PIN mode. When this checkbox is ticked, it enables the <strong>PIN is user code</strong> option.</p></td></tr><tr><td>PIN is user code</td><td>The user is allowed through the door using the User Code number assigned to their cardholder record.</td></tr><tr><td>Require MIFARE Enhanced Security encoded cards</td><td><p>When ticked, the reader is instructed to only accept MIFARE Classic cards that have the enhanced security data when deciding whether to grant a cardholder access. The MIFARE Enhanced security key is configured on the <strong>Card Security</strong> tab of the Server Properties.</p><p><strong>IMPORTANT:</strong></p><p>Leave this checkbox unchecked in the following situations:</p><ol><li>When not using the MIFARE Enhanced Security feature or when not using it for part of a site.</li><li><p>When some cardholders requiring access using this reader have not yet had their cards re-encoded. It is important to remember to enable the setting once all cards have been re-encoded.</p><p>Disabling this setting will also allow cards encoded at sites using the MIFARE Enhanced Security feature to be used at sites who are not using this feature.</p><p>Cards not encoded using the MIFARE Enhanced Security feature will be denied access with an event saying <em>"Denied - MIFARE High Security Card Required at [Door]”</em>. To enable the card to gain access at the door, uncheck the checkbox for the Door Reader.</p></li></ol></td></tr><tr><td>Use MIFARE Serial Number as Card Data</td><td>When ticked, the reader is instructed to read the MIFARE Classic Card Serial Number (CSN). The CSN is used to identify a Cardholder in Command Centre.</td></tr></tbody></table>

   **Notes:**

   * The **Require MIFARE Enhanced Security encoded cards** and **Use MIFARE Serial Number as Card Data** options cannot be used at the same time, therefore when one of these checkboxes is ticked, the other checkbox is disabled. However, **PIN is user code** can be used in conjunction with either option.
   * An Aperio lock is configured using the Aperio PAP to read either a MIFARE Classic sector 1 to 15, or to just read the MIFARE Classic Serial Number (CSN). The second checkbox should only be ticked if the Aperio lock has been configured to read the Card Serial Number (CSN). When using a MIFARE sector it is important that all cards for your site have their Gallagher data encoded onto the same sector.
3. When using the CSN, you will need to specify a Card Type to be used with this door.

   Click the **Card Type** drop-down list and select the correct Card Type.
4. Click the **Entry Access Zone** drop-down list and select the zone you enter into.
5. If you want to configure **Double card overrides** for this Aperio Door, refer to [Configuring Local Overrides at Card Readers](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/status-and-overrides/configuring-local-overrides-at-card-readers.md) for the procedure.

</details>

<details>

<summary>Advanced tab</summary>

1. Click the **Advanced** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-b9e0e0a37126d4e73943b52629dfea96602005c4%2Faperio_advanced_tab.png?alt=media)
2. Configure the Aperio Door timeouts as required.

   <table><thead><tr><th width="264">Option</th><th>This setting determines...</th></tr></thead><tbody><tr><td>Card to complete action must be presented within</td><td><p>either:</p><ul><li>the maximum time between card swipes for Dual Authorisation,<br><strong>OR</strong></li><li>the time between pressing a function key on a keypad reader and badging the card for an Access Zone or Alarm Zone override.</li></ul><p>(Default = 10 seconds. Valid range = 1-99 seconds)</p></td></tr><tr><td>Door warns 'Open Too Long' if still open after</td><td><p>when the open warning output turns on and when the status of the door changes to show that it has been open too long.</p><p>(Default = 20 seconds. Valid range = 0-9999 seconds)</p><p><strong>Note:</strong> This cannot be set as greater than the alarm time, (i.e. the <strong>Door is 'Open Too Long'</strong> <strong>time</strong>). If it is, and you attempt to save the door, the following error message displays:</p><p><em>"The 'Open Too Long' warning time must be less than or equal to the 'Open Too Long' alarm time."</em></p></td></tr><tr><td>Open warning</td><td>the Output to activate when the door has been open too long.</td></tr><tr><td>Door is 'Open Too Long' if still open after</td><td><p>when a 'Door Open Too Long' alarm is generated.</p><p>(Default = 20 seconds. Valid range = 5-9999 seconds)</p></td></tr><tr><td>Door is 'Forced Open' if opened unexpectedly</td><td>whether or not a Forced Door alarm will be generated if the open sensor (if the lock has it) detects the door is opened.</td></tr><tr><td>Door unlock time</td><td><p>the maximum time the Unlock relay is energised.</p><p>(Default = 5 seconds. Valid range = 1-86400 seconds (24 hours))</p></td></tr><tr><td>Extended Access time</td><td><p>the period of time the door will remain unlocked for in addition to the <strong>Door unlock time</strong>, for cardholders who require it (e.g. disabled people, couriers, delivery vehicles).</p><p><strong>Note:</strong> For further detail about extended access time, and how to identify cardholders that require special access, see <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/doors/configuring-extended-access-time-for-a-door.md">Configuring extended access time for a Door</a>.</p><p>(Default = 25 seconds. Valid range = 0-86400 seconds (24 hours))</p></td></tr></tbody></table>

</details>

7. Click the **Cameras** tab if you want to associate a DVR Camera(s) with this Aperio Door.

   For further details see [Cameras tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/cameras-tab.md).
8. Click the **Icons** tab if you want to change the Icon Set for this Aperio Door.

   For further details regarding the **Icons** tab, see [Icons](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/icons.md).
9. Click the **Custom Fields** tab if you want to add and assign a custom field value to this Aperio Door.

   For further details regarding the **Custom Fields** tab, see [Custom Fields](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/custom-fields.md).
10. Click the **Notes** tab if you want to add a note(s) about this Aperio Door.

    For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
11. Click **OK** to exit and save your changes.

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

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


---

# 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/integrated-systems/aperio-integration/gallagher-command-centre-site-configuration/creating-an-aperio-door.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.
