> 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-2-perform-open-door-override-during-lockdown.md).

# Scenario 2: Perform 'Open Door Override' during lockdown

### Scenario

Any operator can perform an open door override when the Access Zone is not locked down. A subset of these operators (the 'higher privileged operators') can perform an open door override whether or not the Access Zone is locked down.

### Solution

This can be achieved with the following set up:

1. The 'Open Door Override' privilege is given only to the higher privileged operators - those who can perform open door overrides whether or not the Access Zone is locked down.
2. For lower privileged operators, an 'Open Door' macro is placed on a Site Plan (or in Status Viewer). All operators are given the privilege to run this macro. The macro is configured to override a virtual output to on for 4 seconds (I'll call this 'Output A'). The same virtual output as used in Scenario 1, is also set up so that it is on when the Access Zone is locked down, and off at all other times (I'll call this 'Output B').
3. The remote release input on the door is set up as a logic block. The logic block is configured so that it is on when Output A is on and Output B is off, (i.e. when an operator has run the 'Open Door' macro and the Access Zone is not locked down). The logic block 'on' is mapped to 'input closed'.

   This configuration means when the 'Open Door' macro is run it will unlock the door, via the use of logic and the remote release input, only if the Access Zone isn't locked down. Note that this solution doesn't use an open door override for the lower privileged operators, so the event log will only show the macro being run and in some cases the logic block changing state, and hence the door opening.


---

# 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-2-perform-open-door-override-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.
