> 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/command-centre-duress-terminal-formerl.md).

# Duress terminal (formerly Duress RAT)

{% hint style="info" %}
Formerly **Duress RAT**. The feature was renamed when the T20 HBUS Terminal replaced the GBUS Remote Arming Terminal (RAT) as the supported hardware. Release notes use "Duress RAT" up to v8.20 and "Duress Terminal" from v8.30.
{% endhint %}

The **Duress Terminal** feature turns a **T20 HBUS Terminal or Remote Arming Terminal (RAT)** into a permanent **Duress Alarm Panel** that stays in alarms view without any login or navigation, so guards can watch for and respond to alarms continuously. A common use is monitoring duress alarms triggered by people in physical danger.

## What it is

The Duress Terminal feature introduces the **Duress Alarm Panel**, which contains:

* a **Duress Terminal** (T20 or RAT)
* an **LED**, illuminated if the Duress Terminal contains active or unacknowledged alarms
* a **siren**, which sounds if a new alarm occurs at the Duress Terminal
* a **pushbutton** which silences the siren (until another alarm occurs)

The feature allows a T20 HBUS Terminal or RAT to permanently remain in alarms view (without login or navigation) to display alarms to guards so they can respond. The **Menu** option on a T20 Duress Terminal does not display, and is optionally replaced with an **Acknowledge** (acknowledge alarm) option.

One use for this feature is for guards to monitor duress alarms, which are triggered by people who are in physical danger.

## Command Centre versions supported

Per the source page (a tick = supported):

| v7.90 | v8.00 | v8.10 | v8.20 | v8.30 | v8.40 | v8.50 | v8.60 | v8.70 | v8.80 | v8.90 | v9.00 |
| :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: |
|   ✓   |   ✓   |   ✓   |   ✓   |   ✓   |   ✓   |       |       |       |       |   ✓   |   ✓   |

Supported in **v7.90 through v8.40**, and again in **v8.90 and v9.00**. The source shows no support across v8.50 to v8.80.

## Release notes

Release notes for each supported version (newest first):

* [Release Note Duress Terminal (v9.00)](https://media.gallagher.com/m/27188d2d21514bb3/original/Release-Note-Duress-Terminal-v9-00.pdf)
* [Release Note Duress Terminal (v8.90)](https://media.gallagher.com/m/38c1196ba13e39d7/original/Release-Note-Duress-Terminal-v8-90.pdf)

{% file src="/files/MtcSCzMY7niKUND6PpwY" %}
Release Note Duress Terminal (v8.40)
{% endfile %}

{% file src="/files/mC9XrwZ4wiYUiuuJNUAn" %}
Release Note Duress Terminal (v8.30)
{% endfile %}

{% file src="/files/h2LsN3FN9Dy5wCACGTWJ" %}
Release Note Duress RAT (v8.20)
{% endfile %}

{% file src="/files/5J1F2Gj9cQWiiyNEV6Sp" %}
Release Note Duress RAT (v8.10)
{% endfile %}

{% file src="/files/oT3nzXkzPuPyhexPfAO8" %}
Release Note Duress RAT (v8.00)
{% endfile %}

{% file src="/files/xraC0MjF40u6saXjlePU" %}
Release Note Duress RAT (v7.90)
{% endfile %}

***

🔗 **Related**

* [Command Centre - Alarm Zones](/knowledge-hub/products/cc-software/configure/alarm-zones.md). The alarms a Duress Terminal displays and acknowledges.


---

# 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/command-centre-duress-terminal-formerl.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.