Connect the platform to the systems your people already use
OpenLMS is built on Drupal, which means integration is a first-class concern rather than an afterthought. Employee data, identity and learning records move through configured data exchange or standard APIs.
Key facts
- What it covers
- Employee data, identity, learning records and content libraries connected through configured data exchange or standard APIs.
- Standards
- REST and GraphQL APIs, SAML 2.0 and OpenID Connect for single sign-on, and SCORM / xAPI / H5P / YAML for content.
- Typical connections
- HRIS, identity provider, Microsoft 365, Google Workspace, Slack, Teams, and external content libraries.
- Data control
- Your data stays in your infrastructure, in your schema, under your retention policy.
- Licence cost
- HK$0. Integration work is scoped separately and quoted before commitment.
Enterprise integration
Keep employee data aligned
Receive staff profiles, departments, job information and employment status from your current HR system through configured data exchange, reducing duplicate entry and outdated records.
Use your existing enterprise identity
Connect the platform to the authentication process managed by your organisation, giving employees simpler access while IT retains identity control. Supports SAML 2.0 and OpenID Connect through Drupal modules.
Move learning information where it is needed
Plan the exchange of employee, course, attendance, completion and training record data with connected business systems using agreed fields and integration flows, via REST or GraphQL endpoints.
Learning content integrations
Bring every learning library into one experience.
SCORM
SCORM 1.2 and SCORM 2004 packages from Storyline, Captivate and other authoring tools.
xAPI
xAPI package ingestion with a minimalistic LRS for activity states and scores.
H5P
The open-source H5P interactive activity library, at no per-activity cost.
YAML packages
Export and import courses as zip packages with YAML files for version control.
Common Hong Kong enterprise integration scenarios
| Scenario | Approach |
|---|---|
| Employee onboarding triggers enrolment | HRIS data exchange fires assignment rules by department, role and start date |
| Central identity for staff and students | SAML 2.0 or OIDC single sign-on; IT retains password policy and MFA |
| Learning records back into HR | Scheduled export or API write-back of completion, certificates and licence status |
| Procurement and finance visibility | Training spend and claim data exported for existing finance systems |
| Existing content library | SCORM 1.2 / 2004 migration, plus H5P authoring in place |
| Custom internal tools | REST or GraphQL API access to courses, enrolments, records and reports |
No rows match your filter.
Questions about integrations
Specific connections depend on your source systems and agreed implementation scope.
Which HR systems can be integrated?
The platform supports configured HRIS data exchange, single sign-on and API-based data flows. Bring the system names, authentication requirements, fields and update requirements so the team can confirm the integration approach.
Do we need a commercial integration module?
Usually not. Drupal provides contributed modules for SAML, OpenID Connect, JSON:API and GraphQL. Where an enterprise connector for a specific HRIS is needed, that is a scoped piece of work rather than a recurring licence.
Can we migrate our existing courses?
Yes. The LMS Migrate module provides migration plugins and templates for migrating from Opigno. SCORM packages from other systems can be uploaded directly; structured courses can be exchanged as YAML packages.
Tell us what you need connected
Bring your HRIS name, identity provider and the reports that must keep working. We will map the data flows.