> 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/hardware/configuring-hbus-terminals/hbus-terminal-overriding-the-access-mode.md).

# HBUS Terminal: Overriding the Access Mode

### Introduction

If the terminal or HBUS Contact Card Reader has been assigned as a Reader for a Door, the following procedure can be used to change the Access Mode for the Door's Access Zone, (e.g. from Secure to Free).

**Notes:**

* The Alarm Zone associated with the Door’s Access Zone must be disarmed.
* You must have the ‘Lock and unlock access zones’ access privilege for the Door’s Access Zone. Refer to [Setting up Access Groups](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/access-groups/setting-up-access-groups.md).

### Method 1:

1. Press the **Mode** key.
2. Log on to the terminal.

   **Notes:**

   * The credentials required to log on to a terminal are configured on the **Welcome Screen** tab of the terminal item. By default, the first logon credential is ‘Card’. By default, the second logon credential is ‘PIN’.
   * If the terminal is assigned as the Reader for an Elevator Car, the **Mode** key is not displayed; hence it cannot be used to override the Access Mode for the Access Zones associated with the Elevator Car.

   If logon is successful, the Access Mode screen displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-86ad3192d577e2e539a43193ad69cfe9890fe194%2Ft20accessmodescreen.png?alt=media)
3. Press the key representing the Access Mode you require.

   <table><thead><tr><th width="138">If you press...</th><th>then the Access Mode is...</th></tr></thead><tbody><tr><td>1</td><td>overridden to Mode 1.</td></tr><tr><td>2</td><td>overridden to Mode 2.</td></tr><tr><td>3</td><td>overridden to the scheduled state.</td></tr></tbody></table>

   **Note:** Mode 1 and Mode 2 are the Access Modes as configured on the **Access Mode** tab of the Access Zone properties. The scheduled state is the Access Mode currently defined in the Schedule associated with the Access Zone.

### Method 2:

Present your card twice, (known as a ‘double card override’) at the terminal.

This overrides the Access Mode of the Access Zone between Mode 2 and the scheduled state (as configured in Command Centre). If the override is successful, the Access Mode is changed and the message *"Override successful"* displays.

**Notes:**

* To use this feature, ‘Double card overrides’ must be set to ‘Override access zone’ on the **Advanced** tab of the terminal item.
* If the terminal is assigned as the Reader for an Elevator Car, it is recommended that double card overrides not be configured, because of the potential to accidentally override multiple Access Zones.
* Double card overrides are not supported when the Access Mode is set to Dual Auth.


---

# 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/hardware/configuring-hbus-terminals/hbus-terminal-overriding-the-access-mode.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.
