# Humaans

<figure><img src="/files/gEPySp15KTVOmwtcbFVk" alt=""><figcaption></figcaption></figure>

### What you get

* **Live People directory** — Humaans employees appear in Siit with role, manager, department, location, and lifecycle dates.
* **Lifecycle triggers** — Start date, End date, Probation end, Work anniversary, and Birthday flow into Siit as workflow triggers.
* **Manager resolution** — Humaans' reporting structure powers auto‑selected approvers.
* **Custom fields** — extend the sync with any custom Humaans field (cost center, contract type, etc.).
* **Pre‑hires** — future employees with a start date in Humaans appear in Siit ahead of Day 1.

### What syncs from Humaans

| Category        | Fields                                                         |
| --------------- | -------------------------------------------------------------- |
| Identity        | First name, last name, preferred name, work email, employee ID |
| Role            | Job title, department, team                                    |
| Org structure   | Manager, location, legal entity                                |
| Employment      | Employment type, status                                        |
| Lifecycle dates | Start date, end date, probation end, date of birth             |
| Custom          | Any custom field you select during mapping                     |

Work email is the canonical identifier across systems.

### Before you connect

* A Humaans admin to generate an API key.
* Work email populated for every active employee in Humaans.

### Connect Humaans

1. In Humaans, go to **Settings → API access** and click **Create new key**. Name it "Siit integration", grant the required read access, and copy the key — it's shown only once.
2. In Siit, go to **Settings → Integrations**, find **Humaans** in the HRIS section, and click **Connect**.
3. Paste the API key and click **Authorize**.
4. Review the imported people and field mapping (including custom fields), then click **Finish setup**.

Need a more detailed walkthrough? Reach out to support via the in‑app chat.

> **Tip** — Humaans API keys inherit the permissions of the admin who created them. Use a dedicated service admin account so the integration survives admin turnover.

### After the connection

* Confirm your **People list** matches your active + upcoming Humaans employees.
* In **Settings → People → Fields**, set Humaans as the source of truth for HR‑owned fields if you're also connected to an IdP.
* In **Settings → Integrations → Humaans**, add any custom Humaans field you want available in Siit.
* Build a Day‑1 onboarding workflow using the Start date trigger.

### Sync frequency

Humaans data refreshes automatically every few hours. Trigger an immediate refresh from **Settings → Integrations → Humaans → Sync now**.

### Common workflows

**Day‑1 onboarding.** *Trigger: Start date. Actions: create IdP account, assign apps by department, ship equipment, DM manager.*

**Offboarding on end date.** *Trigger: End date. Actions: revoke sessions, remove app access, equipment pickup, notify manager.*

**Probation review.** *Trigger: Probation end. Action: send review checklist to manager.*

### Troubleshooting

**Employees missing.** Only active employees and future hires sync by default. Confirm status and work email in Humaans.

**Manager field empty.** In Humaans, check the employee has a manager assigned on their profile.

**Custom field didn't appear.** Make sure the API key has access to the field, then re‑run mapping in Siit.

**"Invalid credentials" on connect.** The API key was revoked or the admin who created it has been deactivated. Generate a new key in Humaans and update Siit.


---

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