Integrations that make training run itself.
Three connections turn a training platform from another login into infrastructure: your HR system (so enrollment is automatic), your identity provider (so access is one click), and your data stack (so evidence flows where decisions happen). Here’s how each works.
The un-integrated platform is a spreadsheet with extra steps
Training platforms die by roster drift: the joiners nobody enrolled, the leavers still licensed, the transfers practising last role’s material. Every gap is a manual reconciliation someone forgets — and in compliance training, a reconciliation gap is an audit finding waiting for its date.
Connected to the HR system of record, the drift disappears: people flow in, across and out of training with their employment events. Identity rides your existing SSO, and the evidence — retention, coverage, risk — exports to wherever your organisation already looks at numbers.
Zoho People
Roster sync from Zoho People: joiners enrolled day one, movers re-pathed, leavers closed out.
Read the page →HROne
Employee sync from HROne — per-company configuration, same day-one enrollment model.
Read the page →Darwinbox
Roster sync for Darwinbox-run HR stacks, with entity and hierarchy scoping.
Read the page →Keka
Employee sync for growth-stage teams — the training spreadsheet, retired.
Read the page →Workday HCM
Enterprise roster sync with verified results exported back into the Workday record.
Read the page →SAP SuccessFactors
Employee Central sync with multi-entity, multi-jurisdiction assignment rules.
Read the page →Microsoft Teams
Practice reminders and one-click sessions where your workforce already works.
Read the page →Single Sign-On (SSO)
SAML 2.0 / OIDC against your identity provider — Azure AD, Okta, Google Workspace and peers.
Read the page →BI / warehouse export
Documented APIs for your analytics stack — the evidence, in your tables.
Coming soonBuilt for the messy real roster
Contractors, rehires, dual roles, sites with their own conventions — sync handles per-company field mapping and keeps a review queue for the genuinely ambiguous, so the roster stays true without silent guesses.
Security posture, stated
SSO means credentials stay with your IdP; role-scoped access controls who sees whom; every admin action and export is logged. The security page documents the full posture.
An API surface that respects your stack
Aggregates, evidence records and events export over documented endpoints — pull them into the warehouse, wire alerts into your ops tooling, or feed the HR suite’s records. Your data was never the product.
Plugged into what you run
HRIS in, results out — the connections that make enrollment automatic and reporting land where people already look.
| Channel | What syncs | Cadence | Status |
|---|---|---|---|
| HRIS | Employee sync | hourly | Live |
| SSO | SAML 2.0 | always | Live |
| Teams | Session nudges | daily | Live |
| Webhook | Results feed | realtime | Live |
Interface shown as an illustration with representative numbers, not a screenshot — the layout is the product’s.
Don’t see your HRIS?
The sync layer is built for additional providers — tell us what you run and we’ll scope the connector with you.
The evidence this page stands on
Questions buyers ask
How long does an HRIS integration take to set up?
For supported providers: an API credential, a field-mapping session and a supervised first sync — typically inside a week, run alongside your pilot rather than before it.
What data does the sync actually read?
Roster fundamentals: identity, role, department, manager, employment status. It reads what enrollment logic needs and nothing more, and the field mapping is explicit and reviewable.
Can enrollment rules differ by department or site?
Yes — paths assign by role, department, site or group, and the rules live in admin configuration your team controls. Sync supplies the facts; your policy decides the training.
Do you write anything back to our HR system?
No — the HR system stays the system of record, untouched. Training evidence exports via API for whatever your HR stack wants to ingest, on your terms.
Is there an API for custom integrations?
Yes, documented and versioned — everything the dashboards read is reachable, which is also how customers wire evidence into BI tools and internal apps.
See it on your own content.
Bring one course. We’ll show you the retention curve your current training leaves behind — and what scheduled review does to it.
- 30 minutes, on your calendar — pick a slot here
- Run on your own content wherever possible, not a canned deck
- You see the dashboards, the learner surface and the evidence exports
- No commitment — and pilot data stays yours either way