> 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/licensable-features/visitor-management/command-centre-site-configuration/creating-card-types.md).

# Creating Card Types

### Introduction

A Visitor Badge Card Type needs to be configured in Command Centre if you intend printing badges or using visitor access cards.

**Note:** Bureau card types cannot be used in Visitor Management.

### Procedure

1. Click **Configure** from the menu bar.
2. Click **Card Types**.

   The **Card Type** List Window opens.
3. **Right click** and select **New\...Card Type**.

   By default the **General** tab displays.
4. Configure the new Card Type as required.

   See [Setting up Card Types](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/card-types/setting-up-card-types.md) for further detail.

   **Note:** The maximum Card Number normally allowed in Command Centre (on the **Setup** tab of the Card Type), is approximately 605 characters in decimal format, (i.e. 2008 bits). However, for Visitor Management the maximum Card Number allowed is 20 digits, (i.e. 18,446,744,073,709,551,615).

### Using recyclable visitor access cards

Recyclable access cards can be held by Receptionists for issuing to visitors when they arrive for a visit. When visitors leave, they return the access cards to the Receptionist so they can be reused for other visitors when required.

If you intend assigning cards to visitors, using recyclable access cards, you need to:

1. Encode all of the cards to be used for visitors.

   See [Printing and/or Encoding a card from a cardholder](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/printing-encoding-cards/printing-and-or-encoding-a-card-from-a-cardholder.md) for further detail.
2. Remove these cards from the cardholder so they can be reassigned to visitors as and when required.


---

# 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/licensable-features/visitor-management/command-centre-site-configuration/creating-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.
