> 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-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-remote-arming-terminal-as-a-ke.md).

# Use a Remote Arming Terminal as a reader keypad

Use a Remote Arming Terminal for door access, alarm-zone control, and access-zone overrides.

When a Remote Arming Terminal is configured as a keypad for a reader, it can be used for door-access operations. This page covers what you can do from it: gaining access, setting and unsetting Alarm Zones, and overriding Access Zones.

In idle mode (keypad mode) the terminal shows the **Welcome screen with the reader's idle prompts**, which are Secure or Free, and Dual-Authority or Code or no entry.

### Soft keys on the idle keypad screen

| Key (soft-key label on screen) | Use to...                                                                                                                                                                                      |
| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Logon**                      | Transfer the Remote Arming Terminal from "door access" mode to standard logon mode ("alarm management" mode) **temporarily**, which allows local alarm management without leaving keypad mode. |
| **F1** (Set/Unset)             | Set/unset Alarm Zones.                                                                                                                                                                         |
| **F2** (Override)              | Override Access Zones of the Door reader for the associated Remote Arming Terminal.                                                                                                            |

The idle Welcome screen shows the three soft keys **F1**, **F2** and **LOGON** along the bottom row.

### Use door access

1. Badge card at the reader associated with the Remote Arming Terminal.
2. The appropriate message displays, granting or denying access.
3. If a PIN is required, enter the PIN to gain entry.
4. **More secure option:** use a user code in place of a PIN. This is configured in Command Centre on the Connection tab of the reader's property. The message then reads **"Usercode please"**.

### Set or unset alarm zones

**Method 1:**

1. Press the **F1** (Set/Unset) key.
2. Badge card at the reader.
3. The Alarm Zone associated with the Access Zone is set/armed.

**Method 2 (double card):**

1. Badge card **twice**.
2. To use this feature, "Double card overrides" **must be set to** "Arm alarm zone" on the Connections tab of the reader associated with the Remote Arming Terminal.

### Override access zones

**Method 1:**

1. Press the **F2** (Override) key.
2. Badge card at the reader. A menu displays on the Remote Arming Terminal.
3. Press the number key for the desired option:

   * **1** = Override to Mode 1
   * **2** = Override to Mode 2
   * **3** = Override to scheduled state

   Mode 1 and Mode 2 are access modes as configured on the Access Mode tab of the Access Zone properties.

**Method 2 (double card):**

1. Badge card **twice** to override the mode of the Access Zone between Mode 2 and scheduled mode.
2. To use this feature, "Double card overrides" **must be set to** "Override access zone" on the Connections tab of the reader associated with the Remote Arming Terminal.
3. The cardholder must be in an Access Group with **"Lock and unlock access zones"** privilege on the Privilege tab.

> ⚠️ The exit-delay screen shows potential alarms as warnings only on terminals in the logged-off state, or used to arm one or more zones. It is **not** shown when the terminal is configured as a keypad for a reader.

***

🔗 **Related**

* [Keypads - Remote Arming Terminal operation](/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-remote-arming-terminal-operati.md). The keys, screens and privileges behind every keypad action.
* [Keypads - Arming](/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-arming.md). Arming from standard logon mode, including the exit-delay behaviour noted above.
* [Keypads - Logging on](/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-logging-on.md). The four ways to log on once you switch out of keypad mode.


---

# 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-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-remote-arming-terminal-as-a-ke.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.
