.png)
Sync Rippling employee data to KnowBe4 so security awareness training enrollments, phishing simulations, and completion tracking stay current without manual roster management.
thePeopleStack configures the Rippling–KnowBe4 integration with Smart Group mapping that reflects your actual department and role structure, ensuring training campaigns are automatically targeted by job function and risk level rather than applied uniformly.
We validate the deprovisioning workflow against your offboarding runbook so KnowBe4 user removal is triggered reliably at termination — not days later. For clients pursuing compliance frameworks that require documented security awareness training, we also configure the completion data sync back into Rippling for a single audit-ready record.
KnowBe4 security awareness training is deployed by thePeopleStack's Rippling clients primarily to meet US compliance requirements including SOC 2, HIPAA, and state-level data privacy mandates, with training content and phishing simulations configured to reflect US threat patterns.
Canadian and cross-border operations: Canadian employees are provisioned into KnowBe4 through the same Rippling sync, with training content localized where applicable. thePeopleStack ensures PIPEDA-aligned data handling is considered when Canadian employee records are synced to the KnowBe4 platform.
The Rippling–KnowBe4 integration uses Rippling's SCIM or API connector to automatically create, update, and deactivate KnowBe4 user records based on hire, change, and termination events in Rippling. Department and role fields drive Smart Group membership for training assignment.
Yes. Rippling fields such as department, job title, location, and employment type can be mapped to KnowBe4 Smart Group criteria. This means training campaigns and phishing simulations are automatically targeted to the right employee populations without manual list management.
When an employee is terminated in Rippling, the integration can deactivate or remove the corresponding KnowBe4 user record, stopping active phishing simulations and freeing up the license. The timing and method depend on how the deprovisioning workflow is configured.
With additional configuration, KnowBe4 training completion status and phishing risk scores can be written back to custom fields in Rippling, giving HR and compliance teams a centralized view of security training status without logging into KnowBe4 separately.
A standard setup covering user provisioning, deprovisioning, and Smart Group mapping typically takes 3–5 hours. Configuring completion data sync back to Rippling or aligning campaigns to compliance frameworks adds additional scoping time.
