> 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/licensable-features/perimeter-fence-controllers/overriding-a-scheduled-fence-zone-state.md).

# Overriding a scheduled Fence Zone state

### Introduction

This procedure describes how to temporarily override a Fence Zone in Command Centre to:

* "On" or "Off" (to allow voltages to be checked by a technician),
* "Shunt" or "Unshunt" (if the Fence Zone is creating false alarms), or
* "High Voltage" or "Low Feel" (to change the voltage level)

  **Note:** HV/LF mode is compatible with F3x, F4x, F5x, F6x and F22 Fence Controllers only.

### Before you begin

Before you begin this procedure:

* Ensure that the Fence Zone has been assigned to a Fence Controller, and that the Fence Controller has been assigned to a Gallagher Controller 7000 or 6000.
* You need to be in the same or parent Division of the Division holding the Fence Zone, and have the "Maintenance Override" operator privilege to perform this procedure.

### Procedure

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. Highlight the Fence Zone you want to override.
3. Either:

   * **Right click** and select **Properties,** then click the **Status and Overrides** tab.

   OR

   * **Right click** and select **Override...**

     The **Status and Overrides** tab displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-7d622c699679b49d416028beb3da7c0de18c9b5d%2Ffencezone_statustab.png?alt=media)
4. Click within the **Override** field and select the required override action from the drop-down list, (i.e. "Shunt", "Unshunt", "On", "Off", "High Voltage" or "Low Feel").

   **Notes:**

   * An "On" override causes the Fence Zone to become active, (i.e. pulsing), and an "Off" override causes the Fence Zone to become inactive, (i.e. not pulsing).
   * Fence Zones do not support timed overrides. All overrides are immediate and persist until specifically cancelled by an operator using Command Centre or from a Terminal. Cancelling an override cancels any existing "On" or "Off" override.
5. Click the **Override Now** button.

### Result

The override is applied and will remain in place until the override is manually cancelled.

**Notes:**

* The Fence Zone turns on when its Alarm Zone is armed. This is not an override - it is normal behaviour.
* Fence logging events will still occur when a Fence Zone is shunted.


---

# 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/licensable-features/perimeter-fence-controllers/overriding-a-scheduled-fence-zone-state.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.
