> 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/data-management.md). # Data management - [People](https://docs.siit.io/data-management/people.md): People are the central object in Siit. Each one connects to their apps, equipment, and requests, so you can pre-fill forms, route by attribute, and target approvals automatically - [Apps](https://docs.siit.io/data-management/apps.md): Your app inventory: every tool employees use, with ownership, lifecycle, cost, and security attributes. Route requests by app, pick approvers automatically, and trigger provisioning in your IdP - [App access policies](https://docs.siit.io/data-management/app-access-policies.md): Govern app access end to end: who can ask, what they must provide, who signs off, and how access lands in the target system. Available on the Pro plan - [Equipment](https://docs.siit.io/data-management/equipment.md): Your device inventory: laptops, phones, peripherals, and anything else you assign. Link a device to a request to see model, serial number, and owner, and track its full lifecycle - [Articles](https://docs.siit.io/data-management/articles.md): Articles are your internal knowledge base. Write them in Siit or sync from Notion, Confluence, or Slab, then use them in the Portal, request replies, workflows, and AI answers --- # 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/data-management.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.