> 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-monitoring/status-and-overrides/performing-overrides.md).

# Performing Overrides

### Introduction

This procedure describes how to temporarily override the [*status*](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#status) of an item. The items you can perform overrides on are:

* Outputs
* Inputs
* Access Zones

  **Note:** Lockdown overrides and pushbutton overrides can also be performed on Access Zones. Refer to [Access Zone Lockdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/access-zones/access-zone-lockdown.md) and [Configuring Pushbutton Overrides](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/access-zones/configuring-pushbutton-overrides.md).
* Alarm Zones
* Fence Zones
* Logic Blocks
* Hardware items:
  * Controller 6000 or 7000
  * HBUS Reader
  * HBUS Terminal
  * HBUS Alarms Only Terminal
  * HBUS Contact Card Reader
  * HBUS I/O
  * HBUS F31/F32/F41/F42 Fence Controller
  * HBUS F22 Fence Controller
  * HBUS Z10 Tension Sensor Group
* High Level Elevator Interfaces (Elevator HLIs)
* Guard Tours

  **Note:** Refer to [Running a Guard Tour](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/guard-tours/running-a-guard-tour.md) for details on overriding, (i.e. stopping and starting) Guard Tours.
* Workstations
* Doors (including Interlock Groups)

  There are three override options for Doors, as follows:

  <table><thead><tr><th width="162">Menu option</th><th>Function</th></tr></thead><tbody><tr><td>Lock Door</td><td>This option is only available for Doors with the ‘Half-Cycle’ Lock type. After access is granted at a half-cycle door, it remains unlocked indefinitely until either it is opened and shut or the Lock Door override is used. This option can lock a half-cycle door while it is shut and unlocked.</td></tr><tr><td>Open Door</td><td>This option releases a door to allow a person to pass through. Refer to <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/status-and-overrides/open-a-door-request.md">Open a Door Request</a> for separate procedure.</td></tr><tr><td>Override Entry Access</td><td>This option opens the 'Status and Overrides' tab of the Access Zone (i.e. entry zone) that is attached to the door. If there is no entry zone this option is greyed out.<br><br><strong>Note:</strong> Overriding an entry zone will override ALL doors in that zone.</td></tr></tbody></table>

Refer to the topic Override to view the privileges required to perform an override in Command Centre.

### Procedure

**Note:** You may not be able to start an override if the target item is offline, as the override will not be immediately applied and could be lost if the target does not come online for over a minute.

1. Open the [List Window](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#list-window) of the item you want to override.
2. **Right click** on the particular item, and click **Override...** from the drop-down menu.

   The **Status and Overrides** tab on the Properties window for this item displays.

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

   **Note:** If you wish to override the access entry of a door, click **Override Entry Access** from the drop-down menu.

   The **Status and Overrides** tab on the Properties window of the Access Zone displays.
3. Click within the **Override** field and select the appropriate status from the drop-down list.

   <table><thead><tr><th width="156" valign="top">If you are overriding...</th><th>then...</th></tr></thead><tbody><tr><td valign="top">an Output, Access Zone or Alarm Zone</td><td><p>set the duration for the override to be implemented.<br>You can either:</p><ul><li>select the <strong>Until the next schedule change</strong> radio button, or</li><li>select the <strong>Until this time</strong> radio button, and enter the time of day you want the override to occur, or</li><li>select the <strong>For xx Hours, xx Minutes</strong> radio button, and enter the hours and/or minutes (this is limited to a maximum of 23 hours and 59 minutes).</li></ul><p><strong>Notes:</strong></p><ul><li>If you do not select an option, it will default until the next schedule change.</li><li>When viewing the event log, it is not possible to tell the difference between a 'time of day' override, (e.g. override until 4pm), and a duration based override, (e.g. override for 4 minutes). However, it is possible to calculate the end time for an override by adding the duration of the override to the time the override event occurred.</li></ul><p></p><p><strong>ALARM ZONES ONLY</strong><br>If an Alarm Zone <strong>fails to arm due to active</strong> alarms and the operator has either the <em>"Override"</em> or <em>"Override up to Medium Priority"</em> operator privilege, there will be an <strong>Armed (with active alarms)</strong> option available in the Override drop-down list instead of an <strong>Armed</strong> option. Privilege rules apply, (i.e. if the operator has the <em>"Override up to Medium Priority"</em> privilege, the override will only work on active alarms up to and including medium priority, and if the operator has the <em>"Override"</em> privilege they can override active alarms of any priority).</p></td></tr><tr><td valign="top">an Input</td><td><strong>Shunt:</strong> This stops communication with the Input and will remain this way until you "Unshunt".<br><strong>Unshunt:</strong> This starts polling of the Input.<br><strong>Isolate:</strong> Will isolate the Input, so that the Alarm Zone can be armed. Alarms from the Input will no longer be raised.<br><strong>De-isolate:</strong> The Input is no longer isolated.</td></tr><tr><td valign="top">a Fence Zone</td><td><strong>Shunt:</strong> This stops communication with the Fence Zone and will remain this way until you "Unshunt".<br><strong>Unshunt:</strong> This starts polling of the Fence Zone.<br><strong>On:</strong> This causes the Fence Zone to become active, (i.e. pulsing).<br><strong>Off:</strong> This causes the Fence Zone to become inactive, (i.e. not pulsing).<br><strong>High Voltage:</strong> This will change the HV/LF mode to high voltage for this Fence Zone. This override is compatible with the F31, F32, F41, F42 and F22 Fence Controllers only.<br><strong>Low Feel:</strong> This will change the HV/LF mode to low feel for this Fence Zone. This override is compatible with the F31, F32, F41, F42 and F22 Fence Controllers only.</td></tr><tr><td valign="top">a Hardware item</td><td><p><strong>Reset:</strong> This performs a software reset on the hardware item. ( Note: It is recommended you check the state of DIP Switch 2 before performing a "Reset" on a Controller.)<br><strong>Shunt (not for Controllers):</strong> This stops communication to the device, and all inputs and outputs on that device will no longer be available by the system. It will remain that way until you "Unshunt".</p><p><br><strong>HBUS READERS, HBUS TERMINALS, HBUS ALARMS ONLY TERMINALS AND HBUS I/O INTERFACES ONLY</strong><br><strong>Start Identifying Device:</strong> <em>HBUS Readers, HBUS Terminals, HBUS Alarms Only Terminals, and HBUS Contact Card Reader:</em> This causes the reader/terminal to flash amber five times and beep five times repeatedly, spaced approximately three seconds apart.<br><em>HBUS I/O Interfaces:</em> The board’s status LED will stay on until the override is cancelled. This enables an installer to identify the board within a cabinet<br><strong>Stop Identifying Device:</strong> <em>HBUS Readers, HBUS Terminals, HBUS Alarms Only Terminals, and HBUS Contact Card Readers:</em> This causes the reader/terminal to stop identifying itself.<br><em>HBUS I/O Interfaces:</em> This causes the board to stop identifying itself.</p><p><br><strong>CONTROLLERS ONLY</strong><br><strong>Disable Communication:</strong> This stops a server communicating with the Controller and remains that way until you "Enable Communication". It prevents the server from attempting to connect to the Controller, or the server from accepting contact from the Controller.<br><strong>Enable Communication:</strong> This enables a server to start communicating with the Controller.<br><strong>Enable WWW Connections:</strong> This is a timed override that allows web access to the Controller until the given expiry time, irrespective of DIP Switch 1 settings.<br><strong>Cancel WWW Override:</strong> This expires an "Enable WWW Connections" override, and web access will once again be controlled by DIP Switch 1 settings.<br><strong>Revalidate Certificate:</strong> This tells the server to forget the previous stored identity of the Controller, and to re-challenge the Controller the next time it establishes a connection to the server. After performing the override, the Controller's status message will show <em>"Controller using legacy encryption"</em>, until the Controller reconnects. This status message will however stay if the Controller is running firmware earlier than v7.80.<br><strong>Send Server address:</strong> If a controller is unable to connect to the server (and is therefore "offline") this override enables the controller to establish communication with the server. It will establish a connection to the controller and then use this connection to send the server’s address. When successful, the controller will connect to the server and come "online" again.<br><br><strong>Note:</strong> A warning message <em>"Controller and all related items may be unusable for a period of time"</em> will display if you use this override when the Controller's status message shows as <em>"Controller using legacy encryption"</em> (on the Controller’s <strong>Status and Overrides</strong> property page).</p><p><br><strong>CONTROLLER ONLY (when configured for 'Enable Secondary Ethernet Link')</strong><br><strong>Use Secondary Ethernet:</strong> This is a timed override that requests the Controller to switch the ethernet link it is using.<br><strong>Cancel use Secondary Ethernet:</strong> This expires a "Use Secondary Ethernet" override, and switches back to the original ethernet link it is using.</p><p><br><strong>CONTROLLER 7000 ONLY</strong><br><strong>Start Identifying Device:</strong> This causes the controller Run LED to flash amber five times repeatedly, spaced approximately three seconds apart.<br><strong>Stop Identifying Device:</strong> This causes the controller Run LED to stop identifying itself.<br><br><strong>Note:</strong> F5x/F6x Fence Controllers can also have <strong>Initiate Battery Test</strong> and/or <strong>Reset LV Sync Secondaries</strong> overrides performed on them. See <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/perimeter-fence-controllers/configuring-an-f3x-f4x-f5x-f6x-fence-controller.md">Configuring an F3x/F4x/F5x/F6x Fence Controller</a> for a description of these overrides.</p></td></tr><tr><td valign="top">an Elevator HLI</td><td><strong>Shunt:</strong> This stops communication with the elevator system and remains that way until you "Unshunt". Once the elevator system has detected that communication has been lost it will apply the default access mode. Normally this means access to any floor from an elevator car is allowed. (Some elevator systems, however, will allow a configurable access mode to be applied when communication is lost.)<br><br><strong>Unshunt:</strong> This starts polling of the elevator system. Access to floors from the elevator cars will now be controlled by Command Centre.</td></tr><tr><td valign="top">an Interlock Group</td><td><strong>Disable Group:</strong> This disables the interlocking functionality by ignoring all interlocking rules. The doors in the group operate as if they do not belong to an Interlocking Group.<br><strong>Enable Group:</strong> This enforces the interlocking rules defined for the group.<br><br><strong>Note:</strong> Items other than doors in an Interlock Group give misleading status, (i.e. a status message about preventing XXX from opening only applies when XXX is a door).</td></tr><tr><td valign="top">a Logic Block</td><td><strong>On:</strong> This disables the Logic Block's rules and timing options, and sets it's output "on".<br><strong>Off:</strong> This disables the Logic Block's rules and timing options, and sets it's output "off".<br><strong>Reset Logic:</strong> This restores the logic to a known state, and cancels long delay times or pulse times if these are unwanted.</td></tr><tr><td valign="top">a Workstation</td><td><strong>Deregister Workstation:</strong> Workstations only need to be registered if Server Properties have been configured with workstation restrictions or an Operator Group is restricted to the Workstation. When a Workstation is registered, the Command Centre server expects a certain certificate to be used when the Workstation connects.<br>If this certificate is lost or changed, or the Workstation is re-installed, the Workstation needs to be deregistered and registered again. While deregistered, the Workstation cannot logon until a new registration code is entered. Refer to the "Client Authentication" appendix in the <em>Release Note Command Centre</em> document for details about registration and the WorkstationCertificateInstaller utility.<br><strong>Disable Workstation:</strong> This disables the Workstation so that it cannot be logged into using either Command Centre or Configuration Client. Any currently logged-in Command Centre or Configuration Client operator will be logged off. These clients will remain disabled until the Workstation is manually enabled again with the 'Enable Workstation' override.<br><strong>Enable Workstation:</strong> This returns the Workstation to the normal enabled state so it can be used by operators.</td></tr></tbody></table>

   **Note:** You cannot specify the duration of the override on Inputs, Hardware items and Elevator HLIs, (i.e. until the next schedule change or for a specified time).
4. Click the **Override Now** button.

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

### Result

The item is overridden for the time specified.

While the "Shunt" override is in place, the system will not monitor the item, and the item will not generate alarms or cause event initiated actions.


---

# 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-monitoring/status-and-overrides/performing-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.
