> 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/2026/september/v5-1-4.md). # v5.1.4 **Date Released:** 26/09/2026 ### Custom field answers reach Gallagher personal data fields **Area:** Integrations ยท Highlight A question from the custom field library can now be **mapped onto a Gallagher personal data field**, configured once for all visitor types, so what a visitor answers at sign-in is written to their cardholder. * **A question becomes a field mapping**\ On the all-visitors configuration, any active library question can be the source of a field mapping. The field picker offers only the Gallagher fields that question can be written to, so a text question meets a text field and a slider a numeric one. * **Choices map to values**\ For a dropdown or multi-select question, each choice is mapped to the value it writes. Onto a Gallagher list field, the choice is paired with one of the field's own list values; onto a text field, the choice's own text is written. * **The answer arrives as mapped**\ The visitor's answer reaches the cardholder as its mapped value on sign-in, badge linking, pre-registration credentials and access passes, one Gallagher field per mapped question. * **A changed answer is sent again**\ When a visitor updates their pre-registration and a check-in answer changes, the credential is sent to Gallagher again with the new answers, so a mapped field takes the new value. ### The payload preview shows what was sent **Area:** Integration Ops The payload preview on a transmitted Gallagher record now reads **the payload that was actually sent**, not only the event it came from. * **Every Gallagher field shows its sent value**\ Each personal data field on a sent record now shows the value that reached Gallagher, and a field whose value came from a source on the event shows the value as it went on the wire. * **The question behind a mapped field**\ A field written from a custom field mapping shows the question the visitor answered beneath the field name, so the sent value can be read against what was asked. ### One prompt per question type **Area:** Custom fields A custom field no longer carries its own helper text; **every question shows a fixed prompt for its type**. * **Prompts follow the input type**\ A text question prompts for an answer, a number for a number, a dropdown to select an option and a multi-select to select one or more. Helper text authored on a question is no longer offered or shown. Learn more: [The visitor pre-registration flow](/knowledge-hub/kenai-user-guide/visitor-management/pre-registration.md), [Check in at the kiosk](/knowledge-hub/kenai-user-guide/visitor-management/kiosk-check-in.md) ### Kiosk device logins by device id **Area:** Platform services Creating a kiosk device login now asks for **a device id only**; the sign-in address is composed from the location and shown before it is created. * **Device id is the only input**\ The administrator types a short device id. The address the device signs in with is built from the location and the device domain and shown as it will sign in, so every device login belongs to the location it was created at. * **Copy the address**\ Every device address carries a copy button, in the device list and in the preview when a login is created. ### Quality of life and reliability **Area:** Quality of life * **Reliability improvements**\ Asset photos shown when a visitor reopens an invite. Learn more: [Declare assets (visitor)](/knowledge-hub/kenai-user-guide/asset-management/declare-assets.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/kenai-release-notes/2026/september/v5-1-4.md?ask=&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.