.png)
Automate RingCentral user provisioning, phone number assignment, and offboarding through Rippling so employees have business communication tools on day one and extensions are reclaimed cleanly when they leave.
The Rippling–RingCentral integration manages RingCentral user provisioning through Rippling's identity layer. New employees in sales, support, and other teams requiring business phone numbers are provisioned into RingCentral with the correct extension, site, and call group assignments based on their Rippling department. When they leave, their RingCentral account is deprovisioned and the phone number is released as part of Rippling's offboarding workflow.
For companies using RingCentral with SSO, Rippling acts as the SAML identity provider — ensuring RingCentral access requires active Rippling authentication.
RingCentral provisioning is frequently handled by the telephony team rather than IT, creating a silo from the broader HR and IT provisioning workflow. The result is that offboarding processes don't reach RingCentral — former employees retain active extensions and voicemail access, and DID numbers aren't reclaimed for reassignment.
thePeopleStack configures SCIM provisioning and SAML SSO between Rippling and RingCentral, including site, extension, and call group mapping aligned to Rippling department and job level structure. We configure phone number assignment rules for new hires and ensure offboarding events in Rippling trigger complete RingCentral deprovisioning.
For Canadian employees, thePeopleStack ensures RingCentral provisioning is included in the standard onboarding and offboarding workflow. RingCentral's Canadian data centers and data residency options can be noted for clients with compliance requirements.
Yes. RingCentral supports SCIM provisioning and SAML SSO, allowing Rippling to automate user lifecycle management for RingCentral MVP (Message, Video, Phone) based on employment status changes.
Yes, through group-level SCIM mapping. Rippling departments can be mapped to RingCentral sites, extensions, and call groups, automating phone number assignment and call routing configuration for new hires.
RingCentral is typically used by companies with distributed teams, customer support, or sales teams that need business phone numbers. It's particularly common in mid-market companies transitioning from legacy PBX systems to cloud UCaaS platforms.
When a termination is processed in Rippling, the RingCentral account is deprovisioned — removing the extension, releasing the DID number back to the pool, and disabling voicemail and message access. This happens automatically without requiring manual IT or telephony admin action.
Standard SCIM and SSO configuration takes 1–3 hours. Phone number assignment rules and call routing configuration may require additional scoping depending on the complexity of your RingCentral setup.