> 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/performing-overrides-on-an-aperio-door.md).

# Performing Overrides on an Aperio Door

### Introduction

These procedures describe how to temporarily override the status of an Aperio Door.

**Note:** When using double-card overrides or dual authorisation at an Aperio lock, the cardholder must wait until the Aperio LED has ceased flashing before the second card can be presented at the lock.

### Procedures

#### To enable a single/double card override for access zone

This override allows cardholders to set the door into a pre-configured ‘Mode 2’ when they badge their card, and reset it into its scheduled state when they badge it again. For example, if the scheduled state is ‘Secure - No PIN’ and Mode 2 is ‘Free - No PIN’, the first card badge will set the door into free access mode until the card is badged again, which will reset it to secure mode.

Only cardholders with the ‘Lock and unlock Access Zone’ privilege are able to do this.

1. Set Access Zone schedule and Mode 2.

   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 instructions.
2. Assign appropriate Access Groups the ‘Lock and unlock Access Zone’ privilege.

   Refer [Setting up Access Groups](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/access-groups/setting-up-access-groups.md) for instructions.
3. From the **Hardware** List Window, right-click the Aperio Door you want to perform an override on and select **Properties**.

   By default, the **General** tab displays.
4. Click the **Configuration** tab.
5. Click the appropriate override radio button, as follows:

   * **Single card override access zone** radio button to allow the override to occur when a card is badged once; or
   * **Double card override access zone** radio button to allow the override to occur when a card is badged twice.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-731e1e455789252bf4ccd113347fad47c699ad0c%2Fdoorproperties_configurationsinglecardoverride.png?alt=media)
6. Click **OK**.

   The override feature is enabled.

#### To perform a double card override for alarm zone

This override allows cardholders to arm the alarm zone configured on the selected Aperio door when they badge their card twice. Only the cardholders with the *"Change to Armed state"* and *"Change to Disarmed state"* alarm zone privileges can do this.

1. Assign the appropriate Access Groups the *"Change to Armed state"* and *"Change to Disarmed state"* privileges.
2. From the **Hardware** List Window, right-click the Aperio Door you want to perform an override on and select **Properties**.

   By default, the **General** tab displays.
3. Click the **Configuration** tab.
4. Select the **Double card arm alarm zone** radio button to allow the alarm zone to set armed when a card is badged twice.
5. Click the **OK** button.

   The arm alarm zone feature is enabled.

#### To perform a one-off override

1. From the **Hardware** List Window, right-click the Aperio Door you want to perform an override on and select **Properties**.

   By default, the **General** tab displays.
2. Click the **Status and Overrides** tab.

   Five options are available in the Override drop-down menu:

   <table><thead><tr><th width="180">Menu Option</th><th width="372">Function</th><th>Privilege Required</th></tr></thead><tbody><tr><td>Reset</td><td>Performs a software reset on the Aperio Hub that the Door is connected to.</td><td>Override</td></tr><tr><td>Shunt</td><td>Stops communication to the device (door).</td><td>Maintenance Override</td></tr><tr><td>Unshunt</td><td>Restarts communication to the device (door).</td><td>Maintenance Override</td></tr><tr><td>Open Door *</td><td>Unlocks the selected Door regardless of what status the current Access Zone is in (only supported by V3 type locks; V2 type locks do not support this functionality).</td><td>Override - Open Door</td></tr><tr><td>Clear dynamic cache</td><td>Clears the Door’s cache (saved cards).</td><td>Override</td></tr></tbody></table>
3. Click the **Override Now** button.

   From this screen you can see the status change as a result of the override.
4. Click the **OK** button.

   For further information, see [Status and Overrides](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/status-and-overrides.md).

**Notes:**

* You can also right-click the door from the **Hardware** List window and click **Open Door** to override the lock and open the door.

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

* Overrides can stay in effect until either the next automatic change (as programmed on the time schedule), or for a specified length of time entered by the operator. Overrides that have been implemented for a specified time will persist if the Server resets, or a configuration in the system occurs.


---

# 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/performing-overrides-on-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.
