> 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/piv-card-support/enrolling-piv-and-piv-i-cards-using-a-pivclass-workstation.md).

# Enrolling PIV and PIV-I cards using a pivCLASS Workstation

### Introduction

PIV and PIV-I cards can be enrolled into Command Centre via either:

* **Command Centre Client** (the preferred method)

  Refer to the "PIV Cardholder Registration Process" in the *Gallagher Command Centre Client User Guide* for detailed instructions for this method.

  OR
* **a pivCLASS Workstation** (covered in this topic)

  pivCLASS provides cardholder and card data to Command Centre via the XML import. This data is required to be held in Command Centre to facilitate credential authentication.

  **Note:** In a multi-server system, enrolment of a PIV Cardholder (and associated PIV Card) need only occur at one server. All PIV cardholder details (including card details) will be replicated to all servers in a multi-server environment.

### Before you begin

Before you begin enrolling PIV and PIV-I cards ensure:

* the pivCLASS PACS Plug-in has been installed on the Command Centre Server.

  See [Installing pivCLASS PACS Plug-in](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/piv-card-support/installing-the-necessary-applications-tools-for-a-pivclass-workstation.md) for the procedure.
* pivCLASS Workstation has been installed on the workstation (either server or remote).

  See [Installing pivCLASS Workstation](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/piv-card-support/installing-the-necessary-applications-tools-for-a-pivclass-workstation.md) for the procedure.

### Procedure

1. Enrol this card in the pivCLASS Workstation.

   Refer to "Chapter 7: Identity Verification" of the *pivCLASS Registration Workstation Use Manual* ( **pivCLASS\_Registration\_Workstation\_User\_Manual.pdf** provided with the Gallagher Command Centre installation files), for a detailed procedure.

   The cardholder is registered with pivCLASS and also created in Command Centre.

   Additional credential and path validation is run from Command Centre upon import to ensure the validity of PIV card certificates. Any revoked, expired or not trusted cards are disabled and events/alarms are generated.
2. Configure the cardholders access.

   **Note:** If a cardholder is enrolled for a PIV card it will appear as 'read-only' on the **Cards** tab of their properties (in Configuration Client), or on the 'Cardholder Cards Tile' (in Command Centre Client). All fields will be pre-populated.


---

# 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/piv-card-support/enrolling-piv-and-piv-i-cards-using-a-pivclass-workstation.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.
