.png)
Connect Rippling to GoTo Meeting so video conferencing access is provisioned at hire, licensed by role, and deprovisioned at offboarding — with Rippling driving meeting platform access the same way it drives every other communication tool.
thePeopleStack configures the Rippling–GoTo Meeting integration with SSO enforced and license tier assignment mapped to Rippling role data — ensuring organizer licenses go to employees who need to host meetings while attendee licenses are assigned to those who don't. We configure the offboarding workflow to deactivate GoTo Meeting accounts and release licenses at termination, preventing seat cost leakage from departed employee accounts.
For clients using GoTo Meeting as part of a broader GoTo product portfolio — alongside GoTo Connect or GoTo Webinar — we ensure the Rippling provisioning configuration covers all GoTo products consistently, preventing gaps in communication access that arise when each product is provisioned through a separate workflow.
GoTo Meeting is deployed by thePeopleStack's Rippling clients primarily for US-based video conferencing and online meeting workflows, with provisioning and licensing structured around US team communication requirements.
Canadian and cross-border operations: Canadian employees are provisioned into GoTo Meeting through the same Rippling sync, with thePeopleStack confirming that data handling and PIPEDA considerations for meeting recordings and attendee data are addressed for cross-border GoTo Meeting deployments.
GoTo Meeting is LogMeIn's video conferencing and online meeting product — distinct from GoTo Connect (which includes UCaaS telephony and messaging) and GoTo Webinar (which handles large-scale broadcast events). The Rippling integration provisions GoTo Meeting user accounts at hire and deactivates them at offboarding, keeping the meeting platform roster current without separate IT admin action.
Rippling job title and department data informs GoTo Meeting's organizer license assignment — ensuring employees who need to host meetings receive organizer licenses at hire, while employees who only attend meetings receive the appropriate attendee license tier. This prevents over-purchasing organizer seats for employees who don't need them.
Employee termination in Rippling deactivates the GoTo Meeting account, releasing the license and preventing former employees from hosting meetings on company credentials. Any scheduled meetings owned by the departing employee can be transferred to their manager or a designated successor as part of the Rippling offboarding workflow.
Yes. Rippling can be configured as the SAML identity provider for GoTo Meeting, allowing employees to authenticate using their Rippling credentials. SSO deactivation through Rippling offboarding ensures meeting platform access is revoked immediately at termination.
A standard configuration covering SSO, user provisioning, license tier assignment, and offboarding deprovisioning typically takes 2–4 hours. Organizations using GoTo across multiple products — Meeting, Connect, and Webinar — may require additional scoping to ensure each product's provisioning is configured consistently from Rippling data.
