> 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/elevator-cars/high-level-interface-elevator-cars/performing-executive-overrides.md).

# Performing executive overrides

### Introduction

This procedure enables an operator with the "Overrides" privilege to send individual lift cars to selected floors by performing an executive override.

**Notes:**

* This procedure can only be performed on **Schindler** and **Otis Modbus** lift systems.
* The operator is required to select an Access Zone (floor) to send the elevator car to. Ensure the operator is assigned the correct operator privileges in order to view all Access Zones.

There are two methods for performing executive overrides:

* using the Properties window, or
* using the Context menu

***

### Procedure

Use one of the following methods to perform an executive override:

<details>

<summary>Using the Properties window</summary>

1. Click **Configure** from the menu bar, then **Elevator Cars**.

   The **Elevator Car** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. **Right click** on the required elevator car and select **Properties**.
3. Click the **Status and Overrides** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-49d2ae262f647feebec9eb273dfe0a3473abf7b4%2Felevatorcarhli_overridestab.png?alt=media)
4. Select the appropriate **Destination floor** from the drop-down list.

   **Note:** If an Access Zone has not been assigned to a floor, this means the floor is free access, (i.e. anyone can access this floor). See [Configuring an Elevator Car HLI](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/elevator-cars/high-level-interface-elevator-cars/configuring-an-elevator-car-hli.md) for the procedure.
5. Click the **Go** button to send the Elevator Car HLI to the selected floor.
6. 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.

</details>

<details>

<summary>Using the Context menu</summary>

1. Click **Configure** from the menu bar, then **Elevator Cars**.

   The **Elevator Car** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. **Right click** on the required Elevator Car HLI and select **Go to Floor...**

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c7c387f08236f8e55cda67aeee0c32ef78678908%2Felevatorcarhli_gotofloor.png?alt=media)
3. Select the appropriate **Destination floor** from the context menu.

   The Elevator Car HLI will be sent to the selected floor.

   **Note:** Alternatively, you can select **Override...** from the context menu to display the **Status and Overrides** tab of the selected Elevator Car HLIs property pages.

</details>

### Result

When an override is requested, the elevator car will be sent to the requested floor, (e.g. Floor 5). This is dependent on the HLI protocol used, for example:

If the car has already been sent to a floor, the car will travel there before travelling to the requested floor, (e.g. Floor 3 then on to Floor 5).


---

# 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/elevator-cars/high-level-interface-elevator-cars/performing-executive-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.
