> 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/people.md).

# People

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

**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**

Siit organizes people into four kinds of groups:

* Teams
* Departments
* Office locations
* Legal entities

Use these groups to power audience rules in the Service Catalog, conditions in Workflows, and filters in Reporting.

**Managing groups**

Groups are managed in **Settings → Context management → People groups**, one tab per group type (Team, Department, Office location, Legal entity): create, rename, recolor or delete a group, and add or remove its members.

When a group field is synced from your HRIS or identity provider, the priority source set in **People fields** wins: a department changed by hand in Siit is overwritten at the next sync, so change it in the source system instead (see below).

**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 — your HRIS, or an identity provider such as Google Workspace or Microsoft Entra ID. 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.

**Managing the primary email**

When a person has several email addresses synced from your integrations (an HRIS email change, or an IdP with an active and a suspended profile), Siit holds one as the primary. That's the address integration actions resolve against.

* Admins with user-management permission can change the primary email directly from a person's `...` actions menu, without contacting support.
* Integration lookups (JumpCloud, Okta, and others) resolve against the new primary right away.
* Each change is recorded as a timeline event on the person, naming the new address and the one it replaced.

> **Note** : This action is only available when a person has more than one known email address.


---

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