The training platform that won’t colonise your backlog.
You’ve inherited enough platforms that arrived as ‘simple’ and matured into ticket factories. Here’s the honest technical picture of this one: SAML/OIDC SSO in a session, HRIS sync on scoped read credentials, browser-only delivery, logging everywhere — and what stays your problem versus ours.
What this deployment actually consists of
Three integration points, in honest order of effort. SSO: SAML 2.0 or OIDC against Azure AD, Okta, Google Workspace or any compliant IdP — one working session including tests, SSO-only mode available. HRIS sync: a scoped read credential and a field-mapping session; supported connectors run event-plus-reconciliation, and the sync log shows every run. Evidence export: API keys for whatever your BI or GRC stack wants to pull.
What stays yours: IdP policy (MFA, conditional access — applied to us like any app), device standards (any modern browser or phone), and network posture (we’re SaaS over TLS; no inbound holes, no appliances). What stays ours: hosting, patching, upgrades, uptime, and the pager. The steady-state ticket profile from existing deployments is access questions and the occasional export request — coordination, not operation.
Access control that mirrors your directory
Group and attribute claims map to platform roles; deprovisioning follows the IdP; every admin action and export logs. The security review finds what it hopes to find.
The HRIS sync you can audit
Explicit field mapping, scoped reads, run logs, reconciliation backstops — and a review queue for ambiguous records instead of silent guesses.
Failure modes, documented
Missed webhooks reconcile on schedule; offline sessions sync on return; degraded states surface in admin views — the questions you’d ask in review, answered before it.
Deployed, integrated, forgotten
SSO, SCIM provisioning, API logs and uptime — the admin view of a system designed to not create tickets.
| System | Protocol | Cadence | Status |
|---|---|---|---|
| SSO | SAML / OIDC | live | Healthy |
| Provisioning | SCIM 2.0 | hourly | Healthy |
| HRIS sync | REST API | daily | Healthy |
| Exports | CSV / webhook | on demand | Healthy |
Interface shown as an illustration with representative numbers, not a screenshot — the layout is the product’s.
Bring your identity engineer to the call.
The technical session answers the review checklist directly — most teams leave with SSO staged the same day.
The evidence this page stands on
Questions buyers ask
Where is the platform hosted and what’s the data posture?
EU hosting with CDN delivery, TLS in transit, role-scoped access and logging — the security and privacy pages carry the full posture for your review pack.
What browsers and devices are supported?
Modern evergreen browsers and any reasonable Android/iOS device via mobile web — no minimum-spec drama, no plugins, no MDM packaging.
What does the platform need network-wise?
Outbound HTTPS from clients to our endpoints — no inbound connections, no site appliances, no VPN requirements. Allowlist details ship in the deployment notes.
Who handles upgrades and what breaks?
We ship continuously server-side; there’s no customer-side upgrade surface. Integration contracts (SSO, sync, export API) are versioned — breaking changes come with notice and migration windows.
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