> 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/integrated-systems/schlage-lock-interface/performing-overrides-on-a-schlage-door.md).

# Performing Overrides on a Schlage Door

### Introduction

This procedure describes how to temporarily override the status of a Schlage Door.

### Procedure

1. From the **Hardware** List Window, right-click the Schlage Door you want to perform an override on and select **Properties**.

   By default, the **General** tab displays.
2. Click the **Status and Overrides** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-ce7de5469ca591067eb9d4bb1a96bb39cf08019d%2Fschlage_opendooroverride.png?alt=media)
3. Select the type of override you want to perform from the **Override** drop-down list.

   <table><thead><tr><th width="112">Option</th><th>Function</th></tr></thead><tbody><tr><td>Shunt</td><td>Stops communication to the device (door).</td></tr><tr><td>Unshunt</td><td>Restarts communication to the device (door).</td></tr><tr><td>Open Door</td><td>Unlocks the door momentarily allowing a person to pass through.</td></tr></tbody></table>
4. Click the **Override Now** button.

   From this screen you can see the status change as a result of the override.
5. Click the **OK** button.


---

# 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/integrated-systems/schlage-lock-interface/performing-overrides-on-a-schlage-door.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.
