> 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/tag-tracking/configuring-the-tag-tracking-feature/card-technology-settings.md).

# Card Technology settings

<table><thead><tr><th width="312">To enable...</th><th>See procedure...</th></tr></thead><tbody><tr><td>individual Gallagher T-Series Readers (i.e. only some Readers) to read tracking tags,</td><td><em>"Enabling tracking tags per Reader"</em></td></tr><tr><td>Gallagher T-Series Readers to read tracking tags by default for your whole site (not recommended),</td><td><em>"Enabling tracking tags for your whole site"</em></td></tr></tbody></table>

#### Enabling tracking tags per Reader

To enable individual Gallagher T-Series Readers (i.e. only some Readers) to read tracking tags, perform the following procedure:

1. Click **Configure** from the menu bar, then **Hardware**.

   The Hardware List Window opens.
2. Open the properties of the Gallagher T-Series Reader(s) that you wish to enable to read tracking tags.
3. Click the **Advanced** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-3a040b8c337b324c98716e010e097d92933845d8%2Freader_advanced.png?alt=media)
4. If the **Use the server settings** check box is checked, the Reader will use the configuration as specified on the Server Properties. See *"Enabling tracking tags for your whole site"* below to set the card technology server settings.
5. To configure permitted card technology specific to this Reader, deselect the **Use the server settings** check box and select the **Bluetooth Tracking Tags** check box.
6. Click **OK** to close and save your changes.

#### Enabling tracking tags for your whole site

To enable Gallagher T-Series Readers to read tracking tags by default for your whole site (not recommended), perform the following procedure:

1. Click **File** from the menu bar, then **Server Properties**.

   The **Server Properties** window opens.
2. Click the **Card Security** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e641153e10a41b5efd956cacf4047a54097758fd%2Fserverproperties.png?alt=media)
3. In the 'Permitted Card Technology' section of this screen, select the **Bluetooth Tracking Tags** check box.
4. Click **OK** to close and save your changes.


---

# 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/tag-tracking/configuring-the-tag-tracking-feature/card-technology-settings.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.
