Connect Rippling so Coworker knows your employee roster and reporting lines. Rippling is an admin-connected, identity-only source — it anchors the roster spine of Coworker's knowledge graph.
Rippling Data in Coworker
Indexed into the knowledge graph
People directory, kept current via incremental syncs plus a daily full reconciliation — builds a verified Person entity for each employee
Job-role history
Merges each employee's identity with the same employee across every other connected source
Builds your org chart from reporting lines
Stamps a standard set of HR properties onto each Person node
Never collected
Compensation and salary data, bank details, other sensitive data are excluded at the API-scope and code level for every HRIS connector — they never reach the warehouse, the graph, or a prompt.
Before you start
You must be a Coworker Network Admin
You need a Rippling API token created by a Rippling admin with access to the complete people roster
To create an API key in Rippling, your company must have a subscription that includes specific add-on components rather than a single pre-defined plan tier. Specifically, you need the following enabled on your account:
The Rippling API Key Package: Direct REST API access and token generation are gated behind this dedicated Rippling API Key Package add-on. If it is not active, an account representative must enable it for you.
The Identity & Access Management (IAM) Package: If you are creating API keys to connect to third-party integrations, Rippling requires your core plan to include the Identity & Access Management module alongside your base subscription.
Once these packages are provisioned, any administrator with the correct permissions can generate keys by navigating to Company Settings → API access (or Tools → Developer → API Tokens) within the admin dashboard.
Connect as an admin
Select Directory & Identity > HRIS / IAM system from the admin setup in Coworker Onboarding and select Rippling.
Click Connect to Rippling then Allow and Continue
Follow the on-screen steps to create API key with the following scopes via assign with csv:
workers.read,levels.read,users.read,legal-entities.read,employment-types.read,teams.read,custom-fields.read,departments.read,work-locations.read,workers.custom-fields.read,companies.read,leave-balances.read,leave-requests.read,leave-types.read,time-entries.readPaste the API token.
Save.
Connect as a member
Rippling has no per-user connection path.
Good to know
A token with incomplete scopes can authenticate successfully but yield an incomplete org chart — use an admin-created token per the scope requirements above.