Skip to main content
Oleria provides identity security and access management teams with visibility and intelligence into who has access to what, where they got that access, how they use it, and whether they should even have it. As part of that promise, we integrate your Rippling HRIS into the Oleria platform as the authoritative source for employees, departments, and reporting structure. Follow these steps to connect Rippling to your Oleria workspace using an API token.

​
Prerequisites

  • Rippling administrator account with permission to create API tokens under Developer settings
  • Admin access to the Oleria workspace
Use a service account (and not an individual employee’s account) to create the API token. Rippling revokes the token if its owner is terminated, so a personal account puts the integration at risk of breaking unexpectedly.

​
Create an API token in Rippling

1

Open API Tokens

Log in to Rippling as an administrator, then select Tools -> Developer -> API Tokens.
2

Create a new token

Select Create API token.
3

Set the API version and scopes

Select API version 2024-08-01 and assign the following read scopes:
To let Oleria add or remove workers from Rippling groups as a remediation action, also assign the supergroups.read-write scope. Without it, the integration is read-only.
4

Copy the token value

Save the token. Rippling displays the token value only once, so copy it now.

​
Connect Rippling to Oleria

1

Open the integration

Go to your Oleria workspace, select Integrations -> select Rippling.
2

Complete the connection form

Select Continue and provide the following:
3

Confirm the connection

Select Authenticate to validate the token. Find the newly connected Rippling instance in your Oleria workspace connected integrations.
If the token is revoked, generate a new API token in Rippling and update it from the Rippling integration’s edit mode in your Oleria workspace.

​
What Oleria imports from Rippling

Oleria uses Rippling as the authoritative source for your workforce identity data:
  • Employees, people, and accounts, including manager relationships
  • Departments and department hierarchy
  • Rippling groups and group membership
  • Third-party applications Rippling has provisioned for each worker, and which workers are assigned to them
  • Worker change activity (hires, changes, and offboards), where your tenant has the separately licensed Worker Changes API entitlement
A later change to the token creator’s Rippling permission profile can silently narrow what the connector can read. Rippling omits fields the token can no longer see rather than returning an error, so if data starts disappearing from Oleria, check the token owner’s permissions first.
Activity data (worker change events) requires Rippling’s separately licensed Worker Changes API. If your tenant doesn’t have that entitlement, Oleria still connects successfully, but activity data stays empty.

​
Verify the integration

Once connected, Oleria performs an initial sync of employees, departments, groups, and third-party application access from Rippling. Subsequent syncs run on Oleria’s standard sync cadence and pick up changes to workers, departments, group membership, application access, and worker change activity.

​
Contact us

For questions about this integration, contact us at support@oleria.com.