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

# Sage HR

Connect Sage HR to Siit to sync your employee directory and lifecycle events. Sage HR is a common choice for SMBs across the UK, Ireland, and Europe.

<figure><img src="https://451675063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz9xmM8V3atukfr2XaElR%2Fuploads%2FqPXRKH1ccUrJuQ5jShYi%2FSiit_Sage%20HR.jpg?alt=media&amp;token=eaeacc92-98a2-444a-87f3-9f3affe1e1ac" alt=""><figcaption></figcaption></figure>

### What you get

* **Live People directory** — Sage HR employees appear in Siit with role, manager, department, and lifecycle dates.
* **Lifecycle triggers** — Start date, End date, Work anniversary, and Birthday flow into Siit as workflow triggers.
* **Manager resolution** — Sage HR's reporting structure powers auto‑selected approvers in workflows.
* **Pre‑hires** — future employees with a start date in Sage HR appear in Siit ahead of Day 1.

### What syncs from Sage HR

| Category        | Fields                                         |
| --------------- | ---------------------------------------------- |
| Identity        | First name, last name, work email, employee ID |
| Role            | Job title, department                          |
| Org structure   | Manager, work location                         |
| Employment      | Status                                         |
| Lifecycle dates | Start date, end date, date of birth            |

Work email is the canonical identifier across systems.

### Before you connect

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

### Connect Sage HR

1. In Sage HR, generate an API key for Siit with read access to the employee directory.
2. In Siit, go to **Settings → Workspace → Integration library**, find **Sage HR** in the HRIS section, and click **Connect**.
3. Paste the API key, then click **Authorize**.
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 Sage HR's active workforce.
* In **Settings → Context management → People fields**, set Sage HR 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 Start date trigger.

### Sync frequency

Sage HR data refreshes automatically every few hours.

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

### Troubleshooting

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

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

**"Invalid credentials" on connect.** The API key was revoked. Generate a new one and update Siit.


---

# 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/sage-hr.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.