> 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.md).

# Access Zone Lockdown

### Introduction

The Access Zone "lockdown" mode allows a site to very quickly and easily deny entry to an Access Zone to all but selected cardholders, while still allowing cardholders to exit the zone.

The lockdown status of an Access Zone can be changed by either:

* a lockdown override, or
* the cancelling of a lockdown override, or
* changing the state of a lockdown input, or
* running a macro to override the Access Zone.

### Lockdown behaviour

When an Access Zone is in lockdown mode cardholders are only allowed entry if they belong to at least one Access Group that allows scheduled access at the current time, and that also conveys the "Entry allowed during lockdown" privilege (on the **Privileges** tab of the Access Group properties).

When entry to an Access Zone in lockdown mode is provided from an elevator car, the elevator car floor level buttons for the Access Zones that are in lockdown remain disabled when a cardholder badges their card, unless the cardholder also has the "Entry allowed during lockdown" privilege for that floor/Access Zone.

### Scenarios

Refer to [Scenarios using Logic and Virtual Outputs](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/logic-blocks-and-virtual-outputs/scenarios-using-logic-and-virtual-outputs.md) for worked examples of lockdown configuration.

Select the item below that you require further detail on:

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Setting a Lockdown source](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/access-zones/access-zone-lockdown/setting-a-lockdown-source.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Performing a Lockdown Override](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/access-zones/access-zone-lockdown/performing-a-lockdown-override.md)


---

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