> 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/command-centre-client/configuring-command-centre/configuring-licensable-features/universal-credential/physical-credentials.md).

# Physical Credentials

### Defining the Site Code and Card Number

Physical credentials can contain both a site code (facility code) and a card number. When configuring a Universal Credential Type, you can include the site code in the card number or read it separately.

**Option 1: Define the site code**

This is the recommended option. The site code and card number are read independently. The site code is matched against the Universal Credential Type, and the card number is matched against the cardholder assignment.

**Result**

* The card number in Command Centre matches the printed card number or provider's card number.
* Supports duplicate card numbers across different site codes.
* Supports multiple Universal Credential Types using the same key, if using different site codes.

**Option 2: No site code defined**

This alternative option can be used if the site code is unknown, or if only one site code is used. The site code here is included in the card number. For example, 0xXXXX00YYYYYY where XX are bytes representing the site code, and YY are bytes representing the card number. The card number offset and length must include both values.

**Result**

* Both values are assigned to the cardholder as the card number. Note, this is not ideal for manual card assignment, as the operator will need to enter both values when assigning a card to a cardholder or searching for a cardholder. The combined number may not match the number printed on the card or in the credential provider’s system.
* Controllers will only authenticate the combined number.

**Notes:**

* If only one site code is used, configuring a site code in the Universal Credential Type is optional.
* When using more than one Universal Credential Type without defining site codes, the system will not be able to distinguish credentials with the same card number but different site codes. This may result in access being granted to the wrong cardholder.
* A Universal Credential Type site code can be edited after credential assignment. The new card number definition will display for new card assignments only.

### Duplication

Command Centre prevents duplication of a Universal Credential Type. A Universal Credential Type cannot be created if the combination of the following fields matches an existing credential. Note: The exception to this rule is the Site Code. If the Site Code is different, and the fields below are an exact match, creation of the credential is allowed.

* CardDataAID
* KeyValue
* KeyType
* KeyNumber
* DivInputSequence
* DivCMAC pad length
* ProtectionLevel

### Card Issue Level

Physical profiles always have a card issue level of 1. The Gallagher REST API should either omit the issue level or send a value of 1. Any other value will cause the entire API call to fail with a generic error.


---

# 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/command-centre-client/configuring-command-centre/configuring-licensable-features/universal-credential/physical-credentials.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.
