> 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/cloud-services/kenai.md).

# Kenai

Manage visitors, employees, evacuations and bookings with Kenai, integrated with Command Centre.

Kenai is a cloud-based **workplace access intelligence** platform. It manages visitors and employees from invitation or directory entry through to the historical record, giving you a live view of who is expected, who is onsite, and how site-access workflows are running. It sits alongside access control. Command Centre grants the access; Kenai runs the visitor and workplace processes around it and provisions that access automatically through the **Kenai Connector**.

### What it is

Kenai lets you run a professional, secure and measurable check-in operation across one site or many. Visitors pre-register online, check in touchlessly at a kiosk, and their hosts are notified automatically by email, SMS, WhatsApp or Teams.

The platform is made up of these modules:

<table><thead><tr><th width="220">Module</th><th>Description</th></tr></thead><tbody><tr><td>Visitor management</td><td>Invites, online pre-registration (NDAs, inductions, parking), and touchless kiosk check-in by QR code or facial recognition, with badge printing and host notifications.</td></tr><tr><td>Employee management</td><td>A single log of every arrival and departure, with team office hours, return-to-work patterns and timesheet exports.</td></tr><tr><td>Evacuation management</td><td>One presence log across every entry point. Start an evacuation in one click, notify everyone onsite, and track who is safe or needs help in real time.</td></tr><tr><td>Resource booking</td><td>Desks, rooms, parking and lockers in one system. Bookings turn into access, synced in real time with Command Centre.</td></tr><tr><td>Safety induction</td><td>Remote or onsite inductions with identity verification, version control and automated expiry, all in a central audit log.</td></tr><tr><td>Asset declaration</td><td>Visitors and employees declare assets, and security tracks them in and out with the Kenai Guardian app.</td></tr></tbody></table>

**How it works with Command Centre:**

* **Provision access before arrival.** Kenai creates cardholders and assigns access groups for visitors automatically.
* **Choose the credential.** Issue a Gallagher Mobile credential ahead of time, link a card onsite, or use a facial biometric.
* **Synchronise events.** Onsite access events create Kenai logs, so you always know who is onsite.
* **Disable access.** Trigger access changes from Kenai events, such as an expired induction.

Kenai connects to Command Centre through the Kenai Connector, a service installed on the Command Centre server (or a separate host) that uses a Command Centre REST API key.

### Related links

* [Kenai part numbers](https://help.security.gallagher.com/knowledge-hub/products/cloud-services/kenai/kenai-part-numbers.md)
* [Kenai User Guide](https://help.security.gallagher.com/knowledge-hub/kenai-user-guide/)
* [Kenai Release Notes](https://help.security.gallagher.com/knowledge-hub/kenai-release-notes/)


---

# 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/cloud-services/kenai.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.
