> 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/access-zones/access-zone-lockdown/performing-a-lockdown-override.md).

# Performing a Lockdown Override

### Introduction

This procedure allows operators with the "Override" privilege in an Access Zone's division to set or reset the lockdown state of an Access Zone.

**Note:** If a site wants to be able to determine which operator performed a lockdown override, they can review the event log which will have either an operator event saying who locked the Access Zone down, or a state change message for a lockdown input. If the site has a large number of events this may not be practical, so another alternative is to use the Access Zone **Notes** tab. The operator who performed the lockdown would need to update the Access Zone **Notes** tab to tell others why the lockdown has occurred and who to contact, if necessary.

If the lockdown is performed by an input, the input lockdown event can be configured as an alarm, and the associated alarm instructions can be used to tell other operators what they need to do.

### Procedure

1. Click **Configure** from the menu bar, then **Access Zones**.

   The **Access Zone** 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 Access Zone you want to perform a lockdown override on.
3. **Right click** and select **Properties**.
4. Click the **Status and Overrides** tab.
5. Click the **Lockdown** tab within this screen.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-5cf6786ba38453a5d08632eadad95b542cbaa6bf%2Faczone_overrides_lockdown.png?alt=media)
6. Click the **Lockdown** button.

   The status message will change to include the following text:

   *"The access zone is locked down. Only Cardholders with the Entry during lockdown privilege can enter."*

   **Notes:**

   * When a **Lockdown** override occurs, the following event is logged:

     *Operator '\[Name]' requested a Lockdown Override for access zone '\[Name]'*

     and then when you perform a **Cancel Lockdown** override, the following event is logged:

     *Operator '\[Name]' requested a Cancel Lockdown Override for access zone '\[Name]'*

     If you have the "Access Zone State Change" Event Group set to 'log an event' (via the **Event Defaults** tab of the Server Properties), in addition to the events above, the following event will **also** be logged at the time of a **Lockdown** override and a **Cancel Lockdown** override:

     *\[Access Zone] changed to \[access mode] \[PINs mode] at \[Door]*
   * While a lockdown override is in force, other overrides of the Access Zone can occur, (e.g. to other access modes).
7. Click the **OK** button.

### Result

The Access Zone has been overridden to "lockdown" mode. The lockdown override will remain in force until it is cancelled, (i.e. the **Cancel Lockdown** button is clicked).

**Note:**

Once a lockdown override is cancelled, the Access Zone will return to either:

* it's scheduled state if no other overrides of the Access Zone are active,

  or
* it will return to the overridden state if other overrides are currently active.


---

# 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/access-zones/access-zone-lockdown/performing-a-lockdown-override.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.
