> 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/deployment-resources/external-launch-faq.md). # External launch FAQs Answers common questions about the external launch of the Gallagher Security Knowledge Hub. ### What's changing? We're moving our product documentation to a new Gallagher Knowledge Hub, to make it faster and easier to find what you need. The Knowledge Hub is already where you'll find content for AccessNow, Kenai, and Release Notes, with the rest of our product documentation following progressively. ### Do I need to do anything? No action needed. Content has moved to its new home and is organised by product, with clearer navigation and search. One change you'll notice: this content is now openly accessible, so there's no need to request access or log in to view it. ### Will I still be able to find everything I used before? Yes - all existing Product-related content will be moving across to the new hub. Navigation has been restructured around products and common tasks, so some pages may be in a different place than you're used to. With AI-enabled search now built into the site, you shouldn't need to rely on browsing to find your way around - just ask your question directly and it'll point you to the answer. And because this content is now open and publicly accessible, it's also discoverable through external AI tools and search engines, so you can find answers from whatever LLM you already use. ### What content should I expect to see here in the future? More content is being added progressively. Next up are the Command Centre and Configuration Client User Guides for v9.60, which will be published in **mid-November**. ### Will the old site (Security Hub) still be available? Yes, for now. Security Hub will remain live for Product content for a transition period, to give you time to update any saved links, bookmarks, or internal processes that point to it. **Product content will be removed from Security Hub between now and the end of the year.** Going forward the Knowledge Hub should be treated as the current source for all product documentation. Content requiring a login — including the Technology Partner Portal and Sales & Marketing collateral — will continue to be available on Security Hub as it is today and is not affected by this change yet. ### Who can I contact for support? Technical Support remains available for certified Channel Partners - [Technical Support](https://security.gallagher.com/en-NZ/Support/Technical-Support) ### How can I give feedback on the Knowledge Hub? The best feedback is simply using the site. As more of you search, browse, and ask questions, it helps us see where content is working well and where there are gaps - so we can keep improving things over time. There's no separate form to fill out; just use the Knowledge Hub as you normally would, and we'll take it from there. --- # 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/deployment-resources/external-launch-faq.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.