> 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

Stop a fence zone pulsing so it can be worked on safely, from a Gallagher T20 Terminal.

Lockout lets someone work on a fence knowing it will not be energized.

**Required privilege:** your Access Group must have **Lock out fence zones** and must list the fence zone's alarm zone. It also needs **View alarms and items** for that alarm zone, or the fence controller does not show on the Fences screen.

### Rules

{% hint style="warning" %}

* **A lockout can be canceled only at the terminal that started it.** Lockouts cannot be started or canceled from a Command Centre workstation.
* **Only the cardholder who started a lockout can cancel it,** unless another cardholder has **Cancel others lockout**, such as a site manager. They still have to cancel it at the terminal that started it.
* **The fence controller shows no sign of a lockout.** Before anyone touches the fence, check that the fence zone shows **Lockout** on the terminal.
* **A lockout stays in place** through a fence controller restart or a Gallagher Controller restart. A Gallagher Controller restarted with DIP switch 2 on does not keep the lockout. Treat the fence as live after such a restart.
  {% endhint %}

### What happens during a lockout

* The fence is not pulsed, so no deterrent is delivered.
* Overrides and state changes are ignored.
* Scheduled changes do not take place.
* Requests to arm are ignored and discarded. Turning the zone on from a Command Centre workstation has no effect, although the zone can still show as armed.
* If the fence controller is then put into Service mode, the magnetic key cannot arm or disarm a locked-out fence zone. This applies to F3x, F4x, F5x and F6x fence controllers.
* **Alarms are still raised.** Command Centre raises an alarm for each locked-out fence zone.

### Lock out one fence zone

1. [Log on](https://help.security.gallagher.com/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-logging-on.md). If the fence controller list isn't showing, choose **Fences** from the Menu.
2. Select the fence controller and press **More**.
3. Select the fence zone and press **Lockout**. Or press **More**, choose **Lockout** and press **Select**.

### Lock out every fence zone on a fence controller

1. [Log on](https://help.security.gallagher.com/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-logging-on.md). If the fence controller list isn't showing, choose **Fences** from the Menu.
2. On the Fences screen, select the fence controller.
3. Press **Lockout**.

This locks out all the fence zones on that controller.

### Cancel a lockout

{% hint style="danger" %}
Undoing a lockout reactivates the fence. Treat it as live.
{% endhint %}

1. At the terminal that started the lockout, go back to the Fences screen and select the fence controller.
2. Press **Undo Lockout**.
3. For each fence zone, the terminal asks **Do you want to undo this lockout?** Choose **Yes**.

To undo the lockout on one fence zone, open the fence zone at the same terminal (select the fence controller, press **More**, select the zone, press **More**), choose **Undo Lockout** and press **Select**.

***

🔗 **Related**

* [Override a scheduled fence zone state](https://help.security.gallagher.com/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-overriding-a-scheduled-fence-z.md). The other fence zone actions.
* [Monitor fence zone status](https://help.security.gallagher.com/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-monitoring-fence-zone-status.md). Check a zone's state before and after.


---

# 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.
