> 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-user-guide/setting-up-a-new-environment/before-you-start/prerequisites.md). # Prerequisites What you need in place before starting a new environment setup. * A Kenai administrator account on the new organisation * Gallagher Configurator access * Access to the server or VM that will host the connector * Permission to install software on that machine * Permission to edit files under `ProgramData`, or to copy values into them {% hint style="warning" %} If the connector will not sit on the Command Centre server, plan for it in advance. A split install needs additional networking entries in the configuration file. {% endhint %} The most common blocker is not having install rights on the server. Confirm this before you begin. --- # 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-user-guide/setting-up-a-new-environment/before-you-start/prerequisites.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.