> 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/licensable-features/locker-management-solution/configuring-a-locker-bank/assigning-an-hbus-terminal-to-a-third-party-osdp-reader.md).

# Assigning an HBUS Terminal to a Third Party/OSDP Reader

1. Open the Properties window of the required Third Party/OSDP Reader, and click the **HBUS Terminal Display** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-728eba360ad3893f5c9eea92e19fe3db4560f331%2Fthirdpartyreader_hbustab.png?alt=media)
2. From the **HBUS Terminal** drop-down list, select the HBUS Terminal that is to display feedback from this Third Party/OSDP Reader.
3. Click **OK** to exit and save your changes.
4. To use this Third Party/OSDP Reader and HBUS Terminal for a Locker Bank, add both the Third Party/OSDP Reader and the HBUS Terminal to the **Readers** tab of the Locker Bank (refer to step 7 earlier in this topic).

### Result

* The Third Party/OSDP Reader can be used for reading third-party cards.
* The HBUS Terminal will display the Locker that the Cardholder has been assigned and when the Locker assignment will expire on its screen.

**Note:** The **First** option for the Locker Bank's **Access Credentials** must be set to **Card**, the **Second** option must be set to **None** (refer to step 12 later in this topic). Neither the Third Party/OSDP Reader or the HBUS Terminal will ever prompt for PIN/User Code.


---

# 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/licensable-features/locker-management-solution/configuring-a-locker-bank/assigning-an-hbus-terminal-to-a-third-party-osdp-reader.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.
