> 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/logic-blocks-and-virtual-outputs/scenarios-using-logic-and-virtual-outputs/scenario-1-disabling-access-zone-pushbuttons-during-lockdown.md).

# Scenario 1: Disabling Access Zone pushbuttons during lockdown

### Scenario

Disabling push-button entry and exit, or remote release push-buttons while an Access Zone is locked down. This assumes either a keyswitch or operator overrides can be used for initiating and cancelling a lockdown.

### Solution

This can be achieved with the following set up:

1. Operators place an Access Zone into lockdown by running a 'Lockdown' macro. The macro is configured to override a virtual output to on when the Access Zone is locked down, as well as performing the Access Zone lockdown override.
2. Operators cancel a lockdown on an Access Zone by running a 'Cancel lockdown' macro. The macro is configured to override the virtual output (as in **a.** ) to off, as well as cancelling the Access Zone lockdown.
3. If the Access Zone is locked down using an input, then the 'input closed' event is configured to run the 'Lockdown' macro, via an action plan, and the 'input open' event is configured to run the 'Cancel lockdown' macro, via a different action plan. This means, the virtual output in **a.** and **b.** provides lockdown status - it is on when the Access Zone is locked down and off when the Access Zone is not locked down.
4. Configure each of the push-button entry, exit or remote release inputs in Command Centre as a logic block (rather than the real inputs). The logic is configured to be on when the real push button entry/exit or remote release input is closed and the Access Zone is not locked down (i.e. the virtual output in **a.** is off). The logic block 'on' is mapped to 'input closed', and used as the entry/exit button or remote release input.

   This configuration means that pushing the push-button entry/exit or remote release inputs will have no effect when the Access Zone is locked down, but will open the door at all other times. Note this is just one configuration using logic and virtual outputs that would provide this functionality - there are other similar configurations which would achieve the same effect.


---

# 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/logic-blocks-and-virtual-outputs/scenarios-using-logic-and-virtual-outputs/scenario-1-disabling-access-zone-pushbuttons-during-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.
