> 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/sites-and-locations.md). # Sites and locations How organisations, sites and locations relate, and what is configured at each level. Kenai structures every customer as an **organisation**, containing one or more **sites**, each containing one or more **locations**. Organisation settings reach every location beneath them. ## Site A site matches Gallagher's billing and account structure, and holds the connection to one Command Centre. Gallagher licenses by site. * Connectors, API tokens and the entity hierarchy value are all set per site * A site can cover one campus or a whole country, depending on the Command Centre's reach * Sites are largely invisible day to day, and appear only as a parent in the Config location dropdown ## Location A location is Kenai's operational unit: where visitors and employees sign in, and where day-to-day configuration lives. * Almost everything under **Config → Location** is set per location * Devices and integration events attach to a location * Two locations in one organisation can be configured completely differently --- # 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/sites-and-locations.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.