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

# Rippling

> How to install Pike from the Rippling App Shop to provision members, sync departments, managers, and leave, and send hourly time to payroll.

The Rippling integration provisions Pike members from Rippling, syncs departments, managers, and approved leave, and sends approved hours for hourly employees to Rippling payroll. New hires appear in Pike without a manual invite.

## Connect Rippling

Rippling connects from the Rippling side.

1. In Rippling, open the **App Shop** and find **Pike**.
2. Install the Pike app and follow the prompts to connect your Pike workspace.

Only workspace admins can connect or disconnect Rippling.

## Import data

On the integration page, click **Import data**. The stepper runs entities in dependency order, so Pike reads departments before the employees who belong to them. It skips entities whose **Read** toggle is off, names them, and links to sync settings.

## What syncs

| Rippling | Pike | Direction |
| - | - | - |
| Employees | Members, created, updated, and deactivated by Rippling | Rippling to Pike |
| Departments | Teams | Rippling to Pike |
| Groups | Teams | Rippling to Pike |
| Managers | Managers | Rippling to Pike |
| Approved leave | Time off | Rippling to Pike |
| Payroll hours | Regular and overtime hours from a closed Pike pay period | Pike to Rippling, when **Send hours to payroll** is on |

### Provisioning

Rippling creates, updates, and deactivates Pike members, and maps Rippling groups to Pike teams. A deactivated member keeps their history.

### Send hours to payroll

When **Send hours to payroll** is on, closing a [pay period](https://usepike.com/docs/members/payroll.md) in Pike posts each hourly employee's hours to Rippling payroll: normal hours as regular hours, and paid-out Overtime 1 and Overtime 2 as overtime and double overtime. The [working time policy](https://usepike.com/docs/members/working-time.md) decides the split. Only approved entries count.

### Time off

Approved leave from Rippling creates Pike time off of the mapped type. Defaults: vacation to Vacation, sick to Sick, parental to Parental, time off in lieu to Time off in lieu, unpaid to Unpaid leave, and other types to Vacation. That removes those hours from capacity, so allocations and utilization stay correct. A part-day absence removes only its hours, and 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. Pending or rejected requests do not sync.

### Compensation

**Sync compensation to cost profiles** is off by default. Only admins and finance users can turn it on. When on, salary and pay period from Rippling set the member's [cost profile](https://usepike.com/docs/members/cost-profile.md), with the effective date from Rippling.

### Source of truth

Once a record is linked, Rippling owns the linked fields and Pike reads them back. Pike-only fields, such as project links, internal notes, allocations, and cost profiles, stay in Pike and are never overwritten. Rippling owns person fields.

### Schedule

Pike syncs with Rippling every 24 hours by default. Change the schedule in the integration settings. **Import data** and **Refresh** always run on demand.

## Sync settings

While Rippling is connected, the **What syncs with Rippling** card sits under the top button row on the integration page. Each entity has a **Read** toggle (Rippling to Pike) and, where supported, a **Send** toggle (Pike to Rippling). Toggles save immediately.

| Entity | Read | Send |
| - | - | - |
| Employees | Yes | Not available |
| Leave | Yes | Not available |
| Hours to payroll | Not available | Yes, off by default |

New connections start with **Read** on for everything and **Send hours to payroll** off.

## Synced records

Every synced record shows the Rippling marker, "Last synced {time}" or "Not synced yet", and a **Refresh** action. **Refresh** shows only while **Read** is on for that entity.

### Sync issues

Records that fail to sync appear in the **Sync issues** list on the integration page, with the record, the reason, and a **Retry** action. The integration never deletes Pike data on its own. A record removed in Rippling is marked "Removed in Rippling" in Pike, never deleted.

## Disconnect

Disconnecting Rippling stops syncing and keeps all imported data. Linked records keep their history.

## Permissions

Synced data respects Pike roles and private projects. A private project's tasks never sync out to anyone who cannot see the project in Pike.

## Limits

* Salaried employees' hours are not sent. Rippling pays salaried employees from their salary.
* Time off in lieu balances stay in Pike. Rippling receives paid-out overtime only.
* Pike does not run payroll.
* Rippling connects from the Rippling App Shop, not from Pike.

## Related

* [Rippling integration overview](https://usepike.com/integrations/rippling): What syncs, how agencies use it, and FAQs.
* [Gusto](https://usepike.com/docs/integrations/gusto.md): Employees, time off, and hours to payroll.
* [SCIM provisioning](https://usepike.com/docs/integrations/scim.md): Provision members from your identity provider.
* [Pay periods and payroll](https://usepike.com/docs/members/payroll.md): Period close and pay lines.
* [Workspace capacity](https://usepike.com/docs/allocation/workspace-capacity.md): How time off and contracts set available hours.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.