> For the complete documentation index, see [llms.txt](https://docs.itconductor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itconductor.com/readme.md). # Welcome Welcome to the IT-Conductor Knowledge Base, an extensive resource for those who use the IT-Conductor platform to monitor, manage, and orchestrate enterprise IT through intelligent automation. Browse our library to find instructions and best practices to Automate, Monitor, Manage, and Orchestrate systems using IT-Conductor. We regularly update our knowledge base to ensure you have access to the latest features and their respective documentation. You will also find documentation for different [cloud migration scenarios](/user-guide/automation/migration.md) that may be useful if you are considering moving your environment to the cloud. ### Contact Us If you can't find what you're looking for, our Support Team is always available to answer your questions and provide additional guidance. * [General Inquiries](https://www.itconductor.com/contact-us) * [Submit a Support Ticket](/references/support.md) ### Additional Information * [Frequently Asked Questions](https://www.itconductor.com/it-conductor-faq) * [Visit Our Blog](https://www.itconductor.com/blog) * [Upcoming Events](https://www.itconductor.com/events) * [Past Events](https://www.itconductor.com/past-events) * [Other Resources](https://www.itconductor.com/resources) --- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.itconductor.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 `build a script that syncs our docs to a CMS` 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.