> ## 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. # Justworks > Sync Justworks employees and contractors into Pike members, departments into teams, and approved time off into capacity, with optional compensation sync. The Justworks integration syncs employees and contractors from Justworks into Pike [members](https://usepike.com/docs/members/overview.md), departments into teams, and approved time off into Pike [time off](https://usepike.com/docs/members/time-off.md). Your HR and payroll team keeps working in Justworks. Resource managers plan allocations on the hours people are actually available, and margin reports use the same people, teams and pay rates as payroll. ## At a glance | | | | - | - | | **Direction** | Justworks to Pike for members, departments, managers, approved time off and, when turned on, pay rates | | **Who sets it up** | Workspace admins, with a Justworks admin who authorizes the Pike app | | **Plan** | All plans | | **Sync** | Every 3 hours. On the Enterprise plan, changes sync in real time. | | **Source of truth** | Justworks for person fields, time off and pay rates. Pike for capacity, allocations, projects, time and cost profiles | ## Before you start You need: * The workspace admin role in Pike. * A Justworks admin with full access to the company's people, time off and pay information. The admin signs in during setup and approves access for Pike. Pike asks for read access to member details, employment details, departments and time off, and to pay details when you plan to use compensation sync. * Pike time off types for the Justworks time off policies you use. You map each policy during setup. See [Time off](https://usepike.com/docs/members/time-off.md). * A capacity per week for each member. It is set on the member's [cost profile](https://usepike.com/docs/members/cost-profile.md) in Pike. ## Connect Justworks **1. Open the integration** Go to **Workspace settings → Integrations → Justworks** and click **Add integration**. **2. Authorize Pike** Sign in to Justworks as a company admin and approve access for Pike. You return to Pike with the integration connected and the Justworks company name shown. **3. Map time off types** Under **Time off types**, choose a Pike time off type for each Justworks time off policy. Pike suggests a mapping from the policy names. **4. Choose what syncs** In the **What syncs with Justworks** 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 members, then time off. The integration page shows **Connected**, the Justworks company name, **Last synced** and **Next sync**. ## What syncs | Justworks | Pike | Direction | | - | - | - | | Members (employees) | Members | Justworks to Pike | | Members (contractors) | Contractor members | Justworks to Pike | | Departments | Teams | Justworks to Pike | | Job titles | Positions | Justworks to Pike | | Managers | Managers | Justworks to Pike, matched by email | | Approved time off | Time off | Justworks to Pike | | Pay rate and pay basis | Member cost profiles | Justworks to Pike, when **Sync compensation to cost profiles** is on | ### Members | Justworks 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 | | Member type | Employment type | Employees become salaried or hourly from their pay basis. Contractors become contractors | | Job title | Position | A position is created when no Pike position has the same name | | Department | Team | A team is created when no Pike team has the same name | | Manager | Manager | When the manager's email matches a Pike member | | Employment status | Member status | A terminated member becomes a deactivated member. History is kept | | Start date, termination date | Contract dates | | | Member ID | Justworks ID | Shown on the member as the Justworks marker | ### Time off | Justworks field | Pike field | Notes | | - | - | - | | Member | Member | | | Time off policy | Time off type | Through your type mapping | | Start and end date | Dates | | | Amount and unit | Hours per day | Hours or days. A part-day request removes only its hours from capacity | | Status | Not stored | Only approved requests import | Default type mapping: vacation and PTO to Vacation, sick to Sick, parental to Parental, unpaid to Unpaid leave, and every other policy 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. | Justworks field | Pike field | Notes | | - | - | - | | Pay rate | Cost profile salary | For contractors, the pay rate sets the contractor cost rate | | Pay basis | Cost profile pay period | Hourly or salaried | | Pay history | Cost profile start date | Each pay change adds a new row with its effective date | See [Cost profile](https://usepike.com/docs/members/cost-profile.md). ## Matching and duplicates On the first import, Pike matches before it creates: * A Justworks member matches a Pike member with the same work email. A match links the two, and Justworks 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 off always imports as new time off. Time off already entered in Pike for the same member and dates stays, and the Justworks request is listed in **Sync issues** as an overlap. A Justworks member with no matching Pike 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 | Justworks owns | Pike owns | | - | - | - | | Members | Name, work email, member type, position, team, manager, status, dates | Role, rates, capacity per week, working time, project access, allocations | | Time off | Dates, amount and type of requests from Justworks | Time off requested in Pike | | Cost profiles | Salary rows, when compensation sync is on | Cost profiles, when compensation sync is off | Edit Justworks-owned fields in Justworks. Pike shows them as read-only with the Justworks marker. ## Sync schedule Pike syncs Justworks 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 Justworks is connected, the **What syncs with Justworks** card is below the top button row on the integration page. Toggles save immediately. | Entity | Read | Send | | - | - | - | | Members | 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 members and time off, **Invite new employees** off, and compensation off. ## How it works ```mermaid theme={"system"} sequenceDiagram participant Person as Employee in Justworks participant Admin as Admin in Justworks participant Justworks participant Pike participant RM as Resource manager in Pike Person->>Justworks: Request PTO for Friday Admin->>Justworks: Approve the request Justworks->>Pike: Approved time off, on the next sync or in real time Pike->>Pike: Remove 8 hours from Friday capacity Pike-->>RM: Capacity and allocations show the absence RM->>Pike: Move Friday's allocation to another person ``` ## Use it in Pike ### Plan around approved leave Open **Members → Allocations** to see each person's capacity for the week. Approved Justworks time off 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 employee or contractor is added in Justworks, they appear in Pike with their team, position and manager 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 member is terminated in Justworks, the member is deactivated in Pike. Their logged time, allocations and history stay on every project, and they stop counting toward capacity from the termination date. ### Cost projects at real pay rates With **Sync compensation to cost profiles** on, each pay change in Justworks adds a cost profile row from its effective date. Project margin and contribution use the same rates as payroll, including contractor rates. ## Deletes and removed records An integration never deletes Pike data. A member removed from Justworks is marked **Removed in Justworks** on the member, stays in Pike with their history, and stops syncing. A time off request canceled in Justworks 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 member is missing in Pike | Check that **Read** is on for members and that the person has a work email in Justworks. Then click **Sync now**. | | A member shows under **Unmatched employees** | The work email in Justworks differs from the member's email in Pike. Click **Link to member**, or correct the email in Justworks. | | Approved time off is missing | Check that **Read** is on for time off and that the request is approved in Justworks. Then click **Refresh** on the member. | | Time off shows the wrong type | The Justworks policy maps to a different Pike type. Change it under **Time off types**. Existing time off updates on the next sync. | | **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 | Compensation sync is off, or Pike has no access to pay details. Turn on compensation sync, or reconnect and approve access to pay details. | | **Sync issues** lists an authentication error | The Justworks admin who authorized Pike lost access, or access was revoked in Justworks. Reconnect with a current Justworks admin. | ## Limits * Pike does not write to Justworks. * Pike does not send hours to Justworks payroll. Justworks pays from the hours and salaries entered in Justworks. * Capacity per week and work schedules are set in Pike, on the member's cost profile. * Pending, denied or canceled time off requests do not sync. * Compensation sync is off until an admin or finance user turns it on. ## Disconnect Go to **Workspace settings → Integrations → Justworks** and click **Disconnect**. Syncing stops and every member, team, position and time off entry stays in Pike with its history. Reconnecting the same Justworks company relinks the members. ## Related * [How sync works](https://usepike.com/docs/integrations/how-sync-works.md): The schedule, real-time sync and sync issues. * [Time off](https://usepike.com/docs/members/time-off.md): Time off types and how they count toward capacity. * [Cost profile](https://usepike.com/docs/members/cost-profile.md): How pay rates turn into hourly cost and margin. * [Gusto](https://usepike.com/docs/integrations/gusto.md): Employees, contractors and hours to payroll. * [Rippling](https://usepike.com/docs/integrations/rippling.md): Employees, leave and hours to payroll. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.