> 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.md).

# Card Types

### Introduction

Card Types are required in order to allow you to create New Cards for Cardholders. This option creates card types that will be used in the Command Centre system.

***

### Inactive Card Expiry

The "card expiry" feature allows the life of a card to be specified by defining a "From" time and date as well as an "Until" time and date. Cards with these defined are therefore enabled between those two points in time and are referred to as Scheduled Card Expiry. The "Inactive Card Expiry" feature provides additional flexibility in the way card expiry can be defined.

Inactive Card Expiry enables the automatic disabling of cards, invoked after a period of card inactivity, within a Command Centre controlled site. The length of the period of inactivity is user configurable.

A card that has the Inactive Card Expiry feature enabled shall be disabled if no successful access events occur for that card over the configured inactivity timeout for the card's type. A successful access event is one of:

1. "Door Access Granted"
2. "Elevator Access Granted"
3. "Card Exit Granted"

A number of card authorisation features take precedence over Inactive Card Expiry, as follows:

* If a cardholder is de-authorised, (i.e the "Cardholder Authorised" checkbox is unchecked on the **Card** tab), then all of the cardholder's cards are disabled, irrespective of the "Inactivity" status.
* If a card is disabled, (i.e the "Card Enabled" checkbox is unchecked on the **Card** tab), then that card is disabled irrespective of the "Inactivity" status.
* If a card is expired according to the configured "From/Until" activation period on the **Card** tab, then the card is expired irrespective of the "Inactivity" status.

***

Select the item below that you require further detail on:

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Setting up Card Types](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/card-types/setting-up-card-types.md)


---

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