LMS Feature Overview

This page maps out every feature in the LMS before you read the individual feature pages. Use it as a reference to understand how everything connects and in what order things need to be set up.

---

​

Feature Relationship Map

---

​

Feature Catalogue

​

1. LMS Course

What it does: The central unit of learning. A course organises all content - chapters, lessons, quizzes, and assignments - into a structured learning path that learners progress through. Who uses it: Course Creator (builds it), Learner (takes it), Instructor (manages it) Business goal: Creates a permanent, reusable body of learning content that any number of learners can access at any time. Typical usage scenario: A lecturer creates a “Digital Marketing Fundamentals” course with five chapters. Each chapter has four video lessons and one quiz. The course is published and 200 students enrol. Each student progresses at their own pace. Status flow: Upstream dependency: Instructors must be set up as users. Categories (if used) should be pre-configured. Downstream impact: Drives enrolments, progress tracking, quiz submissions, assignment submissions, reviews, and certificate eligibility. Records involved: LMS Course, Course Chapter, Course Lesson

---

​

2. Course Chapter & Lesson

What it does: Organises a course into sections (chapters), each containing individual lessons. A lesson can be a text article, a YouTube video, a quiz, an assignment, or SCORM content. Who uses it: Course Creator / Instructor Business goal: Structures learning content so it is digestible, sequenced, and trackable. Typical usage scenario: A course on “Business Communication” is divided into five chapters. Chapter 1 contains three text lessons and ends with a quiz. Chapter 3 has two video lessons and an assignment to submit. Status flow: No workflow - saved and published with the parent course. Upstream dependency: LMS Course must exist. Downstream impact: Each lesson completion creates a Course Progress record. Quizzes inside lessons create Quiz Submissions. Assignments create Assignment Submissions. Records involved: Course Chapter, Course Lesson

---

​

3. LMS Quiz & Questions

What it does: Embeds knowledge checks directly inside course lessons. Learners answer multiple-choice questions, get instant scores, and see whether they passed or failed. Who uses it: Course Creator (builds quizzes), Learner (takes them) Business goal: Reinforces learning and checks comprehension without requiring instructor involvement for every test. Typical usage scenario: At the end of each chapter, a 10-question multiple-choice quiz checks understanding. Learners must score 70% to pass. The quiz can be attempted up to 3 times. Status flow: No workflow - quiz is configured and linked to a lesson. Upstream dependency: LMS Course and Course Lesson. Downstream impact: Creates LMS Quiz Submission records per attempt. Scores are recorded and displayed to the learner. Can be set to show or hide correct answers after submission. Records involved: LMS Quiz, LMS Quiz Question (LMS Option), LMS Quiz Submission, LMS Quiz Result

---

​

4. LMS Assignment

What it does: Creates a task that learners must submit a file or written response for. Instructors can optionally grade submissions. Who uses it: Course Creator / Instructor (creates), Learner (submits), Evaluator (grades) Business goal: Provides assessed tasks that require more than multiple-choice answers - essays, reports, projects, case studies. Typical usage scenario: In a Marketing course, each chapter ends with an assignment: “Write a 500-word analysis of the case study.” Students upload a PDF. The instructor reviews and marks each submission. Status flow: Assignment Submission moves from Pending to Graded once the evaluator marks it (only applies when Grade Assignment = Yes is enabled on the assignment). Upstream dependency: LMS Course, Course Lesson. Downstream impact: Creates LMS Assignment Submission per learner. If grading is enabled, evaluator reviews and marks each submission. Records involved: LMS Assignment, LMS Assignment Submission

---

​

5. LMS Batch

What it does: A time-bound, instructor-led learning programme. Unlike a self-paced course, a batch has fixed start and end dates, a weekly timetable, scheduled live classes, and a defined instructor team. Who uses it: Instructor (runs it), Learner (joins it), Administrator (sets it up) Business goal: Delivers structured, cohort-based learning where all learners progress together - similar to a traditional class, but delivered online or in a hybrid format. Typical usage scenario: A “Project Management Professional” batch runs for 8 weeks starting 1 June. It includes three courses, weekly Monday and Thursday live classes, and mid-term and final assessments. 25 learners enrol. All progress through the same timetable together. Status flow: Upstream dependency: LMS Courses must exist and be added to the batch. Instructors must be set up. Downstream impact: Creates LMS Batch Enrollment records. Drives timetable, live classes, assessments, and batch-level feedback. Records involved: LMS Batch, Batch Course, LMS Batch Enrollment, LMS Batch Timetable, LMS Batch Feedback

---

​

6. LMS Live Class

What it does: Schedules and manages a Zoom-based live session within a batch. Creates the Zoom meeting, sends join links to participants, and automatically records attendance when the session ends. Who uses it: Instructor (hosts), Learner (joins), Administrator (sets up Zoom integration) Business goal: Brings synchronous, real-time teaching into the LMS without requiring learners to manage separate Zoom links. Typical usage scenario: Every Monday, the batch instructor schedules a 60-minute live class. Zoom credentials are integrated. The join link appears in the learner’s timetable. After the class ends, Zoom attendance data is pulled in and learners who joined are marked as having attended. Status flow: No submission workflow - scheduled as an event. Automatic triggers:

• Live class reminder email sent to participants daily (automated scheduler)
• Attendance records updated hourly from Zoom data

Upstream dependency: LMS Batch, Zoom integration configured in LMS Settings. Downstream impact: Attendance records created per participant. Learners who miss live classes are visible to instructors. Records involved: LMS Live Class, LMS Live Class Participant

---

​

7. LMS Enrollment

What it does: Records that a specific learner has enrolled in a specific course. Tracks their current lesson, progress percentage, and whether they have earned a certificate. Who uses it: System (created automatically when a learner enrols), Learner, Administrator Business goal: The core link between a learner and their course - enables progress tracking, certificate issuance, and reporting. Typical usage scenario: When a student clicks “Enrol” on a course, an LMS Enrollment record is created automatically. As they complete each lesson, the progress percentage updates. When they reach 100%, they become eligible for certification. Status flow: Enrolled → In Progress → Completed (progress = 100%) Upstream dependency: LMS Course must be published. Payment completed for paid courses. Downstream impact: Enables Course Progress tracking, Quiz and Assignment tracking, and Certificate issuance. Records involved: LMS Enrollment, LMS Course Progress

---

​

8. LMS Certification

What it does: Manages the process of evaluating a learner’s mastery of a course and issuing a formal certificate. Includes the learner’s request, the evaluator’s scheduling, the evaluation session itself, and the final certificate. Who uses it: Learner (requests), Evaluator (conducts), Administrator (manages) Business goal: Provides a formal, verified credential that the learner has demonstrated mastery - not just completion - of the course content. Typical usage scenario: After completing a 12-week programming course, a student requests a certificate evaluation. The evaluator sees the request, schedules a 30-minute Google Meet assessment for next Tuesday. The student and evaluator both receive a calendar reminder the day before. After the session, the evaluator marks the result as Passed. A certificate is generated and published on the student’s profile. Status flow: Automatic triggers:

• Certificate Request Reminder email sent 1 day before the evaluation (to learner and evaluator)
• Evaluation scheduled automatically via LMS scheduler (hourly)
• Evaluation marked as completed automatically after end time passes

Upstream dependency: LMS Course, LMS Enrollment (learner must be enrolled and have completed the course). Downstream impact: LMS Certificate issued and optionally published on learner’s public profile. Records involved: LMS Certificate Request, LMS Certificate Evaluation, LMS Certificate

---

​

9. LMS Payment

What it does: Records the transaction when a learner pays for a paid course or batch. Stores the payment amount, gateway reference, and coupon applied (if any). Who uses it: System (created on checkout), Finance Team (reviews), Learner (completes) Business goal: Handles monetisation of courses and batches - from payment gateway checkout through to enrolment confirmation. Typical usage scenario: A learner selects a ₹2,999 “Data Analysis” course. At checkout, they apply a 20% discount coupon, reducing it to ₹2,399. They pay via Razorpay. A Payment record is created, linked to the enrollment. The course unlocks immediately. Status flow: Automatic triggers:

• Payment reminder email sent daily for unpaid orders
• Batch start reminder sent daily for confirmed enrollments

Upstream dependency: LMS Course or LMS Batch with Paid flag enabled. Payment gateway configured. Downstream impact: LMS Enrollment or LMS Batch Enrollment unlocked after payment. Revenue recorded. Records involved: LMS Payment, LMS Coupon

---

​

10. LMS Badge & Gamification

What it does: Automatically awards digital badges to learners when they meet defined criteria - completing a course, reaching a score, or achieving a milestone. Who uses it: Administrator (configures), Learner (receives) Business goal: Motivates learners to complete courses and achieve goals by recognising accomplishments with visible digital awards. Typical usage scenario: A badge is configured: “When a learner completes their first course, award the ‘First Step’ badge.” Every time any learner completes their first course, the badge is assigned automatically. Status flow: No workflow - badge assignment is automatic based on configured conditions. Automatic trigger: Badge process runs on every record change (doc_events → on_change). Badges are checked and awarded continuously. Records involved: LMS Badge, LMS Badge Assignment

---

​

11. LMS Programme

What it does: Groups multiple courses into a structured learning path that learners can follow in sequence. Who uses it: Course Creator, Learner Business goal: Creates guided learning journeys where the sequence matters - for example, “Complete these 5 courses to become certified in Data Science.” Status flow: Draft → Published Records involved: LMS Programme, LMS Programme Course, LMS Programme Member

---

​

12. LMS Mentor Request

What it does: Allows learners to request a mentor for a course - a more experienced practitioner who can guide their learning and practice. Who uses it: Learner (requests), Mentor (responds), Administrator (reviews) Status flow: Automatic triggers:

• Email sent to learner when their mentor request status changes

Records involved: LMS Mentor Request

---

​

13. LMS Lesson Notes

What it does: Allows learners to take personal notes while watching a lesson or reading content. Notes are saved per-lesson and private to the learner. Who uses it: Learner Records involved: LMS Lesson Note

---

​

Setup Sequence for LMS

When setting up the LMS for the first time: