Skip to main content
If your organization uses Rippling as an HR provider, you can designate it as an IDP/HRIS Integration. This allows Opal to sync employee lifecycle status, managers, and worker attributes from Rippling, on top of managing access to Rippling supergroups.

​
Requirements

Before you set up Rippling as your HR provider, you must:
  • Create a Rippling app in Opal, by following the instructions here. The API token scopes listed there cover the IDP/HRIS integration, so you do not need a new token.
  • Be on version 1.1246.0 or greater, if you self-host Opal. The Rippling app is available from 1.1239.0, but the IDP/HRIS integration is not.
Next, set up Rippling as your HR provider using the following instructions: To find these settings in Opal, go to Settings > Identities > Upstream IDP & HR Directories and select your existing Rippling connection.

​
Employee status

Unlike the Rippling app, which syncs active workers only, the IDP/HRIS integration reads workers in every employment status so that Opal can deprovision people who leave. When a worker is deprovisioned, Opal applies your deprovisioning settings. A rehired worker can hold both a TERMINATED record and an ACTIVE one. Opal takes the ACTIVE record, so a rehire comes back as Active.
Workers without a valid work email, and workers with a status not listed above, are left out of the sync. Opal treats people who are missing from an HR provider as having left, so check that every worker you want in Opal has a work email in Rippling.This also applies to a worker who moves back into INIT, HIRED, or ACCEPTED. If they were already in Opal, they are treated as having left rather than held in place.If no workers can be synced at all, Opal fails the sync instead of deprovisioning everyone. This protects you fully only when Rippling is your sole upstream directory. With more than one directory connected, anyone who exists only in Rippling is still treated as having left.

​
Attributes

Opal matches Rippling workers to Opal users by work email. The following attributes are ingested from Rippling and mapped to Opal’s system attributes by default. If you connect more than one IDP/HR provider, set which provider wins for each attribute under Settings > Identities > Attribute source priority. The following attributes can also be mapped to Opal user attributes or user tags from Settings > Identities > Upstream IDP & HR Directories. Opal does not suggest these keys as you type, so enter the key exactly as it appears below.
Last modified on October 29, 2026