> 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/external-alarm-monitoring/configuring-items-for-contact-id/configuring-items-for-contact-id.md).

# Configuring Items for Contact ID

Although the following procedure describes how to configure Contact ID for a Door, this same procedure is used for most other items. The only difference is how you select the item at Step 1.

**Important:** When the doors on your site were set up, they may have been configured with a common Alarm Zone associated with the Controller. However, for use with Contact ID they may need to use different Alarm Zones based on the area or location of the door. It may not be appropriate to use the same Alarm Zone as the "Intruder" alarms, as "Door" alarms are mostly 24 hour, whereas "Intruder" alarms use Set and Unset at different times of the day.

1. Click **Configure** from the menu bar, then **Doors** (as an example).
2. **Right click** on the Door and select **Properties**.
3. Click the **Alarm Transmission** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a8ab952e60032c2bcf286942b2cee2018f560a66%2Fcid_door.png?alt=media)
4. Enter a Zone identifier (for Hardware items), or user number (for Cardholders) to be used for Contact ID reporting, (i.e. the CCC value).

   **Notes:**

   * This field will accept 3 Hex digits 0-9, B-F.
   * The default of 000 can be left if you do not wish to indicate a specific zone or user information.
5. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.


---

# 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/external-alarm-monitoring/configuring-items-for-contact-id/configuring-items-for-contact-id.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.
