> 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-monitoring/status-and-overrides/open-a-door-request.md).

# Open a Door Request

### Introduction

This procedure enables an operator with the "Override - Open Door" privilege, to open a specific [*door*](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#door) for a few seconds to allow a person to pass through.

### Procedure

1. Click **Configure** from the menu bar, then **Doors**.

   The **Door** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. **Right click** on the door you wish to open, and click **Open Door** from the drop-down menu.

### Result

The door is briefly unlocked (for a length of time set by the system), and the person can open the door and pass through.

### Hint

{% hint style="info" %}
Alternatively, instead of clicking Open Door from the drop-down menu, you can 'open the door' from the **Status and Overrides** tab on the Properties window for the Door.

<img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-8e1549f5bfb5fa6408314449ec38057a586d3d0e%2Fopendoor1.png?alt=media" alt="" data-size="original">

Click within the **Override** field and select "Open Door", then click the **Override Now** button to open the door.

From this screen you can see the status change as a result of the override.

**Note:**

You can not specify that an override to open a door be implemented until the next schedule change or for a specified time.
{% endhint %}


---

# 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-monitoring/status-and-overrides/open-a-door-request.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.
