> For the complete documentation index, see [llms.txt](https://www.cakewalk.security/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.cakewalk.security/docs/connections-and-integrations/connecting-an-hris.md).

# Connecting an HRIS

One flow covers every supported system: pick your HRIS or IdP, authenticate with an admin account and approve the requested scopes. This page walks the shared flow. The same steps apply when you select an IdP.

### ✅ Before You Start

* You need the Cakewalk Admin role.
* You need an admin account in your HRIS or IdP with rights to read user profiles, reporting lines and groups.

***

### 🛠 Connect

1. Go to **Settings → Data Sources → Users**.
2. Select your HRIS or IdP.
3. Authenticate with the admin account.
4. Review and approve the requested scopes.
5. Save. The first sync starts immediately.

***

### 📦 What Syncs

* User records: name, email, manager.
* Organizational attributes: department, job title, location.
* Lifecycle events: joiners, movers and leavers, which trigger workflows in real time.
* Manager relationships, which route approvals and reporting.

Cakewalk does not read payroll data, health data or details about sexual and religious orientation.

***

### ⏭ After the First Sync

* User data refreshes every 2 hours.
* New hires trigger onboarding and departures trigger offboarding. See [User Lifecycle](/docs/human-access-and-agent-access/user-lifecycle.md).
* Set default assignees for onboarding and offboarding tasks in the integration settings if your company routes them to specific people.

{% hint style="info" %}
Group sync is a separate connection under **Settings → Data Sources → User groups**, with the same authentication flow. Bidirectional group sync requires write permissions for group memberships in the IdP. For what Groups do once synced, see [Groups & RBAC in Human Access](https://www.cakewalk.security/docs/human-access/how-to-guides/users-and-groups/groups-and-role-based-access-control-rbac).
{% endhint %}

Provider-specific prerequisites (the admin role, the plan tier, where the credential lives in that vendor's console) are in the per-system pages: [Identity Source Guides](/docs/connections-and-integrations/identity-sources.md).

***

### 📚 Related

* [HRIS and IdP](/docs/connections-and-integrations/hris-and-idp.md)
* [User Lifecycle](/docs/human-access-and-agent-access/user-lifecycle.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.cakewalk.security/docs/connections-and-integrations/connecting-an-hris.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.