> 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-duress-code.md).

# HBUS Terminal: Duress Code

### Introduction

A duress code can be entered at a terminal or HBUS Contact Card Reader by a Cardholder to indicate that they are being threatened or forced to provide access under duress. Entering such a code generates a duress alarm. Duress alarms are raised in Command Centre but are not visible on the terminal/reader.

To raise a duress logon alarm:

1. Either:

   * Badge your card at the terminal/reader and enter your PIN, with the last digit incremented by one, OR
   * Enter your valid user code with the last digit incremented by one.

   | <p><strong>For example:</strong><br>PIN / User code 1256 = Duress logon is 125<strong>7</strong><br>PIN / User code 1259 = Duress logon is 125<strong>0</strong></p> |
   | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
2. Press the **Enter** key.


---

# 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-duress-code.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.
