# Objects and Data model

{% 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 device” form fields so employees provide precise context.

Workflows

* Conditions can check requester attributes (e.g., Department = Sales), app ownership (App owner = Security), or device state (Lifecycle = Outdated).
* 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 each field.
* 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: 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 current page URL with the `ask` query parameter:

```
GET https://docs.siit.io/core-plateform/interactive-blocks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.