> 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/integrations/hris/zoho-people.md).
# Zoho People
Connect Zoho People to Siit to sync your employee directory and lifecycle events. Zoho People is a flexible HRIS used globally, especially in mid‑market and growing companies.
### What you get
* **Live People directory** — Zoho People employees appear in Siit with role, manager, department, and lifecycle dates.
* **Lifecycle triggers** — Date of joining, Date of exit, Work anniversary, and Birthday flow into Siit as workflow triggers.
* **Manager resolution** — Zoho People's reporting structure powers auto‑selected approvers in workflows.
* **Pre‑hires** — future employees with a date of joining in Zoho People appear in Siit ahead of Day 1.
### What syncs from Zoho People
| Category | Fields |
| --------------- | ---------------------------------------------- |
| Identity | First name, last name, work email, employee ID |
| Role | Designation (job title), department |
| Org structure | Reporting manager, location, legal entity |
| Employment | Employment type, status |
| Lifecycle dates | Date of joining, date of exit, date of birth |
Work email is the canonical identifier across systems.
### Before you connect
* A Zoho People admin with permission to authorize third‑party apps.
* Work email populated for every active employee in Zoho People.
* Note your Zoho data center region (zoho.com, zoho.eu, zoho.in, etc.) — Siit needs the right region during connect.
### Connect Zoho People
1. In Siit, go to **Settings → Workspace → Integration library**, find **Zoho People** in the HRIS section, and click **Connect**.
2. Pick your Zoho data center region.
3. Sign in with your Zoho admin account and approve the requested read scopes.
4. Review the imported people and field mapping, then click **Finish setup**.
Need a more detailed walkthrough? Reach out to support via the in‑app chat.
### After the connection
* Confirm your **People list** matches Zoho People's active workforce.
* In **Settings → Context management → People fields**, set Zoho People as the source of truth for HR‑owned fields if you're also connected to an IdP.
* Build a Day‑1 onboarding workflow using the Date of joining trigger.
### Sync frequency
Zoho People data refreshes automatically every few hours.
### Common workflows
**Day‑1 onboarding.** *Trigger: Date of joining. Actions: create IdP account, assign apps by department, ship equipment, DM reporting manager.*
**Offboarding on exit.** *Trigger: Date of exit. Actions: revoke sessions, remove app access, equipment pickup, notify reporting manager.*
### Troubleshooting
**Employees missing.** Only active employees and future hires sync by default. Confirm status and work email in Zoho People.
**Wrong data center region.** Disconnect and reconnect with the correct region for your Zoho tenant.
**Manager field empty.** In Zoho People, check the employee has a reporting manager assigned.
**Connection shows "needs reauthorization".** Reconnect from **Settings → Workspace → Integration library → Zoho People**.
---
# 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/integrations/hris/zoho-people.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.
