Connect Rippling
Letting staff sign in with Rippling, and what connecting it does and doesn't change.
What connecting does
With Rippling connected, your staff see Sign in with Rippling instead of leading with a password field. They authenticate against Rippling, and RoundUp accepts the result.
It does not create staff accounts. Someone who authenticates through Rippling but has no staff account at your center is refused and told to ask their director — accounts come from an invitation, never from a sign-in.
Setting it up
Connect Rippling from your center's integration settings. Staff email addresses must match between the two systems, because email is what RoundUp matches on. A teacher with a work address in Rippling and a personal one in RoundUp will authenticate successfully and then be refused, which is a confusing failure to debug from the outside.
If you also use Okta or Auth0
A center's own identity provider takes precedence over Rippling. The reasoning: Rippling may be connected for payroll alone, which says nothing about how staff are meant to sign in, whereas connecting Okta or Auth0 is a deliberate decision about authentication.
So a center with both shows the Okta button. See Connect Okta and Connect Auth0.
Offboarding
Deactivating someone in Rippling stops them signing in that way. Deactivate them in RoundUp too unless you've confirmed provisioning is handling it — an active RoundUp account with a password set is still an account, whatever your HR system says.
See What happens when someone leaves.
Troubleshooting
The Rippling button doesn't appear
Either the connection isn't complete, or your center has Okta or Auth0 connected and that takes precedence. An unconfigured provider degrades to the password screen rather than showing a button that dead-ends.
"No account is linked to your email"
They authenticated fine but have no staff account at your center under that address. Check the email on their staff record first — it's nearly always the email.
More: All director guides