.png)
Connect Rippling to HYPR so passwordless authentication is provisioned at hire and deprovisioned at offboarding — with Rippling employee data driving the identity verification layer that eliminates passwords across your entire app stack.
thePeopleStack configures the Rippling–HYPR integration with Rippling as the authoritative employee identity source, ensuring HYPR's user roster stays synchronized through hire, role change, and termination events. We map Rippling role and privilege data to HYPR authentication policy assignment so stronger authentication requirements apply automatically to privileged users without a separate IAM workflow.
For clients replacing password-based authentication across their app stack, we design the HYPR enrollment sequence as part of the Rippling new hire onboarding flow — so passwordless authentication is active for every new employee from day one, not added manually weeks into their tenure.
HYPR passwordless authentication is deployed by thePeopleStack's Rippling clients primarily for US workforce identity security programs, with authentication policies aligned to US security baselines and compliance frameworks including SOC 2, FedRAMP, and CMMC where applicable.
Canadian and cross-border operations: Canadian employees are enrolled in HYPR through the same Rippling lifecycle sync, with thePeopleStack confirming that cross-border biometric and authentication data handling aligns with PIPEDA requirements for Canadian workforce identity programs.
HYPR replaces passwords with biometric or device-bound authentication — using the employee's mobile device or hardware token to verify identity. When anchored to Rippling's employee roster, HYPR enrolls new hires automatically, updates authentication policy on role changes, and revokes authenticator bindings when an employee is terminated in Rippling.
Yes. HYPR's authentication policy framework supports tiered requirements. Rippling job title and department data can assign executives, finance staff, and IT administrators to stricter authentication policies — requiring device binding plus biometric verification — while general employees use a standard passwordless policy.
Employee termination in Rippling triggers HYPR authenticator revocation, removing the user from active authentication policies and invalidating their device-bound credentials. Unlike password-based systems where a password reset suffices, HYPR revocation must be executed through the platform — making automation through Rippling's offboarding workflow essential.
HYPR complements Rippling SSO by replacing the password-based authentication step within SSO with a passwordless equivalent. Rippling SSO still governs which applications employees can access; HYPR governs how they authenticate into those applications — eliminating the password as the weakest link in the SSO chain.
A standard configuration covering user enrollment, authentication policy assignment, and offboarding authenticator revocation typically takes 4–6 hours. Deployments replacing password authentication across a large application portfolio require additional policy design and phased rollout planning.
