> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/ai.md). # AI - [AI trust model](https://docs.siit.io/ai/ai-trust-model.md): Siit's AI is governable by design. Control what each agent can read, propose, and execute with least-privilege permissions, explicit approvals, and a full audit trail on every request - [Triage Agent](https://docs.siit.io/ai/triage-agent.md): The Triage Agent handles request intake conversationally in Slack, Teams and the employee Portal. It deflects with a knowledge article when one exists, or creates a complete, structured request - [An article isn't suggested](https://docs.siit.io/ai/triage-agent/article-not-suggested.md): An employee asked a question and the AI didn't suggest the article you expected. Check the article, then your settings, then what happened in the conversation - [Assist](https://docs.siit.io/ai/assist.md): Assist is the assistant built into your Siit admin dashboard. Ask it a question about Siit and it answers from the documentation. Ask it to do the work and it builds the configuration for you - [IT Agent](https://docs.siit.io/ai/it-agent.md): The IT Agent resolves operational work autonomously. It runs your playbooks across tools like Okta and Jamf, collects approvals in Slack or Teams, and escalates to humans when needed --- # 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://docs.siit.io/ai.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.