> 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-3.md). # v5.1.3 **Date Released:** 21/09/2026 ### Existing organisations join the engine **Area:** Accounts ยท Highlight An organisation that predates the accounts portal can now be **brought under accounts management as it stands**, without re-provisioning it. Kenai runs the adoption for the customer. * **Every site becomes an order**\ Each of the organisation's sites becomes an active order with its own reference, so the estate is managed, licensed and renewed the same way as one created from an order. * **Configuration is read from what exists**\ The organisation's first configuration document is read from the settings it already runs on, not from a template, and no name a customer sees changes. * **Adoption is checked before it writes**\ The whole organisation is reviewed before the first write; anything that cannot be adopted is named, and nothing is changed until every site passes. * **Self-serve configuration opens separately**\ Adoption starts automatic processing for the organisation; configuration authoring in the dashboard is granted afterwards, as a separate step. ### Sign-in answers read as captured **Area:** Visitor log and invites A visitor log row and an invite now keep the form they were answered against, so **what a visitor answered stays readable whatever the form has become since**. * **Answers keep their labels**\ A choice answered on the sign-in form now keeps its label in the visitor log and on the invite, whether or not the form still offers that choice today, and it stays intact when another answer on the row is edited. * **Editing follows the form as captured**\ Which answers on a row can be edited follows the form as it stood when the row was captured, together with the editor's permissions; a later change to the form does not open or close answers already captured. Learn more: [Work the visitor log](/knowledge-hub/kenai-user-guide/visitor-management/visitor-log.md), [The invite log](/knowledge-hub/kenai-user-guide/visitor-management/invites/invite-log.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-3.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.