> 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/editing-a-universal-credential-type.md).

# Editing a Universal Credential Type

### Introduction

This procedure describes how to edit a Universal Credential Type.

**Note:** The "Configure Site" or "Edit Card Types", and the “Manage Keys” operator privilege is required to perform this procedure.

### Procedure

1. Select or search for the credential type on the Universal Credentials Viewer.

   The General page displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2FUvBw8CEnyIMOdHXn5KmZ%2F45008.png?alt=media)
2. Edit the **Name** (limited to 110 characters) for this credential type, if required.
3. Edit the **Description** (limited to 200 characters) for this credential type, if required.
4. Select a **Division** from the drop-down list, if required.
5. Select the **Format** tab. The Format page displays.

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

   Fields that can be edited post creation of the credential type are:

   <table><thead><tr><th width="170">Field</th><th>Description</th></tr></thead><tbody><tr><td>TCI</td><td>Edit the Terminal Capabilities Identifier (TCI) belonging to the Apple credentials provided by the third-party credential provider in the TCI field.<br>The TCI advertised by the reader to display the correct badge in Apple Wallet. A TCI with length 0 is invalid.</td></tr><tr><td>Customer Code</td><td>Edit the Customer Code (the last three bytes of the DFNAME) in the <strong>Customer Code</strong> field. Alternatively, enter the full DFNAME and the Customer Code will be extracted automatically.</td></tr><tr><td>Terminal Subtype</td><td>Select Corporate or University as the <strong>Terminal Subtype</strong>. The third-party credential provider will issue either Corporate or University wallet credentials.</td></tr><tr><td>Read Key Number</td><td>Edit the Read Key Number (2-6) belonging to the key shared from the third-party Gallagher system in the <strong>Read Key Number</strong> field.</td></tr><tr><td>Read Key</td><td>Edit the Read Key belonging to the credential in the <strong>Read Key</strong> field. This is a 32 hexadecimal key.<br><br><strong>Note:</strong> Changing the key may affect access for cardholders already assigned a credential using this credential type. This change takes effect immediately. All readers and controllers will be updated.</td></tr><tr><td>Privacy Key</td><td>Edit the Privacy Key belonging to the Apple credentials in the <strong>Privacy Key</strong> field. This is a 32 hexadecimal key.</td></tr><tr><td>Site Code Format</td><td>Select Decimal or Hexadecimal as the <strong>Site Code Format</strong>. Typically, decimal is used when displaying and entering a Site Code in Command Centre. The chosen format does not change the data stored on the credential.</td></tr><tr><td>Site Code</td><td>Edit the Site Code belonging to the physical format in the <strong>Site Code</strong> field. Command Centre references the Site Code to identify cards of use on the site. Different Site Codes allow you to use identical keys and card numbers.<br><br><strong>Note:</strong> If you don’t know the Site Code at the time of credential type creation, defining it now, means new credential assignments will display only the card number, matching that printed on the card.</td></tr><tr><td>First Bit of Site Code</td><td>Edit the first bit for the Site Code. Command Centre will start reading bits from this position for the Site Code.<br><br><strong>Note:</strong> Not all physical formats have Site Codes. If this is the case, leave the field blank or enter 0.</td></tr><tr><td>Bits in Site Code</td><td>Edit the number of bits to read for the Site Code. This number of bits define the Site Code.</td></tr></tbody></table>
6. Select the **Duration Defaults** tab. The Duration Defaults page displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2F6DDonRsxhBXaXiYv0Ibo%2F45010.png?alt=media)
7. Configure the date and time this credential type **Starts**.

   <table><thead><tr><th width="170">If you select...</th><th>then...</th></tr></thead><tbody><tr><td>Upon assignment</td><td>Credentials of this type will be active from the time of assignment.</td></tr><tr><td>On a specific date</td><td>Set the date and time that credentials of this type will be activated in the <strong>Date</strong> and <strong>Time</strong> fields.</td></tr></tbody></table>
8. Configure the date and time this credential type **Expires**.

   <table><thead><tr><th width="170">If you select...</th><th>then...</th></tr></thead><tbody><tr><td>Never</td><td>Credentials of this type will never expire unless manually disabled or automatically disabled due to inactivity (if enabled).</td></tr><tr><td>After a specific duration</td><td>Set the <strong>Duration</strong> by entering a value and 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 a duration is specified, the expiry date will be determined from the start date with the configured offset/duration.</td></tr><tr><td>On a specific date</td><td>Set the date and time that credentials of this type will expire in the <strong>Date</strong> and <strong>Time</strong> fields.</td></tr></tbody></table>

   **Note:** When a credential of this type is assigned to a cardholder, (i.e. on the **Cardholder Cards** tile in Command Centre Client), the **Until** Date will reflect the expiry date configured here.
9. Do you wish to automatically disable inactive credentials of this type?

   <table><thead><tr><th width="83">If...</th><th>then...</th></tr></thead><tbody><tr><td>yes</td><td><p>Enable the <strong>Automatically disable inactive credentials of this type</strong> toggle, then enter the number of days of inactivity that will disable this credential.<br><br><strong>Notes:</strong></p><ul><li>When first enabled the default timeout = 30 days. The range is 1-999 days.</li><li>If set to disable after 1 day of inactivity, the cardholder’s credential will become disabled 24 hours to the second after the Save button is clicked, (e.g. if saved on 27/11/2026 at 16:10:15; and the credential has not been used, then it will be disabled on the 28/11/2026 at 16:10:15).</li><li>This feature will not work unless card activity events are configured to log events throughout the site. Refer to Event Defaults for further detail.</li></ul></td></tr><tr><td>no</td><td>go to next step.</td></tr></tbody></table>
10. The **Send Expiry Notification** section allows you to configure warning notifications of pending credential expiry, when the specified period is reached, for all credentials regardless of status.

    Do you want to configure credential expiry notifications?

    <table><thead><tr><th width="83">If...</th><th>then...</th></tr></thead><tbody><tr><td>yes</td><td>enter the period before credential expiry that a warning notification will be sent. Select a period from the drop-down, (i.e. days, weeks, months, or years).</td></tr><tr><td>no</td><td>disable the <strong>Send Expiry Notification</strong> toggle.</td></tr></tbody></table>
11. Select the **Notes & History** tab.

    The Notes & History page displays. This page displays the credential type creation date and time, who last modified the credential type's properties and when, and allows you to add any relevant notes about the credential type.

    ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2FOdlL6sN2hcEa9SX0qKVD%2F45011.png?alt=media)
12. Enter any note(s) you want to record in the **Notes** field.

    **Notes:**

    * The **Notes** field accepts at least 2,500 characters.
    * The scroll bar can be used to move through the text, or the normal navigation keys can be used, (i.e. Up and Down Arrows, Page Up and Page Down keys).
13. The **History** grid is "read-only" and shows Audit history details for the credential type.

    Each entry represents one change made to the credential type. The entries are sorted by time, in descending order, with the latest change at the top.

    **Note:** Extra details can be revealed for an entry by selecting (highlighting) an entry.
14. Select **Save**.

### Result

Your edits to the Universal Credential Type will be saved.


---

# 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/editing-a-universal-credential-type.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.
