> 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/core-platform/interactive-blocks.md).

# Objects and Data model

Siit unifies three core objects: People, Applications, and Equipment. Connect your IdP, HRIS, and MDM so every request carries the context that powers routing, approvals, and reporting

{% stepper %}
{% step %}

### Overview

Siit’s data model unifies three core objects—People, Applications, and Equipment—so every request carries the right context. This foundation powers routing, approvals, automation, audience targeting, and reporting. Connect your sources of truth (IdP/HRIS/MDM), choose which fields matter, and work from a single, consistent view.
{% endstep %}

{% step %}

### How these objects power requests and automation ⚙️

Requests

* See requester info, recent requests, assigned apps and devices, and SLA—all in one place. Make decisions without switching tabs.

Service Catalog

* Use People groups (department, location, legal entity) to define who can see and submit each service.
* Add “Select application” or “Select an equipment” form fields so employees provide precise context.

Workflows

* Conditions can check requester attributes (e.g., Department = Sales), app ownership (App owner = Security), or equipment type (e.g., Computer).
* Actions can provision/deprovision access, add to groups, or open tickets in Jira/Linear based on app or requester data.
  {% endstep %}

{% step %}

### Governance and privacy 🔒

* Field‑level visibility: hide sensitive fields (e.g., compensation) from most roles.
* Source priority: select which integration is the source of truth for supported People fields.
* Roles & permissions: restrict who can view/edit People, Applications, and Equipment data.
  {% endstep %}

{% step %}

### Explore all the objects

{% endstep %}
{% endstepper %}

{% content-ref url="/pages/I75RKm06EMgODC6TINY1" %}
[People](/data-management/people.md)
{% endcontent-ref %}

{% content-ref url="/pages/rtBtYTtyUvxFnJ65oZti" %}
[Apps](/data-management/apps.md)
{% endcontent-ref %}

{% content-ref url="/pages/mYLLm4OLAWjamKfQd2EJ" %}
[Equipment](/data-management/equipment.md)
{% endcontent-ref %}

{% content-ref url="/pages/ahKUJCL4Cv8aGzqfjd6h" %}
[Articles](/data-management/articles.md)
{% endcontent-ref %}


---

# 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/core-platform/interactive-blocks.md?ask=<question>&goal=<user_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.