Mandatory Training and Validity

Corporate deployments use Mandatory Training and Validity Period (Days) on LMS Course plus LMS Training Assignment rows to drive due dates, overdue status, portal widgets, and HR onboarding automation. This guide explains configuration, assignment APIs, renewal strategy, and how LMS complements HR compliance records.

Help URL: smoothhiring.com/help/lms/courses/mandatory-training-and-validity

Table of Contents

1. Course-level flags
2. LMS Training Assignment
3. Onboarding auto-enrollment
4. assign_mandatory_training API
5. Learner portal experience
6. Renewals and validity
7. Reporting
8. Desk paths
9. Step-by-step
10. Tips
11. Troubleshooting
12. Related guides
13. HRMS integration

Course-level flags

On LMS Course → Course Settings:

Description on validity field: "After expiry, employees must recertify." Implement renewal by creating new assignment rows or re-enrollment campaigns—schedule via calendar playbooks.

Pair with Disable Self Learning so only assigned employees enroll.

LMS Training Assignment

DocType LMS Training Assignment (TA-####):

Moderators and System Managers create assignments; students read own rows.

Onboarding auto-enrollment

Hook on_onboarding_created (lms.lms.hrms_integration):

1. Loads employee user_id from Employee.
2. Finds published courses where is_mandatory = 1.
3. Creates LMS Enrollment per missing course.
4. Creates LMS Training Assignment with due date = today + 30 days.

Requires HR onboarding document with employee field populated.

assign_mandatory_training API

Whitelisted assign_mandatory_training(course, employees, due_date):

• Callers: System Manager, Moderator
• Skips duplicate open assignments (Pending/In Progress)
• Auto-creates enrollment if missing
• Returns count assigned

Use for annual refresh, department sweeps, or ad-hoc remediation after incidents.

Learner portal experience

StudentHome shows Mandatory Training list via get_my_training_assignments with course title, image, due date, status, progress from enrollment.

Overdue assignments remain visible until completed—pair with email jobs or HR outreach.

Renewals and validity

Validity days are informational unless you operationalize:

1. Track Completed On + validity in reporting spreadsheet, or
2. Build scheduled job (custom) to create new assignments when expiry approaches, or
3. Mirror renewals in Employee Compliance with renewal periods

LMS certificate printout can include completion date for auditors.

Reporting

• Desk list /app/lms-training-assignment filtered by Overdue.
• Portal Statistics page shows Mandatory Training Compliance widget (counts assigned/completed/overdue) for admins.
• Learning workspace enrollment shortcuts for progress = 100.

Export quiz PDFs for proof of comprehension, not just completion click-through.

Desk paths

Step-by-step

Configure compliance course

1. Edit Harassment Prevention course.
2. Check Mandatory Training; set Validity Period 365.
3. Check Disable Self Learning.
4. Publish.

Assign department

1. Moderator opens assign tool with course, user list, due date.
2. Submit—verify assignments created.
3. Email employees link to /lms/courses.

Onboarding test

1. Create employee with user.
2. Submit Employee Onboarding.
3. Confirm enrollment + assignment.
4. Complete course; status → Completed.

Renewal cycle

1. Before expiry, run assign API again with new due date.
2. Optionally reset enrollment progress via support script (custom).
3. Update HR compliance record renewal date.

Tips

• Align due dates with payroll cutoff or audit seasons.
• Use 30-day onboarding default as template—adjust in hook if needed via custom app.
• Keep mandatory course count small for new hires (<5) to avoid fatigue.
• Document difference between LMS completion and HR compliance sign-off.

Troubleshooting

Related guides

• First setup
• Roles and permissions
• Enroll employees

HRMS integration

• Employee Onboarding overview — triggers auto-enrollment
• Employee records — source of user_id
• Employee Compliance — regulatory renewal ledger alongside LMS validity

Course completion certificates do not replace compliance records unless your process explicitly merges them.

HR alignment workshop

Meet with compliance owners to define: which courses are mandatory, validity days, due date policy, and whether LMS completion satisfies Employee Compliance or requires additional attestation. Document escalation for Overdue assignments—manager notification vs HR ticket.

Annual recertification: run Moderator bulk assign with new due dates; communicate via email linking /lms/courses.

Governance, auditing, and data retention

Training data in Smooth LMS is standard Frappe JSON in MariaDB plus files in public/files and public/scorm. HR audits typically require evidence of who completed what by when. Export desk lists (LMS Enrollment, LMS Quiz Submission, LMS Training Assignment, LMS Certificate) to CSV for sampling. Quiz submission print formats provide question-level detail suitable for safety investigations or harassment prevention audits.

Retention policy should align with HR document retention: keep LMS submissions at least as long as related Employee Compliance records. When employees depart, disable User accounts but retain enrollment history unless legal counsel approves purging. Version course content via amended records or annual duplicated courses so historical completions still reference the correct curriculum year.

System Managers should restrict Moderator role membership and enable login activity review on sensitive cohorts (executive leadership programs). Pair LMS reports with HR onboarding status from Employee Onboarding overview to prove training preceded start date when required.

Frequently asked questions

Do employees need desk access? No. LMS Student is portal-only by default; send {site}/lms/courses links.

Can one user be both Course Creator and Moderator? Yes on small teams; larger orgs should separate author vs publish duties.

How do we handle contractors? Create User + optional HR employee record; assign training like employees via Employee records linkage or direct enrollment.

What breaks if HRMS is down? LMS continues serving published content; new hire auto-enrollment pauses until Employee/Onboarding APIs succeed.

Are certificates legally equivalent to HR compliance rows? Not automatically—store PDFs on compliance or document types when statute requires.

Performance and scale notes

Large enrollments (5,000+ users) should batch assign overnight via assign_mandatory_training rather than manual enrollment rows. Rebuild website cache after bulk publish. Monitor background workers if email notifications queue heavily. SCORM packages should be optimized zip exports to reduce disk usage during large uploads.

Additional troubleshooting

Operations calendar (recommended)

Integration smoke tests with HRMS

1. Create test Employee with user — confirm LMS Student role.
2. Submit test Employee Onboarding — confirm enrollments when courses mandatory.
3. Complete course — attach quiz PDF to test Employee Compliance row.
4. Archive evidence in document compliance SOP.

Support runbook (L1)

Collect: user email, course/cohort name, screenshot of error, timestamp. Check enrollment exists, course published, role present. Escalate to System Manager if SCORM extract failed or permission hooks deny batch access. Reference Employee records to fix missing user_id before reassigning training.

Document history and change control

When updating this process, record the Smooth LMS app version, platform update date, and whether HRMS onboarding templates changed. Authors should note breaking changes in course release notes (quiz question changes may require reattempts). For regulated customers, maintain a binder linking LMS course ID to compliance control ID in Employee Compliance.

Desk administrators use /desk/learning for cross-course metrics; portal users rely on /lms/courses for consumption—both URLs should appear in internal SOP PDFs so auditors can reproduce learner steps without admin credentials.

Last updated: May 2026

Smooth HR (HRMS)