> ## Documentation Index > Fetch the complete documentation index at: https://usepike.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Humaans > Sync Humaans people, job roles, departments, working patterns and approved time away into Pike members, teams, capacity and time off. The Humaans integration syncs people from Humaans into Pike [members](https://usepike.com/docs/members/overview.md), departments into teams, working patterns into work schedules, and approved time away into Pike [time off](https://usepike.com/docs/members/time-off.md). HR keeps working in Humaans. Resource managers plan allocations on the hours people actually work, and utilization reports show people in the same teams as HR. ## At a glance | | | | - | - | | **Direction** | Humaans to Pike for people, job roles, departments, working patterns, approved time away and, when turned on, compensation | | **Who sets it up** | Workspace admins, with a Humaans API access token | | **Plan** | All plans | | **Sync** | Every 3 hours. On the Enterprise plan, changes sync in real time. | | **Source of truth** | Humaans for person fields, working patterns, time away and compensation. Pike for allocations, projects, time and cost profiles | ## Before you start You need: * The workspace admin role in Pike. * A Humaans admin who can see every person you want in Pike, including their job roles, time away and working patterns. An API access token never has more access than the person who creates it. * An API access token. In Humaans, an admin opens the API access token settings, creates a token named Pike with read access to public and private data, and adds read access to compensations if you plan to use compensation sync. Choose no expiry, or note the expiry date so you can replace the token in time. Humaans shows the token only once. * Pike time off types for the Humaans time away types you use. You map each type during setup. See [Time off](https://usepike.com/docs/members/time-off.md). ## Connect Humaans **1. Open the integration** Go to **Workspace settings → Integrations → Humaans** and click **Add integration**. **2. Enter your token** Paste the API access token and click **Connect**. Pike checks the token and shows the Humaans company name. **3. Map time off types** Under **Time off types**, choose a Pike time off type for each Humaans time away type. Pike suggests a mapping from the type names. **4. Choose what syncs** In the **What syncs with Humaans** card, turn **Read** on or off for each entity, and choose whether to turn on **Invite new employees**. **5. Import** Click **Import data**. Departments import first, then people and their job roles, then working patterns and time away. The integration page shows **Connected**, the Humaans company name, **Last synced** and **Next sync**. ## What syncs | Humaans | Pike | Direction | | - | - | - | | People | Members | Humaans to Pike | | Departments | Teams | Humaans to Pike | | Job roles | Positions and managers | Humaans to Pike | | Working patterns | Work schedules | Humaans to Pike | | Approved time away | Time off | Humaans to Pike | | Compensations | Member cost profiles | Humaans to Pike, when **Sync compensation to cost profiles** is on | ### People | Humaans field | Pike field | Notes | | - | - | - | | First name, last name | Member name | The preferred name is used when one is set | | Work email | Member email | Also used to match existing members | | Job title on the current job role | Position | A position is created when no Pike position has the same name | | Department on the current job role | Team | A team is created when no Pike team has the same name | | Reports to on the current job role | Manager | When the manager's email matches a Pike member | | Employment start and end date | Contract dates and member status | A person past their end date becomes a deactivated member. History is kept | | Person ID | Humaans ID | Shown on the member as the Humaans marker | A job role with a future effective date applies in Pike from that date. ### Working patterns | Humaans field | Pike field | Notes | | - | - | - | | Working days and hours | Work schedule | Hours per weekday. Days off in a part-time pattern stay off | | Total weekly hours | Capacity per week | The sum of the schedule | | Effective date | Contract start | A new working pattern starts a new contract from that date | See [Work schedule](https://usepike.com/docs/members/working-time.md#work-schedule). ### Time off | Humaans field | Pike field | Notes | | - | - | - | | Person | Member | | | Time away type | Time off type | Through your type mapping | | Start and end date | Dates | | | Half day at start or end | Hours per day | A half day removes half the member's scheduled hours from capacity | | Request status | Not stored | Only approved time away imports | Default type mapping: vacation or annual leave to Vacation, sick to Sick, parental leave to Parental, time off in lieu to Time off in lieu, unpaid leave to Unpaid leave, and every other type to Vacation. Each type counts toward the member's [norm hours](https://usepike.com/docs/members/working-time.md#norm-hours) as set on the Pike type. ### Compensation **Sync compensation to cost profiles** is off by default. Only admins and finance users can turn it on. Pike reads base salary compensations only. Bonuses, commission and equity stay in Humaans. | Humaans field | Pike field | Notes | | - | - | - | | Amount, currency | Cost profile salary | | | Period | Cost profile pay period | Hour, month or year | | Effective date | Cost profile start date | Each compensation change adds a new row | See [Cost profile](https://usepike.com/docs/members/cost-profile.md). ## Matching and duplicates On the first import, Pike matches before it creates: * A person matches a Pike member with the same work email. A match links the two, and Humaans values replace the Pike values for the fields in the mapping. * A department matches a Pike team with the same name. A job title matches a Pike position with the same name. * Time away always imports as new time off. Time off already entered in Pike for the same member and dates stays, and the Humaans entry is listed in **Sync issues** as an overlap. A person with no matching member appears under **Unmatched employees** on the integration page. Click **Invite** to send a Pike invite, or **Link to member** to link the person to a member with a different email. With **Invite new employees** on, Pike sends the invite automatically with the default role the admin chose. ## Which system wins | Entity | Humaans owns | Pike owns | | - | - | - | | Members | Name, work email, position, team, manager, dates, work schedule | Role, rates, working time policy, project access, allocations | | Time off | Dates, half days and type of time away from Humaans | Time off requested in Pike | | Cost profiles | Salary rows, when compensation sync is on | Cost profiles, when compensation sync is off | Edit Humaans-owned fields in Humaans. Pike shows them as read-only with the Humaans marker. ## Sync schedule Pike syncs Humaans every 3 hours. On the Enterprise plan, changes sync in real time. **Import data**, **Sync now** and **Refresh** on a member run straight away on every plan. See [How sync works](https://usepike.com/docs/integrations/how-sync-works.md). ## Sync settings While Humaans is connected, the **What syncs with Humaans** card is below the top button row on the integration page. Toggles save immediately. | Entity | Read | Send | | - | - | - | | People | Yes | Not available | | Working patterns | Yes | Not available | | Time off | Yes | Not available | | Compensation | Off by default, admins and finance users only | Not available | New connections start with **Read** on for people, working patterns and time off, **Invite new employees** off, and compensation off. ## How it works ```mermaid theme={"system"} sequenceDiagram participant HR as HR in Humaans participant Humaans participant Pike participant RM as Resource manager in Pike HR->>Humaans: Set a four-day working pattern from 1 November Humaans->>Pike: Working pattern, on the next sync or in real time Pike->>Pike: New work schedule, 30 hours a week from 1 November HR->>Humaans: Approve time away for a Friday Humaans->>Pike: Approved time away Pike-->>RM: Capacity shows the new hours and the absence RM->>Pike: Rebalance allocations for the week ``` ## Use it in Pike ### Plan around approved leave Open **Members → Allocations** to see each person's capacity for the week. Approved Humaans time away shows on the day with its type, and the hours are already removed from capacity, so an over-allocated day stands out before the work is due. See [Workspace capacity](https://usepike.com/docs/allocation/workspace-capacity.md). ### Onboard a new hire When a new person is added in Humaans, they appear in Pike with their team, position, manager and working pattern on the next sync. Turn on **Invite new employees**, or click **Invite** under **Unmatched employees**, and the person can log time on their first day. ### Offboard a leaver When a person's employment end date passes in Humaans, the member is deactivated in Pike. Their logged time, allocations and history stay on every project, and they stop counting toward capacity from the end date. ### Measure utilization on contracted hours A part-time working pattern in Humaans sets the member's work schedule in Pike, so utilization for a four-day week is measured against four days, not five. ## Deletes and removed records An integration never deletes Pike data. A person deleted in Humaans is marked **Removed in Humaans** on the member, stays in Pike with their history, and stops syncing. Time away deleted or canceled in Humaans after approval is removed from Pike capacity on the next sync, and the change appears in the member's time off history. ## Troubleshooting | Symptom | Fix | | - | - | | A person is missing in Pike | The token's creator cannot see that person in Humaans. Create a token with an admin who has full access, then click **Sync now**. | | A person shows under **Unmatched employees** | The work email in Humaans differs from the member's email in Pike. Click **Link to member**, or correct the email in Humaans. | | Approved time away is missing | Check that **Read** is on for time off and that the request is approved in Humaans. Then click **Refresh** on the member. | | Time off shows the wrong type | The Humaans type maps to a different Pike type. Change it under **Time off types**. Existing time off updates on the next sync. | | Capacity does not match the working pattern | Check that **Read** is on for working patterns and that the pattern's effective date has passed. Then click **Refresh** on the member. | | **Sync issues** lists an overlap | Time off for the same dates already exists in Pike. Delete the Pike entry, then click **Retry**. | | Cost profiles do not update | The token has no read access to compensations. Create a token that includes it and enter it under **Credentials**. | | **Sync issues** lists an authentication error | The token expired or was revoked. Create a new token in Humaans and enter it under **Credentials**. | ## Limits * Pike does not write to Humaans. * Pending, declined or canceled time away does not sync. * Compensation sync is off until an admin or finance user turns it on, and reads base salary only. * The token syncs only the people and fields its creator can see. ## Disconnect Go to **Workspace settings → Integrations → Humaans** and click **Disconnect**. Syncing stops and every member, team, position, work schedule and time off entry stays in Pike with its history. Reconnecting the same Humaans company relinks the members. Revoke the token in Humaans if you no longer need it. ## Related * [How sync works](https://usepike.com/docs/integrations/how-sync-works.md): The schedule, real-time sync and sync issues. * [Working time](https://usepike.com/docs/members/working-time.md): Work schedules, norm hours and capacity per week. * [Workspace capacity](https://usepike.com/docs/allocation/workspace-capacity.md): How time off and contracts set available hours. * [Personio](https://usepike.com/docs/integrations/personio.md): Employees, absences and work schedules. * [HiBob](https://usepike.com/docs/integrations/hibob.md): Employees, departments and time off policies. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.