# HRIS
### Why connect your HRIS
Your HRIS is the source of truth for who works at your company. Connecting it to Siit means:
* **A directory that stays current.** New hires appear in Siit the day they're added in your HRIS. Leavers are flagged automatically. No more stale org charts or manual CSV imports.
* **Richer context on every request.** Role, manager, department, location, legal entity, employment type, and start/end dates are attached to each requester — so routing, approvals, and SLAs can rely on them.
* **Automated onboarding and offboarding.** Use **Start date** and **End date** triggers to launch full lifecycle workflows — create accounts, grant app access, ship equipment, and revoke everything at the right moment.
* **Lifecycle-aware automations.** Probation reviews, work anniversaries, and birthdays can trigger touch points without anyone opening a ticket.
* **Better reporting.** Slice metrics by department, office, legal entity, or employment type — because every request carries the HRIS attributes of its requester.
### What Siit syncs from your HRIS
By default, Siit imports the fields you'll need most in requests, workflows, and reporting:
* Identity: full name, work email, employee ID
* Role: job title, level, department, cost center
* Org structure: manager, team, location, legal entity
* Employment: employment type (employee/contractor), status (active, pre‑hire, terminated)
* Lifecycle dates: start date, end date, probation end, birthday
You can extend the sync with custom fields from your HRIS, and decide which system wins for each field when multiple sources provide it (see Objects and Data model).
> **Work email is the canonical identifier.** Siit matches people across your HRIS, IdP, and other tools using work email. Make sure it's populated and consistent before connecting.
### Supported HRIS
Siit integrates natively with the most common HRIS platforms. Each one has its own setup guide:
* [BambooHR](https://docs.siit.io/integrations/hris/bamboohr)
* [HiBob](https://docs.siit.io/integrations/hris/hibob)
* [Workday](https://docs.siit.io/integrations/hris/workday)
* [ADP](https://docs.siit.io/integrations/hris/adp)
* [Deel](https://docs.siit.io/integrations/hris/deel)
* [Rippling](https://docs.siit.io/integrations/hris/rippling)
* Personio
* Gusto
* Humaans
* SAP SuccessFactors
* Oracle HCM
* Remote
* Lucca
* Payfit
* Factorial
* Sage HR
* Namely
* Paychex
* Paylocity
* UKG Pro
* TriNet
* Justworks
* Kenjo
* Charlie HR
* Zoho People
* AlexisHR
Don't see yours? Reach out to your point of contact — we regularly add new HRIS connectors.
### How the sync works
Once connected, Siit pulls People data from your HRIS on a regular schedule and keeps Siit in sync:
* **Initial import** — all active employees are imported the first time you connect.
* **Continuous sync** — Siit refreshes the directory automatically (typically every few hours, depending on the HRIS).
* **Source of truth rules** — for each People field, pick which system wins if multiple are connected (e.g., HRIS for department, IdP for job title). Configure this in **Settings → People → Fields**.
* **Lifecycle events** — start and end dates flow into Siit and can be used as workflow triggers, even before the employee has a user account anywhere else.
### HRIS + IdP: the best combination
Many customers connect **both** an HRIS and an IdP (Okta, Entra ID, Google Workspace, JumpCloud). Here's how they complement each other:
| | HRIS | IdP |
| ---------------- | ----------------------------------------------- | ----------------------------------------- |
| Source for | Employment data, org structure, lifecycle dates | Accounts, app access, authentication |
| Triggers in Siit | Start / end dates, probation, anniversaries | User created, group membership changes |
| Typical actions | Pre‑boarding sequences before accounts exist | Provisioning, SSO, group / app assignment |
Connecting both lets you start a full **Day‑1 onboarding workflow** the moment a new hire is added to the HRIS — days before they ever log in — and cleanly offboard them when their end date arrives.
### Common use cases
* **Day‑1 onboarding** — Trigger: Start date. Actions: create accounts in IdP, assign baseline apps, ship equipment, DM the hiring manager with a readiness checklist.
* **Offboarding on end date** — Trigger: End date. Actions: revoke sessions, remove app access, open an equipment pickup request, notify the manager.
* **Manager approvals** — Use the HRIS‑synced manager field to auto‑select the approver on any access or expense request.
* **Audience targeting** — Publish services only to specific departments, locations, or legal entities straight from HRIS attributes.
* **Probation reviews** — Trigger: Probation period. Action: send a review checklist to the manager.
### Getting started
1. Go to **Settings → Integrations** and pick your HRIS in the library.
2. Authorize the connection (each HRIS has its own flow — see the per‑platform guides).
3. Review the imported People and adjust field mapping in **Settings → People → Fields**.
4. Set the source of truth per field if you're also connected to an IdP.
5. Build your first lifecycle workflow in **Workflows → New → People trigger**.
---
# 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/integrations/hris.md?ask=
```
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.
