> 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/doors/configuring-extended-access-time-for-a-door.md).

# Configuring extended access time for a Door

### Introduction

Extended access can be granted so that a door will remain unlocked for longer than normal, for those cardholders who require it, (e.g. disabled people, couriers, delivery vehicles, etc.).

There are two parts to this procedure, (i.e. configuring the extended access time for a Door, and identifying those cardholders that require extended access time).

This procedure describes configuring the extended access time for a Door.

**Note:** Operators require the "Edit Site" operator privilege to perform this part of the procedure.

Identifying cardholders that require an extended access time is performed in Command Centre Client. Refer to **Setting Accessibility options** (under the "Cardholder Details Tile actions" topic), in the *Gallagher Command Centre Client User Guide* for detailed instructions.

### Procedure

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

   The **Door** List Window opens.
2. Highlight the door the extended access time is to be configured for.
3. Right click and select **Properties**.
4. Click the **Advanced** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-5441ed81c5525f22877017ebd42a82201b191ea3%2Fdoor_advanced.png?alt=media)
5. Enter the maximum time you want the door to unlock for in the **Extended access time** field.

   (The range for this field is 0 - 86400 seconds, and by default is set at 25 seconds).

   **Note:**

   The **Extended access time** affects the times used for all of the following:

   * Door unlock time
   * Door Open Too Long Warning
   * Door Open Too Long Alarm
   * When a cardholder identified as requiring extended access time badges their card at this door, the door will remain unlocked for a time equal to the **Door unlock time** PLUS the **Extended access time**, (e.g. if the door is configured with a Door unlock time of 5 seconds, and an Extended access time of 60 seconds, then the door will remain open for 65 seconds).
   * Once a cardholder has opened the door, the Door Open Too Long Warning is activated if the door is still open after a period of time equal to the **Door Open Too Long Warning time** PLUS the **Extended access time**, (e.g. if the door is configured with a Door Open Too Long Warning time of 40 seconds, and an Extended access time of 60 seconds, then the Door Open Too Long Warning will activate after 100 seconds).
   * Once a cardholder has opened the door, the Door Open Too Long Alarm is activated if the door is still open after a period of time equal to the **Door Open Too Long time** PLUS the **Extended access time**, (e.g. if the door is configured with a Door Open Too Long time of 50 seconds, and an Extended access time of 60 seconds, then the Door Open Too Long Alarm will activate after 110 seconds).
6. Click **OK**.

### Result

An extended access time has been configured for a door.


---

# 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/doors/configuring-extended-access-time-for-a-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.
