# People

**People** are the central object in Siit. They represent every individual your organization interacts with—employees, new hires, alumni, and external partners. Each person connects seamlessly to their apps, equipment, and requests, creating a unified view of the employee experience.

**Why it matters**

* Faster intake: pre‑fill forms and enrich requests with role, manager, department, and location.
* Smarter routing: assign to teams based on requester attributes (e.g., “Route Finance to Finance Ops”).
* Targeted approvals: automatically select a manager or app owner.
* Reporting: slice metrics by department, office, legal entity, or employment type.

**Groups and org structure- create & manage:** 

* Teams
* Departments
* Office locations
* Legal entities Use these groups to power audience rules in the Service Catalog, conditions in Workflows, and filters in Reporting.

**Fields and source of truth** 

* Define the People fields your organization uses (e.g., Department, Job title, Manager, Contract type, Cost center). For each field:
* Pick a priority source (e.g., HRIS or IdP). If multiple systems provide the field, the priority source wins.
* Control visibility (on/off) for privacy and least‑privilege access.
* Add your own custom fields when needed.

**People list and profiles**

* List: browse and filter your directory by group, lifecycle, location, or any field. Save common filters as views.
* Profile: open a person to see:
  * Overview (role, manager, groups)
  * Activity timeline (recent requests)
  * Active apps (and ownership)
  * Equipment assigned
  * Documents (optional) From a profile, you can start a new request, message the person, or jump to related objects.


---

# 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/data-management/people.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.