> 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/august/v5-1-1.md). # v5.1.1 **Date Released:** 30/08/2026 ### Integration configuration becomes self-serve **Area:** Integrations · Highlight The first slice of integrations goes self-service: **visitors core, for the Gallagher integration**. What an integration does on a visitor's journey has always been configured by Kenai; from this release a customer authors it on the same configuration surface as everything else. * **One configuration for all visitor types**\ Visitor events are authored at the **all-visitors level**: one configuration that applies across every visitor type. * **Seven events**\ Sign-in, sign-out, badge linking, pre-registration credentials, access passes, and induction activation and expiry, each one switchable and configurable on the All lane. * **Live connection status**\ A read-only connection tab shows the person configuring a location what the connector makes available to that location, as set up by the site administrator under platform services. ### Agreement images and version history **Area:** Agreements Agreements gain images, and versions are managed with history and restore. * **Images in agreements**\ An author places a picture as its own block in the agreement and sizes it, and it is available on the kiosk, in pre-registration, and in the signed PDF. * **Published versions are read-only**\ Versioning keeps one active version and, while edits are underway, one working successor. A version visitors may have signed is read-only; content changes create a new version. * **Version history and restore**\ Any version can be read back in the editor, and restored as the starting point for a new one. * **Agreement-wide settings**\ Signing frequency and receipt email are settings of the agreement itself; they apply whichever version is current. Learn more: [The visitor pre-registration flow](/knowledge-hub/kenai-user-guide/visitor-management/pre-registration.md) ### Printed badge configuration **Area:** Badges The printed visitor badge is now designed in the dashboard: what each line says, the badge image, and how the timestamp reads. * **Badge lines are templates**\ Each line mixes the author's own text with fields such as the visitor's name or their host, inserted from a token bar into the line being edited. * **The preview matches the printer**\ The on-screen badge preview shows exactly what the kiosk will print, and warns while the design is not yet the one in use. * **Timestamp format**\ The date order and whether a clock is shown are separate choices. * **Header image**\ An optional header image, a logo for example, prints at the top of the badge and is uploaded as part of the design. * **Auto-cut**\ Whether the printer cuts the badge automatically is a switch. ### Induction configuration **Area:** Induction Induction is authored once: one switch, one video, one quiz and one validity, applied to every channel that shows it, from the kiosk to pre-registration to the employee link. * **Induction video**\ The induction can carry a video or run without one, and the video is uploaded in the dashboard. * **Version**\ An induction carries a version. Raising it expires every completed induction, so everyone inducts again on their next visit; it sits behind an explicit confirmation. * **One validity**\ How long a completed induction stays valid is one number for the location, applied to every audience on every channel. * **Questions and quiz**\ Each question has its own order, a mandatory switch, a visibility switch, and answer options marked correct or not, with at least one correct answer per question. The quiz asks all questions or a chosen number, optionally shuffled. Learn more: [Kiosk induction](/knowledge-hub/kenai-user-guide/inductions/kiosk-induction.md) ### Evacuation roll call configuration **Area:** Evacuation Evacuation roll call joins the configuration surface. * **A single switch**\ Roll call is switched on or off per location: on enrols on-site visitors in the roll call, off clears it. Learn more: [What is Evacuation Management?](/knowledge-hub/kenai-user-guide/evacuation/evacuation-overview.md) ### Custom sign-in form fields (pending) **Area:** Custom fields · Pending validation The questions a customer adds to their visitor sign-in forms become configurable like everything else. * **A library of fields**\ The questions themselves are defined once for the estate: the label, helper text, input type and, for a dropdown, its choices. * **Per-visitor-type check-in forms**\ Each visitor type's check-in form is composed from that library, choosing which questions that type is asked. {% hint style="info" %} **Pending validation** Shipped in this release, pending final validation and testing before it is switched on. {% endhint %} Learn more: [The visitor pre-registration flow](/knowledge-hub/kenai-user-guide/visitor-management/pre-registration.md) ### Quality of life and platform services **Area:** Quality of life · Platform services * **The dashboard updates immediately**\ Devices and processing have always picked up configuration changes live; the dashboard now does too. A changed location description or organisation logo is visible right after the change, **without signing out and back in**. * **Permission changes apply live**\ A permission grant, change or removal reaches the affected user's open dashboard immediately, without a reload, and administrators viewing the admins list see it as it happens. * **Help and support built in**\ The help menu opens the new documentation site, and support opens chat directly from the dashboard with email as the fallback. The old help links are retired. * **Kiosk device logins**\ An administrator can create, reset and retire a dedicated device login for a kiosk. Device logins live on the device domain and are **denied on every web surface**, so a kiosk credential can never be used to reach the dashboard. Learn more: [Get support and check status](/knowledge-hub/kenai-user-guide/support/getting-support.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/august/v5-1-1.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.