> 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/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-locking-out-a-fence-zone.md).

# Lock out a fence zone

Disable fence pulses safely while preserving intrusion detection for a selected fence zone.

**Purpose:** allow someone to safely work on the fence in the knowledge that it will not be energised.

**Required privilege:** the Access Group must have the **"Lock out fence zones"** privilege.

### Understand lockout before use

> ⚠️ **Safety rules:**
>
> * **Only the cardholder that initiated the lockout can cancel it.**
> * **Lockout can only be cancelled using the RAT that initiated it.**
> * **Lockout IS persisted during a Fence Controller or Controller restart.** It is NOT persisted during a DIP Switch 2 Controller restart.
> * The additional privilege "Cancel others lock out" allows a person of authority, for example a site manager, to cancel another cardholder's lockout, but **still using the RAT that initiated it**.

### Fence zone behavior during lockout

* **No deterrent will be delivered** (no pulse).
* **Overrides will be ignored.**
* Scheduled changes will not take place.
* Requests to arm will be ignored.
* **Alarms will still be raised.** Detection is unaffected. Only the pulse is disabled.
* If an F31/F32/F41/F42 Fence Controller is subsequently placed in Service mode, requests to arm using the magnetic key (G21963) will be ignored and discarded.

### Procedure

1. Log on to the Remote Arming Terminal.
2. Press **More** on "Choose Action" to reach the "Main Menu".
3. Scroll to "Fence Zones" and press the key. The "Fence Zones" screen displays.
4. Scroll to the Fence Zone and press the key. The "Voltages" screen displays.
5. Press the **Override** key. The "Fence Overrides" screen displays.
6. Press the **Lockout** key. The "Fence Overrides" screen shows "Locked Out" and the cardholder who initiated it.
7. Lockout remains until cancelled.

![Fence Overrides screen showing Lockout option](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-2d27c5b8d93d80920d9b56a50aaaf3ac2ed9b457%2FSECHUB-RAT-ALARMS-01-alarm-list.png?alt=media)

***

🔗 **Related**

* [Keypads - Overriding a scheduled Fence Zone state](/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-overriding-a-scheduled-fence-z.md). The Fence Overrides screen and its other options.
* [Keypads - Monitoring Fence Zone status](/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-monitoring-fence-zone-status.md). The LOCK status code that appears when a zone is locked out.


---

# 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/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-locking-out-a-fence-zone.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.