> 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/site-installation/access-zones/configuring-pushbutton-overrides.md).

# Configuring Pushbutton Overrides

### Introduction

The pushbutton override feature can be used to temporarily set an Access Zone (or an elevator floor) to free access for a defined period of time to allow visitors to travel to the correct floor in a building.

**For example:**

On arrival at an apartment building, a visitor calls the apartment they wish to visit using the intercom system. To allow the visitor entry, the tenant activates a pushbutton which unlocks the apartment building front door and enables the elevator floor button for the required floor.

This procedure allows you to configure a pushbutton override and the time period that the zone will be in free access.

### Procedure

1. Click **Configure** from the menu bar, then **Access Zones**.

   The **Access Zone** 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. Highlight the Access Zone you want to configure pushbutton override functionality for.
3. **Right click** and select **Properties**.
4. Click the **Triggered Overrides** tab.

   **Notes:**

   * By default the **Lockdown Override** radio button is enabled.
   * This tab allows you to configure EITHER pushbutton overrides OR lockdown functionality for an Access Zone, (i.e. you cannot use both features for the one zone).

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f9727f38ab430809e289cdb12f0489844a2d9d84%2Faczone_triggeredoverridestab.png?alt=media)
5. Click the **Push Button Override to Mode 2** radio button.

   The fields in this section of the screen become enabled.
6. Set the override time, (i.e. how long the zone will be in free access), in the **Duration** field.

   **Note:** The default time is 5 minutes.
7. Drag (or copy and paste) the input source required to initiate the override into the grid.

   **Note:** The input source can be an input, an output, a virtual output or a logic block.
8. 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.
9. All Access Zones (or elevator floors), in the building need to have an input source assigned to them to perform the override function. Therefore, repeat Steps 2 - 8 for every Access Zone.

### Result

The pushbutton override feature has been configured for the building.

### Hint

{% hint style="info" %}
**Event Reporting**

By default, the pushbutton override will NOT generate an event. However, if you do require events to be generated, this can be achieved by setting up Action Plans for the input sources, (i.e. inputs, outputs, virtual outputs and/or logic blocks) used for pushbutton overrides, as follows:

1. Open the properties for the input source.
2. Click the **Event Response** tab.
3. Assign the appropriate Action Plan to the 'Closed' Event Group.
4. Repeat Steps 1 - 3 for each input source used for pushbutton overrides.
   {% endhint %}


---

# 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/site-installation/access-zones/configuring-pushbutton-overrides.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.
