> 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/using-command-centre/working-with-viewers/tile-actions/cardholder-passenger-details-tile-actions.md).

# Cardholder Passenger Details Tile actions

The Cardholder Passenger Details Tile allows default floors and passenger types to be assigned to ThyssenKrupp Elevator Groups for a Cardholder. This tile is only applicable to the Cardholder Viewer and will only appear if your site license file contains the following options:

`[Features]`\
`ThyssenKrupp EthernetHLI=1`

The number of Kiosks is also licensed:

`[Features]`\
`ThyssenKrupp Kiosks=X` (Where `X` is the maximum number of Kiosks that can be created)

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

The tile is populated with default floors or passenger type options that have previously been assigned. It will appear empty if none have been assigned. The ThyssenKrupp Elevator Groups that a Cardholder has access to is based on the Access Groups they belong to, and the Access Zones assigned to those Access Groups and Elevator Groups.

A cardholder needs to be associated with default floor(s) within buildings to get the benefit from the automated floor selection.

**Default Floors**

Having a default floor configured for an elevator group means that as soon as the cardholder badges at an Elevator System Kiosk, they are directed to a particular elevator which will take them to the default floor without any further interaction.

**Passenger Types**

Assigning passenger types to Cardholders differentiates the behaviour in the ThyssenKrupp Elevator System.

<details>

<summary>Click here for an explanation of the Passenger Types</summary>

<table><thead><tr><th width="130">Passenger Type</th><th>Description</th></tr></thead><tbody><tr><td>VIP</td><td>Allows users to swipe a card or enter a PIN to isolate the elevator and provide uninterrupted access to a designated floor, (e.g. tenants paying a premium to reside on a top floor can experience a premium ride to their floor).</td></tr><tr><td>Service</td><td>Service personnel can call an empty elevator and ride it non-stop to their destination floor by registering a call via a card swipe or PIN entry that is pre-programmed to grant access, (e.g. hospital staff transferring patients requiring privacy between floors).</td></tr><tr><td>Code Blue</td><td>Used for emergencies, when the first-available elevator car needs to be called, (e.g. in a hospital). A Code Blue call will remove the car from automatic operation and deliver the user to the destination floor, and then return it to automatic operation.</td></tr><tr><td>Capture</td><td>Authorised users can select and recall specific elevators to specific floors using a kiosk or other destination input device. Once captured, the elevator car can be placed on independent service to allow for cleaning or maintenance.</td></tr><tr><td>Express</td><td>Maximises the trip speed so that the elevator can be cycled continuously between floors for a pre-determined duration, (e.g. in a hotel so food can be transported efficiently from their kitchen to ballroom).</td></tr><tr><td>Service 2</td><td><em>Reserved for additional features.</em></td></tr><tr><td>Service 3</td><td><em>Reserved for additional features.</em></td></tr></tbody></table>

</details>

**Note:** While Cardholder Passenger Types for ThyssenKrupp are configured in Command Centre Client, ThyssenKrupp Elevator Systems are primarily configured using Command Centre Configuration Client. See "ThyssenKrupp Elevator Systems" in the *Configuration Client Help file* for further detail.

**Notes:**

* If the Cardholder doesn’t have access to any Elevator Groups, a message will display on the Cardholder Passenger Details Tile indicating that no Elevator Groups are available.

  ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-a64a5f4022236f97c945d1467e7457623421a3fe%2Fcholdpassengerdetails_operational_nogroups.png?alt=media)
* If a cardholder doesn’t have access to the default floor the text shows in red.

  ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-edad7208ba2c5525b05d9d9c39c89806af31a541%2Fcholdpassengerdetails_operational_invaliddefaultfloor.png?alt=media)
* Default floors can be changed via a Cardholder Bulk Change. See [Creating a new Cardholder Bulk Change](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/bulk-changes/creating-a-new-cardholder-bulk-change.md) for the procedure.

### Tile Actions

<details>

<summary>Adding default floors</summary>

Default floors can be added to the Cardholder Passenger Details, as follows:

1. Click on the **Default Floor** drop-down box beside the Elevator Group you want to assign a Default Floor to.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-c6aff1255187241adb967752311be86d4de3d0d8%2Fcholdpassengerdetails_operational_defaultfloordropdown.png?alt=media)
2. If necessary, search for Access Zone you want by entering characters in the Search field.
3. Select the appropriate Access Zone from the drop-down list.
4. Repeat Steps 1 to 3 for each Elevator Group you want to assign a Default Floor to.
5. Click the **Save** button.

</details>

<details>

<summary>Adding Passenger Types</summary>

Passenger Types can be added to the Cardholder Passenger Details, as follows:

1. Click on the **Passenger Type** drop-down box beside the Elevator Group you want to assign a Passenger Type to.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-775c40b973861320b35a8ceddc07684b0f3dafea%2Fcholdpassengerdetails_selectpassengertype.png?alt=media)
2. Tick the required Passenger Type(s).
3. Repeat Steps 1 to 2 for each Elevator Group you want to assign a Passenger Type(s) to.
4. Click the **Save** button.

</details>


---

# 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/using-command-centre/working-with-viewers/tile-actions/cardholder-passenger-details-tile-actions.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.
