> 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/mobile-connect/setting-up-digital-id-types.md).

# Setting up Digital ID Types

### Introduction

This procedure describes how to create a Digital ID Type. Digital ID Types are required for you to register new Digital IDs for Cardholders. When registering a Digital ID, you select one of your configured Digital ID Types.

The 'card expiry' feature allows the life of a Digital ID to be specified by defining a 'From' time and date and an 'Until' time and date. Digital IDs with these times defined are enabled between those times and are referred to as Scheduled Card Expiry.

**Note:** The "Configure Site" operator privilege is required to perform this procedure.

***

### Configuration

To set up an additional Digital ID Type, perform the following procedure in Gallagher Configuration Client:

1. Click **Configure** from the menu bar, then **Card Types**.

   The **Card Type** window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. **Right-click** and select **New\...Digital ID Type**.

   By default the **General** tab displays.
3. Complete the fields as required.

   For further detail see [General tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.md).
4. Click the **Setup** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-44dbc9b7a3fd3098705fbebb9356263953847645%2Fdigitalidtype.png?alt=media)
5. From the **Card State Set** drop-down box, select the appropriate Card State Set to be associated with this Digital ID Type.

   **Note:** Once the Card State Set is assigned to the Digital ID Type and saved, it cannot be changed. Bulk changes can be used to change the Digital ID Type if an alternative set of Card States is required.
6. In the **Card Defaults** section, you can activate the Digital ID for either a specific Date Range or a Fixed Duration.

   Click the appropriate radio button:

   <table><thead><tr><th width="121">If you select...</th><th>then...</th></tr></thead><tbody><tr><td>Date range,</td><td><p>in the <strong>From</strong> and <strong>Until</strong> fields, set the dates and times that Digital IDs of this type will be activated and will expire.<br><br><strong>Notes:</strong></p><ul><li>If you do not enter a date in the <strong>From</strong> field, when a Digital ID of this type is registered to a user and the Digital ID is enabled, activation will be immediate.</li><li>If you do not enter a date in the <strong>Until</strong> field, the Digital ID will not expire.</li></ul></td></tr><tr><td>Fixed Duration,</td><td>set the duration by selecting an option from the drop-down list, (i.e. Minutes, Hours, Days, Weeks, Months or Years) and entering the appropriate number, (e.g. 2 Weeks).<br><br><strong>Note:</strong> When fixed duration is selected, the expiry date will be determined from the assignment date with the configured offset / duration.</td></tr></tbody></table>

   When a Cardholder is registered to a Digital ID of this type, (i.e. on the **Cardholder Cards** tile in Command Centre Client), the default **Until** date will reflect the expiry date configured here.
7. The **Advance notice** section of this screen allows you to configure notifications of upcoming Digital ID expiries to be sent when the specified period is reached. Warning notifications are given via the Gallagher Mobile Connect app, and are sent for all Digital IDs regardless of status.
8. Do you want to enable Digital ID expiry notifications?

   <table><thead><tr><th width="73">If...</th><th>then...</th></tr></thead><tbody><tr><td>yes</td><td><ul><li>Set the <strong>Period</strong> to the value that represents the number of days, weeks, months or years before Digital ID expiry when warning notifications will be sent.</li><li>Select the unit of time (Days, Weeks, Months, or Years) from the drop-down list.</li><li>Ensure the <strong>Enable card expiry notification</strong> check box is checked.</li></ul></td></tr><tr><td>no</td><td>leave the <strong>Period</strong> as 0 days, and deselect the <strong>Enable card expiry notification</strong> checkbox.</td></tr></tbody></table>
9. Click the **Custom Fields** tab if you want to add and assign a custom field value to this Digital ID Type.

   For further details regarding the **Custom Fields** tab, see [Custom Fields](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/custom-fields.md).
10. Click the **Notes** tab if you want to add a note(s) about this Digital ID Type.

    For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
11. Click **OK** to 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/mobile-connect/setting-up-digital-id-types.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.
