> 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-mobile-credential-types.md).

# Setting up Mobile Credential Types

### Introduction

The Mobile Credential Type "Mobile Credential" is created by default when Command Centre is installed or upgraded. The following procedure describes how to create a new Mobile Credential Type, should an additional Mobile Credential Type be required.

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

***

### Configuration

To set up an additional Mobile Credential Type, perform the following procedures in Gallagher Configuration Client:

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

   The **Card Type** List 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\...Mobile Credential 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 each tab in turn to create a new Mobile Credential Type:

<details>

<summary>Setup tab</summary>

1. Click the **Setup** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-2def321cb230c734b3b76e10eabb39915360ebee%2Fmobilecredentialtype.png?alt=media)
2. Select the appropriate **Card State Set** (if only one exists it will default) to be associated with this Mobile Credential Type, from the drop-down box.

   **Note:** Once the Card State Set is assigned to the Mobile Credential Type and saved, it cannot be changed. Bulk changes can be used to change the Mobile Credential Type if an alternative set of Card States is required.
3. In the **Card Defaults** section you can activate the mobile credential 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>set the date and time that mobile credentials of this type will be activated and expire in the <strong>From</strong> and <strong>Until</strong> fields.<br><br><strong>Notes:</strong></p><ul><li>If you do not enter a date in the <strong>From</strong> field, when a mobile credential of this type is registered to a user and the mobile credential is enabled, activation will be immediate.</li><li>If you do not enter a date in the <strong>Until</strong> field, the mobile credential 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 mobile credential of this type, (i.e. on the **Cardholder Cards** tile in Command Centre Client), the **Until** Date will reflect the expiry date configured here.
4. The **Advance notice** section of this screen allows you to configure warning notifications of pending mobile credential expiry to be sent when the specified period is reached, for all mobile credentials regardless of status.
5. Do you want to enable card expiry notification?

   <table><thead><tr><th width="73">If...</th><th>then...</th></tr></thead><tbody><tr><td>yes</td><td>Set the <strong>Period</strong> to the value that is required to represent the number of days, weeks, months or years prior to mobile credential expiry to initiate the warning notification.<br>Ensure the <strong>Enable card expiry notification</strong> checkbox remains checked.</td></tr><tr><td>no</td><td>leave the <strong>Period</strong> as 0 days, and uncheck the <strong>Enable card expiry notification</strong> checkbox.</td></tr></tbody></table>
6. Configure the Mobile Credential Registration as required:

   <table><thead><tr><th width="166">Checkbox</th><th>Description</th></tr></thead><tbody><tr><td>Send invitation by email</td><td>Tick this option so cardholders can receive an invitation email from the Registration Server.<br>This makes an <strong>Email</strong> field appear on the Assign Card pop-up in the Command Centre Client when registering mobile credentials for a cardholder.</td></tr><tr><td>Send SMS verification code</td><td>Tick this option so the Registration Server can authorise cardholders’ mobile phones.<br><br><strong>Note:</strong> This makes a <strong>Mobile</strong> field appear on the Assign Card pop-up in the Command Centre Client when registering mobile credentials for cardholders.</td></tr></tbody></table>

</details>

<details>

<summary>Inactivity tab</summary>

1. Click the **Inactivity** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-69043ee2f72a056fa9eec34ab29b23136de86169%2Fmobilecredentialtypeinactivity.png?alt=media)
2. Do you wish to enable the Inactive Card Expiry feature?

   **Note:** All mobile credentials of this type shall share a common inactivity timeout if enabled.

   <table><thead><tr><th width="73">If...</th><th>then...</th></tr></thead><tbody><tr><td>yes</td><td>Check the <strong>Disable Inactive Cards</strong> checkbox.<br>Go to Step 3.</td></tr><tr><td>no</td><td>Leave the <strong>Disable Inactive Cards</strong> checkbox unchecked.<br>Go to Step 5.</td></tr></tbody></table>
3. Enter a figure to represent the number of days of inactivity that will disable a mobile credential.

   **Notes:**

   * When this feature is first enabled the default timeout = 30 days. The range is 1-999 days.
   * Users will be expired regardless of activity if mobile credential activity events are not configured to log events throughout the site. (Refer to [Event Defaults](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/event-defaults.md) for further detail.)

</details>

5. Click the **Custom Fields** tab if you want to add and assign a custom field value to this Mobile Credential 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).
6. Click the **Notes** tab if you want to add a note(s) about this Mobile Credential 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).
7. 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.

   **Note:** After you register your phone against the Cloud, there may be a delay of up to 90 seconds before it reaches the Command Centre Server. Badging at the reader before the credential status changes to "Active" will result in "Access Denied".


---

# 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-mobile-credential-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.
