> 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/products/cc-software/configure/configuration-scenarios/scenario-stopping-the-door-open-too-lo.md).

# Stop door-open-too-long alarms from sounding

Override a door to Free access or suppress door sounds during open-too-long alarms.

To stop "door open too long" alarms sounding, put the door into **Free access** via an override (from the Configuration Client, from a Command Centre Client site plan, or via a schedule change). If you need to suppress the noise at the door itself, you can turn off the door's warning/alarm sounds and set the reader volume to off, but note the alarm **still shows in the Alarm Viewer**. Removing the door sensors also stops the alarm.

### Override to Free access from the Configuration Client

1. In the Configuration Client, find the door you want to override. Open the door, go to the **Entry** tab, right-click on the access zone and select **Override**.

![Right-click access zone and select Override in the Configuration Client](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-15ab7f5f95eeab2525e0088a14461fb5e8e51650%2FSECHUB-CCS-DOOROPEN-01-config-client-override.png?alt=media)

2. The Access Zone Properties appears. Select **Status and overrides**, choose **Free - no PIN** from the dropdown, then click **Override Now**. The door's access zone will be in Free access.

![Status and overrides set to Free - no PIN](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-2465cc00a818abed5f1f5cae4f428adb6bd3a51d%2FSECHUB-CCS-DOOROPEN-02-status-overrides-free-no-pin.png?alt=media)

![Door access zone now in Free access](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-c47884d62cd6410b5a1ee27228b3ca33f8263f96%2FSECHUB-CCS-DOOROPEN-03-free-access-result.png?alt=media)

### Override from the Command Centre Client using site plans

1. Find the site plan with the door you want to override. Right-click on the door and select **"Override Entry Access"**.

![Right-click door on site plan and select Override Entry Access](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-496668289cc6800fcc86246b7441239fd45015cd%2FSECHUB-CCS-DOOROPEN-04-site-plan-override-entry.png?alt=media)

2. Select **Override to Free - No PIN**, then select how long you want the override to last. The door should now be in Free access.

![Override to Free - No PIN with a duration](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-0d870e47b2c08a6b2f61a66696ee75b6c1e1cfed%2FSECHUB-CCS-DOOROPEN-05-override-free-duration.png?alt=media)

### Change the schedule

Change the schedule for the access zone for the door to **Free access**.

### Suppress the noise at the door

The following options stop the sound but do **not** clear the alarm from the system:

* On the door config, turn off all warning / alarm sounds. **The alarm still shows in the Alarm Viewer.**
* Set the volume on the reader to **Off**. **The alarm still shows in the Alarm Viewer.**
* Remove the door sensors from the door.

![Door config sound settings](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-58f50d7ea1a4562c89414c1ad4eb978a661d2fe8%2FSECHUB-CCS-DOOROPEN-06-door-config-sounds.png?alt=media)

### Related links

* [Alarm Transmission - Monitoring](/knowledge-hub/products/cc-software/configure/alarm-transmission/alarm-transmission-monitoring.md). How door and input alarms reach monitoring.


---

# 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/products/cc-software/configure/configuration-scenarios/scenario-stopping-the-door-open-too-lo.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.