> 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/card-types/setting-up-card-types/setup-tab.md).

# Setup tab

1. Click the **Setup** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a6e026d1c5b0229df0f6f57837f6a2dad2abfc6b%2Fcardsetup.png?alt=media)

   Your site Facility Code is entered in the **Card Facility** section on this tab. Command Centre references the Facility Code to identify cards for use on site.

   Gallagher Security Management Systems supply sites with Facility Codes, and ensure different sites have different facility codes. This allows several sites to use identical card numbers.
2. If your site Facility Code has already been entered, then select it from the **Current Facility Codes** drop-down box.

   **OR**

   If you wish to enter your Facility Code, then enter the letter representing the **Region Code** for your Facility Code, and enter the number in the **Facility Code** field.

   **Notes:**

   * Facility Codes can only be used on one card technology.
   * One Facility Code cannot be used by two card types that have different card number formats. This is due to the difficulty in converting the byte array representation of a card number to its displayable string representation.
   * Gallagher Command Centre can support up to 256 Facility Codes on Gallagher Controller 6000s and 7000s.
3. The settings configured in the **Card Number** and **Card Defaults** sections will be used when you allocate a new card to a cardholder. They can then be overwritten if required.

   In the **Card Number** section select the appropriate option from the **Format** drop-down list:

   **Note:** The **Format** drop-down list is disabled once the Card Type is created and saved.

   <table><thead><tr><th width="122">If you select...</th><th>then...</th></tr></thead><tbody><tr><td>Decimal</td><td>the following additional fields display in the <strong>Card Number</strong> section:<br><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-26c75584b72bfaa7469943ed43940d030419e125%2Fcardsetuptab_decimalformat.png?alt=media" alt=""><br>Enter the range in the <strong>Range</strong> fields.<br>The Minimum Card Number is 1, and the Maximum is limited to approximately 605 characters in length, which is the number of digits for the result of 2^2008.<br>(Defaults = 1 to 16,777,215)<br><br><strong>Note:</strong> For 24-bit Gallagher cards, the number range has a limit of 1 to 16,777,215. For Magstripe card types, the number range has a limit of 1 to 65,500.</td></tr><tr><td>PIV</td><td>no additional fields populate the <strong>Card Number</strong> section.</td></tr><tr><td>Text</td><td><p>the following additional fields display in the <strong>Card Number</strong> section:<br><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e3b55a299064c027c0f9543da3ef571e1d95f9cf%2Fcardsetuptab_textformat.png?alt=media" alt=""></p><ol><li><p>If you want to force the card number format to fit a regular expression for the Card Type, enter a syntax string into the <strong>Syntax</strong> field. This string will be used to validate a card number that is entered by an Operator.<br><br><strong>Notes:</strong></p><ul><li>Refer to <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/card-types/setting-up-card-types/sample-regular-expressions.md">Sample Regular Expressions</a> for a list of example regular expressions.</li><li>The syntax string can be changed after the Card Type is saved, allowing the Operator to initially configure a strict pattern and later add additional patterns if requirement changes. <strong>For example:</strong><br>Card Numbers for alphanumeric vehicle number plates may initially support 2 English letters and 4 number digits, (e.g. 'AB1234') and later support 3 English letters and 3 number digits, (e.g. 'ABC123').</li></ul></li><li>Enter a description of the syntax in the <strong>Description</strong> field.<br><br><strong>Note:</strong> This message will be displayed to an operator if the value entered cannot be saved because it doesn't meet the regular expression validation.</li></ol></td></tr></tbody></table>
4. Select the appropriate **Card State Set** (if only one exists it will default) to be associated with this card type, from the drop-down box.

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

   Click the appropriate radio button:

   <table><thead><tr><th width="122">If you select...</th><th>then...</th></tr></thead><tbody><tr><td>Date Range,</td><td><p>set the date and time that cards 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 cardholder is issued a card of this type and the card is enabled, activation will be immediate.</li><li>If you do not enter a date in the <strong>Until</strong> field, the card 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 card of this type is assigned to a Cardholder, (i.e. on the **Cards** tab of a Cardholder’s properties in Configuration Client, or on the **Cardholder Cards** tile in Command Centre Client), the **Until** Date will reflect the expiry date configured here.
6. The **Issue Level** field allows the issue number to be incremented if a card is replaced, instead of needing to go through the process of creating a new card. (Range = 1 to 15)

   *For example:* A card may need to be replaced if the cardholder has lost their card.
7. The **Advance notice** section of this screen allows you to configure warning notifications of pending card expiry to be sent when the specified period is reached, for all cards regardless of status.
8. Check the **Card Issue Level must match default** checkbox if required.

   **Notes:**

   * When checked, the **Issue Level** field becomes disabled.
   * This setting can be changed again after the Card Type is saved if required.
   * If you are using the Salto integration and card numbers in 26 bit Wiegand format, changing the Issue Level on a card assignment will have no impact on a Cardholder’s ability to gain access through a Salto Door. Hence it is advised that you configure a default Issue Level (i.e. ‘1’) by checking the **Card Issue Level must match default** checkbox for all encoded cards using the 26 bit Wiegand format.
9. 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><ol><li>Set the <strong>Period</strong> to the value that is required to represent the number of days, weeks, months or years prior to card expiry to initiate the warning notification.</li><li>Ensure the <strong>Enable card expiry notification</strong> checkbox remains checked.</li></ol></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>


---

# 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/card-types/setting-up-card-types/setup-tab.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.
