> 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/using-command-centre/working-with-viewers/tile-actions/cardholder-cards-tile-actions/assigning-a-card-credential-or-digital-id.md).

# Assigning a Card, Credential, or Digital ID

A Cardholder can either be assigned:

* a brand new Card, where the card number and issue level are automatically assigned by the system, OR
* a recycled Card, where the Administrator sets the card number and issue level based on a spare card they have available, either manually or by badging the Card at a reader.

A Cardholder can be registered to:

* a Mobile Credential for use at Gallagher Bluetooth® or NFC enabled readers. Mobile Credentials are registered to Cardholders in Command Centre Client and recieved by Cardholders on their mobile devices.
* a Digital ID for visual identification. Digital IDs are formatted in Gallagher Configuration Client, registered to Cardholders in Command Centre Client, and received by Cardholders on their mobile devices.

To assign Cards or register Mobile Credentials or Digital IDs in bulk, see [Creating a new Cardholder Bulk Change](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/bulk-changes/creating-a-new-cardholder-bulk-change.md).

To assign a new Card or register a Mobile Credential or Digital ID:

1. Click the **Assign Card** button.

   The Assign Card pop-up displays.

<details>

<summary>Assign Card pop-up</summary>

The first example shows the appearance of the Assign Card pop-up when assigning a card.

![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-5b2313c6cd52f037a1c57fe42711cc18353164ad%2Fassigncard_popup.png?alt=media)

The second example shows the appearance of the Assign Card pop-up when registering a mobile credential.

![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-8ba69c97eb71bce86e5c9595636fce8534aa9607%2Fassigncredential.png?alt=media)

</details>

<details>

<summary>Click here for a description of how the fields are populated</summary>

<table><thead><tr><th width="130">Field</th><th>Description</th></tr></thead><tbody><tr><td>Card Type</td><td><p>This drop-down list is populated with an alphabetical list of the Card Types, Mobile Credential Types, and/or Digital ID Types that can be assigned/registered to a Cardholder AND that the operator has the privilege to assign.<br>Either select a Card Type, Mobile Credential Type, or Digital ID Type from the drop-down list, or click the <img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-eb8b7e19f56793693de4c172c25d4dd7bf3e4fbf%2Fselectcardtype_button.png?alt=media" alt=""> button to use the browse tool to make your selection.<br><br><strong>Notes:</strong></p><ul><li>If you select a Digital ID Type and the Cardholder does not yet have a Mobile Credential, you will see a warning message. You should register a Mobile Credential to this Cardholder before registering a Digital ID, so they can receive the Digital ID on their mobile device.</li><li>Only one Digital ID per Digital ID Type can be registered to each Cardholder.</li></ul></td></tr><tr><td>State</td><td>The state defaults to the Initial Card State as defined in the Card State configuration, and can be set to any other available state in the drop-down list.</td></tr><tr><td>Email</td><td>The Mobile Credential recipient's email address. The Registration Server will send the invitation email to this address. This field will be populated if the Cardholder has an Email Address PDF assigned.</td></tr><tr><td>Mobile</td><td>The Mobile Credential recipient's mobile phone number. The Registration Server needs this to authorise the phone. This field will be populated if the Cardholder has a Mobile Phone PDF assigned.</td></tr><tr><td>Phone ID</td><td>This field enables you to identify the phone that will be authorised, (i.e. the Cardholder may have multiple phones).</td></tr><tr><td>Name</td><td>The Mobile Credential recipient's name. This field will be populated with the Cardholder's First Name.</td></tr><tr><td>Number</td><td>Each Card requires an encoded number to uniquely identify it. The card number format of the selected Card Type will determine what characters can be used, as follows:<br><strong>Decimal</strong><br>A decimal card range is supported. The system "auto-allocates" a card number, (i.e. the next unassigned number for the selected Card Type), however, this can be changed before saving your changes on this screen.<br><strong>Text</strong><br>If the selected Card Type has a syntax string configured, you will be forced to enter a card number that fits that definition. There will be a red border around this field, and a message indicating what the expected format is will display when the field has focus, as shown in the following example:<br><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-004e38bccb7d0832c40d8edafc5d0165285433be%2Fcardnumberformat.png?alt=media" alt=""><br><br><strong>Note:</strong> A maximum of 251 characters are supported. However, with some languages this may be less as some characters use more than one byte.</td></tr><tr><td>Issue Level</td><td>This is set to the default for the Card Type. It can be changed for a different value as long as it is within the allowable range for issue levels. If the Card Type is changed, the system will reset this to the default for the new Card Type.</td></tr><tr><td>From</td><td>This defaults to the 'from date and time' for the Card Type, Mobile Credential Type, or Digital ID Type. This can be overtyped, but if the Card Type is changed, the 'from date' will be reset. This field can be left blank.<br>If the date/time is in the future and the <strong>Enabled</strong> check box is checked, the warning message <em>"Card not yet activated"</em> will appear to the left of the <strong>Cancel</strong> button.</td></tr><tr><td>Until</td><td>This defaults to the 'until date and time' for the Card Type, Mobile Credential Type, or Digital ID Type. This can be overtyped, but if the Card Type is changed, the 'until date' will be reset. This field can be left blank.<br>If the date/time is in the past and the <strong>Enabled</strong> check box is checked, the warning message <em>"Card expired"</em> will appear to the left of the <strong>Cancel</strong> button.</td></tr><tr><td>Resident</td><td>Check this box if you require the details of this Cardholder to be stored (resident) at the Controller. This is unchecked by default.<br><br><strong>Note:</strong> Mobile Credentials are stored on Controller 6000s only.<br>The Controller stores a 'resident' Cardholder and security parameters database to enable it to carry out access control and security functions. The Cardholder database stores access data for Cardholders who will regularly use the devices attached to that Controller. It enables the Controller to make access control decisions instantaneously.<br>For Cardholders that are not included in the resident Cardholder database, when they present their Card or Mobile Credential, the Controller requests access information from Command Centre. Their information is then stored on the resident database, but may get discarded if the Controller Cardholder database becomes full and another unknown user presents their Card or Mobile Credential. If communications fail and the Cardholder information is not in the Controller, that Cardholder will not be able to gain access.</td></tr></tbody></table>

</details>

2. Click the **OK** button.

   If valid, the **Assign Card** pop-up will close and the Card, Mobile Credential, or Digital ID will appear in the grid in the Cardholder Cards tile.

   **Note:** If you decide to cancel this change, the **Revert to Saved** button allows you to do so before saving it.
3. Click the **Save** button.

**Note:** The number of Mobile Credentials you can register is limited. Refer to the string 'Mobile Credentials' within the 'Limits' section of your license file. If an invitation email expires (e.g. the Cardholder didn't accept the invitation in the allotted time), deleting the credential registered will free-up another Mobile Credential.

To assign an already-encoded card to a Cardholder by badging the card at a Reader:

1. Badge the encoded card at your Workstation’s designated Reader. It does not matter whether access is granted or denied.

   **Note:** This must be a Reader that is attached to this Workstation’s ‘Assign Card Door’, specified in Gallagher Configuration Client. For details, refer to the "Configuration tab" section in the topic *"Creating a new Workstation item"* in the Gallagher Configuration Client Help.
2. If you badged the card at the correct Reader, the **Assign Card from Reader** button becomes enabled. Click **Assign Card from Reader**.

   If successful, the card will appear in the grid in the Cardholder Cards tile. If the card is still assigned to another Cardholder, you will get a ‘Card Assignment Warning’ pop-up which will let you remove it from the other Cardholder or cancel.
3. Click the **Save** button.

### Registration process

<table><thead><tr><th width="69">Stage</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>An operator uses the Cardholder Cards tile in Command Centre to register a mobile credential with a user. When registered, a request is sent from Command Centre to the Command Centre Cloud. Command Centre sends the user's: email address, phone number, invitation expiry time, and mobile credential identifier.</td></tr><tr><td>2</td><td>The Command Centre Cloud sends an invitation email to the user's email address. This email contains a link to the Gallagher Mobile Connect App. The user must download and install the App on their device. The email also contains an <strong>Accept Credential</strong> button. The user must accept the credential.</td></tr><tr><td>3</td><td>The Command Centre Cloud sends an SMS containing a six-digit confirmation code to the user's phone number. The user must enter the six-digit code into the App in order to authorise their device.</td></tr><tr><td>4</td><td>The user must specify their second authentication factor, either PIN or fingerprint. If the door requires a second authentication factor, this must be entered using the device, not the keypad on a reader.</td></tr><tr><td>5</td><td>There may be a delay of up to 90 seconds before registration of the device reaches the Command Centre Server. Badging at a reader before the credential status changes to "Active" will result in "Access Denied".</td></tr><tr><td>6</td><td>The user can now request access at a Gallagher reader.<br><br><strong>Note:</strong> The credential identifier is stored on the Gallagher Controller. Internet connectivity is not required for a user to request access at a Gallagher reader.</td></tr></tbody></table>


---

# 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/using-command-centre/working-with-viewers/tile-actions/cardholder-cards-tile-actions/assigning-a-card-credential-or-digital-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.
