> 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/products/integrations/elevators/kone/kone-office-flow.md).

# KONE Office Flow

Understand KONE Office Flow cardholder synchronization, licensing, and Command Centre items.

| Attribute     | Value                                                          |
| ------------- | -------------------------------------------------------------- |
| Status        | Current                                                        |
| Introduced in | Pre-vEL9.10 (cardholder sync); vEL9.10+ (event reporting)      |
| Relationship  | Standalone. Operates independently of KONE serial and KONE ELI |
| Purpose       | Data synchronization only. Not for elevator access control     |
| Licensing     | Licensed feature (`Kone Access=1`)                             |

{% hint style="warning" %}
KONE Office Flow does not provide elevator access control. It synchronizes cardholder records and access rights with KONE Office Flow. For floor access control, use [KONE ELI](/knowledge-hub/products/integrations/elevators/kone/kone-eli.md) or [KONE serial integration](/knowledge-hub/products/integrations/elevators/kone/kone-serial-standard.md).
{% endhint %}

### How it works

The Gallagher KONE Office Flow integration synchronizes Command Centre cardholder records with KONE Office Flow.

Manage cardholders in Command Centre. Their details and access rights update in KONE Office Flow.

From vEL9.10, Command Centre receives access and service online or offline events.

### Command Centre items

| Item                           | Description                                                                                                          |
| ------------------------------ | -------------------------------------------------------------------------------------------------------------------- |
| **Kone Service**               | Contains KONE Office Flow connection details. Imports lift decks, actions, areas, and terminals into Command Centre. |
| **Kone Validity Time**         | A Command Centre schedule representing a KONE Office Flow validity time.                                             |
| **Kone Elevator Access items** | Represents KONE Office Flow access rights. Configure these on the **Kone Elevator Access** administration tab.       |

### Licensing

Gallagher KONE Office Flow is a licensed feature. The license must contain:

```
[Limits]
Kone Services=X   (where X is the max number of Kone Service items configurable on site)

[Features]
Kone Access=1
```

### Configuration

Configuration is documented in the release note **Release Note KONE Office Flow Integration.pdf**, located in the Command Centre installation files under:

```
Utilities\System Interfaces\KONE Office Flow Integration
```

Latest release note (external Gallagher reference):

* [Release Note KONE Office Flow Integration.pdf](https://media.gallagher.com/m/7c9db0380f0cf989/original/Release-Note-KONE-Office-Flow-Integration.pdf)

***

### Related content

* [KONE](/knowledge-hub/products/integrations/elevators/kone.md)
* [KONE ELI](/knowledge-hub/products/integrations/elevators/kone/kone-eli.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/products/integrations/elevators/kone/kone-office-flow.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.