> 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/kenai-release-notes/readme.md).

# Kenai Release Notes

Keep up-to-date with the most recent releases for the Kenai platform.

## What's new?

{% tabs fullWidth="false" %}
{% tab title="Custom field mapping" icon="arrow-right-arrow-left" %}

### Custom field answers reach Gallagher

A question from the custom field library can now be mapped onto a Gallagher personal data field in v5.1.4, so what a visitor answers at sign-in is written to their cardholder.

<a href="/knowledge-hub/kenai-release-notes/2026/september/v5-1-4.md" class="button primary">Find Out More</a>
{% endtab %}

{% tab title="Custom fields" icon="list-check" %}

### Custom sign-in form fields are generally available

The questions a customer adds to their visitor sign-in forms are configured in the dashboard and generally available from v5.1.2: a library of fields per location, a check-in form per visitor type composed from it, and conditions between the questions on a form.

<a href="/knowledge-hub/kenai-release-notes/2026/september/v5-1-2.md" class="button primary">Find Out More</a>
{% endtab %}

{% tab title="Gallagher events" icon="door-open" %}

### What a card event at a Gallagher door does

Integrations configuration extends to what a card event at a Gallagher door does: two server-side actions that run on the connector, and two events returned to Kenai.

<a href="/knowledge-hub/kenai-release-notes/2026/september/v5-1-2.md" class="button primary">Find Out More</a>
{% endtab %}
{% endtabs %}

## All releases

Use the side navigation panel to look through other recent Kenai platform updates.


---

# 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/kenai-release-notes/readme.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.