> For the complete documentation index, see [llms.txt](https://talentbox.talenteam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://talentbox.talenteam.com/readme.md). # Welcome Welcome to the **TalentBox Documentation Hub** – your central space to learn how to get the most from TalentBox. This site brings together product overviews, configuration guides, integration details, and best‑practice examples to help you design and manage your talent processes more efficiently. Whether you are configuring TalentBox for the first time, setting up integrations, or looking for ways to optimise existing workflows, you’ll find step‑by‑step guidance, screenshots, and explanations organised by topic and area of the platform. Use these resources to support onboarding, answer how‑to questions, and build a consistent understanding of how TalentBox works across your team. The site also includes a powerful **global search** that scans all available TalentBox documentation. Just start typing a feature name, process, or question, and the search will surface the most relevant pages so you can jump straight to what you need, without clicking through multiple menus. This makes it easy to troubleshoot issues, explore new capabilities, or quickly revisit something you’ve read before. As TalentBox evolves, this hub will grow with it, so you can always rely on it as the up‑to‑date source of truth for how TalentBox is designed, configured, and used in practice. --- # 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://talentbox.talenteam.com/readme.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.