> 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/readers/t-series/t-series-t30-operation.md).
# T30 keypad
Reference T30 reader variants, door requirements, and code-only and PIN access behavior.
### T30 keypad reader
The T30 is a lower-cost solution for sites that want card + PIN and code-only access without the cost of T20 terminals. It includes a keypad but no screen.
> ⚠️ **The T30 must be attached to a Door.** If the keypad is not responsive, verify that the reader is configured to a Door in Command Centre.
> ⚠️ **The T30 is HBUS only.** There is no way to connect it via CardaxIV. That functionality is not present in the T30 hardware.
***
### T30 variants
| Part Number | Description |
| ----------- | ----------------------------------- |
| C300490 | T30 Multi Tech Keypad Reader, Black |
| C300491 | T30 Multi Tech Keypad Reader, White |
| C300495 | T30 MIFARE® Keypad Reader, Black |
| C300496 | T30 MIFARE® Keypad Reader, White |
> ⚠️ **T30 "Multitech" does NOT include 125 kHz.** In this model, "Multi Tech" means MIFARE + Bluetooth only. No version of the T30 supports 125 kHz. This technology has been deprecated in this model.
***
### Code-only and PIN access behavior
The T30 can arm a single alarm zone associated to the access zone, but cannot arm via user code entry (unlike the T20). The table below shows expected behaviour for code-only and PIN access options depending on alarm zone state.
| Alarm Zone | PIN is User Code | Code Only — Card and no PIN | Code Only — Card and PIN | Credential at T30 | Result |
| ---------- | ---------------- | --------------------------- | ------------------------ | ----------------- | -------------- |
| Disarmed | | Enabled | | Code only Code | Access Granted |
| Disarmed | | | Enabled | Code only Code | Access Granted |
| Armed | | Enabled | | Code only Code | Access Denied |
| Armed | | | Enabled | Code only Code | Access Denied |
| Disarmed | ✓ | Enabled | | User Code | Access Granted |
| Disarmed | ✓ | | Enabled | User Code | Access Denied |
| Armed | ✓ | Enabled | | User Code | Access Granted |
| Armed | ✓ | | Enabled | User Code | Access Denied |
> **Note:** The alarm zone will be disarmed when access is granted, assuming the cardholder has the disarm privilege. However, the T30 **cannot be used to arm** the alarm zone via user code entry. This differs from the T20, which can arm the alarm zone if suitably configured.
***
🔗 **Related**
* [T Series](/knowledge-hub/products/cc-hardware/readers/t-series.md). T30 part numbers.
* [T Series - T20 User Guide and Resolution](/knowledge-hub/products/cc-hardware/readers/t-series/t-series-t20-user-guide-and-resolution.md). The higher-featured terminal that can arm via 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/products/cc-hardware/readers/t-series/t-series-t30-operation.md?ask=&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.