Most teams running ERPNext HR hit the same wall: the Employee lifecycle lives in ERPNext, but the actual learning lives somewhere else. ERPNext has an Employee Onboarding DocType with an activity checklist, and Frappe LMS is a capable course/quiz platform, but out of the box the two do not talk. So a new hire is created in ERPNext, and then someone manually creates an LMS account, manually assigns the right courses, and manually chases completion in a spreadsheet. Compliance training (safety, data-protection, code-of-conduct) has no audit trail on the employee record, certificates are PDFs in an email folder, and nobody can answer "which of our people are current on which mandatory training?" without a manual reconciliation. ERPNext native Training Event / Training Result covers instructor-led sessions but has no bridge to self-paced LMS courses, quiz scoring, or auto-enrolment.

We build a dedicated Frappe app — a proper installable module with its own hooks.py, DocTypes and permissions — that closes that gap. At its core is a Learning Path DocType (role-based, mapping a Designation, Department or Employment Type to an ordered set of LMS Courses) and an Employee LMS Enrollment DocType that records every assignment, its due date, and its state. On Employee creation and on Employee Onboarding submit, a hooks.py doc_events handler resolves the new hire's role, matches the applicable Learning Paths, and creates the corresponding LMS Enrollment records in Frappe LMS via server-side calls — no manual enrolment. When a learner finishes a course or a quiz in LMS, a doc event on the LMS Course Enrollment / Quiz Submission writes the result back: completion date, score, pass/fail against the path's threshold, and a link to the generated certificate, all posted onto a child table on the Employee record so HR sees it inline.

Technically it is built the way a Frappe app should be. Business rules that must never be bypassed (auto-enrol, score sync, certificate issue) run as server scripts / whitelisted Python methods with frappe.has_permission checks, not as client scripts that a user could skip. Client Scripts handle the in-form UX — a "Training status" panel on the Employee form, a "re-sync enrolments" button. A scheduler_events daily job sweeps for overdue and soon-to-expire compliance training (annual re-certification) and raises ToDos / notifications to the employee and their manager. Everything is reachable over the Frappe REST API and versioned whitelisted endpoints, so your LMS front-end, an external HRIS, or a Power BI report can read enrolment and completion state without touching the database directly. Role Profiles and permission rules keep L&D admins, managers and employees each seeing only what they should. It targets Frappe/ERPNext v15 and the v16 line.

Because this is build-to-order, nothing ships until we agree what you actually need. It starts with a scoping call where we map your roles to learning paths, your compliance matrix, and how your LMS is hosted (same bench, separate site, or Frappe Cloud). We build against your version on a staging site, you run UAT, and then we install into production with a rollback plan. Typical delivery is one working week from confirmed scope depending on how many role paths and compliance rules are in play. You receive the full source, the git repository, install and configuration docs, a training session, and a post-go-live support window — the app is yours, not a black box.