> 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/licensable-features/kone-eli-hli-feature.md).

# Kone ELI HLI feature

The Kone ELI licensable feature allows Command Centre to support message type 11. This enables CC to set flags against a Cardholder to allow for a particular behaviour. The flags can be used to prioritize and/or restrict access to certain floors based on the Cardholder privileges. With message type 11, CC can be used to configure both front and rear doors for access.

This feature also supports Kone Destination Operation Panels (DOPs) and Kone Car Operation Panels (COPs). COPs are located inside the elevator car. A Gallagher reader is positioned at each DOP or COP. When a cardholder badges their card at a reader, Command Centre instructs the Kone System which levels the cardholder has access to. The cardholder can then select a destination, limited to those floors. If the cardholder is using a DOP, the DOP will instruct the cardholder on which elevator car to use, alleviating the need for floor selection within the elevator car itself.

**WARNING:** If a cardholder badges at a reader associated to a Kone terminal (DOP or COP) and then walks away without selecting a floor, another user may select a floor based upon that cardholder’s access privileges until the configured floor selection timeout is reached. If any cardholder attempts to present another card during this time, their card read will be ignored. Any floor selection made will be subject to the first cardholders access privileges. The floor selection will be reported as belonging to the first cardholder.

<details>

<summary>Assign or Remove a Call Type</summary>

Once Call Types are configured, you can assign a Call Type to Cardholder. Each Elevator HLI can contain numerous Call Types. However, you can assign only one Call Type to a Cardholder from a particular Elevator HLI. To assign another Call Type to the same Cardholder, another HLI must be configured and assigned to the Cardholder.

1. From the Gallagher Command Centre menu, click **Viewers** > **Cardholder Viewer**.
2. Enter the Cardholder’s name in the search bar.

   The Cardholder is displayed.
3. Do you want to assign or remove a Call Type?

   <table><thead><tr><th width="100">To...</th><th>then...</th></tr></thead><tbody><tr><td>assign</td><td><ol><li>From the 'Cardholder Kone ELI Properties' tile, click <strong>Assign</strong>.<br>The Assign Elevator HLI window displays.</li><li>Select the check box for the appropriate Elevator HLI then, click the <strong>Add Selection</strong> button.<br><br><strong>Note:</strong> You assign multiple Elevator HLI to a Cardholder by selecting multiple check boxes.</li><li>From the <strong>Call Type</strong> drop-down list, select the appropriate Call Type.<br>By default, the first Call is selected. Calls are listed alphabetically.</li></ol></td></tr><tr><td>remove</td><td><ol><li>From 'Cardholder Kone ELI Properties tile, select an Elevator HLI.<br>By default, the first Elevator HLI is selected.</li><li>Click the <strong>Remove</strong> button.</li></ol></td></tr></tbody></table>
4. Select the **Save** button to keep your changes.
5. Select the **Revert to Saved** to undo changes.

</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/licensable-features/kone-eli-hli-feature.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.
