> 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/getting-started.md). # Getting Started - [Quickstart](https://docs.siit.io/getting-started/quickstart.md): Create and resolve your first access request from Slack or Teams in minutes, then turn it into an automated workflow so the next one resolves itself - [Connect Slack](https://docs.siit.io/getting-started/connect-slack.md): Connect Slack so employees submit requests in chat and admins work from threads and the Siit inbox. Covers prerequisites, the permission scopes Slack requests, and Enterprise Grid - [Connect Microsoft Teams](https://docs.siit.io/getting-started/connect-microsoft-teams.md): Connect Microsoft Teams so employees submit and follow requests without leaving chat. Connect from the integration library, install the Siit app from the Microsoft marketplace, then verify it works - [Set Live](https://docs.siit.io/getting-started/set-live.md): Move from sandbox to production: pick a pilot scope, define your services, configure channels, then open Siit to employees so requests arrive and automation starts resolving them --- # 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/getting-started.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.