Rippling SSO App Not Provisioning
Quick answer
When a Rippling-managed app does not create a user, the cause is usually an unassigned app, a missing policy or a broken connection. Reconnect the integration and check the user's group membership.
Most likely fix: Check app assignment
How to fix it
Try these in order — the most common fix is first.
1. Check app assignment
- Admin: open App Shop or IT > Apps and find the app.
- Confirm the employee's group or policy grants it.
Did this fix it?2. Reconnect the integration
- Open the app's settings in Rippling and re-authorise the connection.
- Rippling logged Salesforce disconnects on Nov 10-11, 2026 from a token change; reconnecting fixed those.
Did this fix it?3. Check seats and fields
- Confirm free licences in the app and a work email on the employee record.
- Re-run provisioning or add the user manually.
Did this fix it?
Symptoms
New hire missing from Slack, Google or another app, or an SSO login that says not assigned.
Why it happens
- Employee not in the group or policy that grants the app
- Integration token expired or disconnected
- App seat or licence limit reached
- Employee data missing a required field such as work email
- Integration incident
This guide also covers
- rippling sso not provisioning
- rippling app provisioning failed
- rippling integration disconnected
Still not working?
If Rippling keeps failing, you're not alone. See every Rippling problem users report or the alternatives people switch to.
Done fighting Rippling? Our small team builds your own Rippling alternative, or any software you need: web, mobile, games, desktop. Price agreed together.
Talk to us