LMS Workflows — By Concept

What each role does in plain language. Only features that are linked in the live application. Diagrams flow top-to-bottom for easy reading.

Admin

Sign in & reach the control panel

Concept: An administrator signs in with email and password to manage the whole platform.

  • Entry is the Admin login page (no link from public home — direct URL).
  • After login, Dashboard shows key counts: users, courses, revenue, recent activity.
  • All further work happens from the left sidebar grouped by area.
flowchart TB A[Visit Admin Login] --> B[Enter email & password] B --> C{Credentials valid?} C -->|No| A C -->|Yes| D[Dashboard] D --> E[Use sidebar to pick an area] style D fill:#7c3aed,color:#fff
Admin

Admin sidebar menu (exact labels)

Concept: After login, the left sidebar lists every admin area. Labels below match the application menu exactly.

  • Users — Students, Kids, Instructors
  • Courses — Course Management, Workshops, Course Programmes, and four programme reports
  • Demo — Demo Sessions, Demo Sessions Report, Demo Requests
  • Cart Management — Pending Carts, Empty Carts
  • Master Data — Categories, Grade Rules
  • Documents — Students, Instructors (document files, not the Users list)
  • Top-level items: Question Bank, Payments, Certificates, Analytics, Settings, Events

Hidden in menu (not shown): Communications, Course Approvals, Assignments.

flowchart TB D[Dashboard] D --> U[Users] U --> U1[Students] U --> U2[Kids] U --> U3[Instructors] D --> C[Courses] C --> C1[Course Management] C --> C2[Workshops] C --> C3[Course Programmes] C --> C4[Programme Allotment Report] C --> C5[Programme Students Report] C --> C6[Programme Shifted Students] C --> C7[Programme Schedules Report] style D fill:#7c3aed,color:#fff
flowchart TB D2[Dashboard] D2 --> DM[Demo] DM --> DM1[Demo Sessions] DM --> DM2[Demo Sessions Report] DM --> DM3[Demo Requests] D2 --> QB[Question Bank] D2 --> PAY[Payments] D2 --> CM[Cart Management] CM --> CM1[Pending Carts] CM --> CM2[Empty Carts] D2 --> CERT[Certificates] D2 --> MD[Master Data] MD --> MD1[Categories] MD --> MD2[Grade Rules] D2 --> DOC[Documents] DOC --> DOC1[Students] DOC --> DOC2[Instructors] D2 --> AN[Analytics] D2 --> SET[Settings] D2 --> EV[Events] style D2 fill:#7c3aed,color:#fff
Admin

Build and publish a course

Concept: Create structured learning content from basics through curriculum to publish.

  • Start from Course Management — search and filter existing courses.
  • Add Course wizard — six steps: basics, description, curriculum, pricing, preview, publish.
  • Content Studio — add lessons; each lesson can have text, images, quiz, or Zoom block.
  • Optional demo lessons for prospects; categories from a linked button.
flowchart TB S[Open Course Management] --> A[Start Add Course wizard] A --> B[Fill basics & description] B --> C[Build curriculum in Content Studio] C --> D[Add lesson blocks] D --> D1[Text & images] D --> D2[Quiz] D --> D3[Zoom meeting] D1 --> E[Set pricing & preview] D2 --> E D3 --> E E --> F[Publish course] F --> G[Course appears in catalog] style F fill:#7c3aed,color:#fff
Admin

Run a programme batch for a course

Concept: A programme is a timed batch (cohort) for a course — with schedule, student allotment, and optional login credentials.

  • Create programme under Course Programmes for a published course.
  • Manage schedule — set date/time (and Zoom) per lesson.
  • Manage lesson access — open or close specific lessons/quizzes for that batch.
  • Allot students — assign purchased students; shift between batches; email programme login credentials.
  • Track via programme reports (allotment, students, shifts, schedules).
flowchart TB A[Open Course Programmes] --> B[Create programme for a course] B --> C[Set session schedule per lesson] C --> D[Control which lessons are open] D --> E[Allot students to batch] E --> F[Send credential email] F --> G[Students access via programme login] E --> H[View programme reports] style E fill:#7c3aed,color:#fff
Admin

Users, Demo, Cart Management & Settings

Concept: Common workflows using exact menu names from the admin sidebar.

  • Users → Students — list, filter, bulk enroll; open student profile.
  • Users → Instructors — create accounts; assign courses and workshops.
  • Users → Kids — view parents and their children.
  • Demo → Demo Requests then Demo Sessions — review, schedule, send invitations; view Demo Sessions Report.
  • Cart Management → Pending Carts — follow up incomplete checkouts.
  • Settings — Email Notifications, Student Email Activation, Send Test Email.
flowchart TB subgraph Users direction TB S[Students] --> SP[Student profile & enrollments] I[Instructors] --> IA[Assign courses & workshops] K[Kids] end subgraph Demo direction TB DR[Demo Requests] --> DS[Demo Sessions] DS --> DSR[Demo Sessions Report] end subgraph Cart_Management direction TB PC[Pending Carts] --> PF[Follow up checkout] end subgraph Settings direction TB SET[Settings] --> EM[Email Notifications] SET --> ACT[Student Email Activation] end
Student

Join the platform & sign in

Concept: Workforce / adult learners register from the student landing page, then sign in to learn.

  • Register — name, email, password; optional resume upload.
  • If email activation is required (admin setting): account stays pending until link in email is clicked.
  • If activation is bypassed: account is active immediately — no email step.
  • Login — email + password → Student Dashboard.
flowchart TB L[Student landing page] --> N{New user?} N -->|Yes| R[Register account] N -->|No| LG[Login] R --> ACT{Activation required?} ACT -->|Yes| EM[Click link in email] EM --> LG ACT -->|No| LG LG --> D[Dashboard] style D fill:#0d7377,color:#fff
Student

Student sidebar menu (exact labels)

Concept: The student sidebar MENU section lists every linked page. Labels match the application.

  • Dashboard, Browse Workshops, Browse Courses, My Workshops, My Courses
  • Term Calendar, Cart, Materials, Learning Access
  • Assignments, Certificates, Payments, Profile, Settings
  • ACCOUNT section: Change Password, Logout
flowchart TB D[Dashboard] D --> M1[Browse Workshops] D --> M2[Browse Courses] D --> M3[My Workshops] D --> M4[My Courses] D --> M5[Term Calendar] D --> M6[Cart] D --> M7[Materials] D --> M8[Learning Access] D --> M9[Assignments] D --> M10[Certificates] D --> M11[Payments] D --> M12[Profile] D --> M13[Settings] D --> ACC[ACCOUNT] ACC --> A1[Change Password] style D fill:#0d7377,color:#fff
Student

Buy or enroll in a course & start learning

Concept: From discovery to watching lessons and taking tests.

  • Browse Courses → open course details (linked from catalog, not a menu item).
  • Free course — enroll in one step.
  • Paid course — add to Cart → checkout → Payments flow → enrollment.
  • My Courses — open a course → lesson player → optional lesson quiz.
flowchart TB A[Browse Courses] --> B[View course details] B --> C{Free or paid?} C -->|Free| D[Enroll now] C -->|Paid| E[Add to cart] E --> F[Checkout & pay] F --> G[Enrollment confirmed] D --> H[My Courses] G --> H H --> I[Open lesson player] I --> J[Watch content] J --> K[Take lesson quiz optional] style H fill:#0d7377,color:#fff
Student

Workshops & schedule

Concept: Workshops are a separate product type with their own catalog and enrollment path.

  • Browse Workshops → workshop details (linked page) → Cart or buy now → My Workshops.
  • Term Calendar and Dashboard link to workshop schedule and detail pages.
  • Complete profile & resume for better recommendations (shown on dashboard).
flowchart TB A[Browse Workshops] --> B[Workshop details page] B --> C[Cart or buy now] C --> D[Checkout & pay] D --> E[My Workshops] F[Dashboard or Term Calendar] --> G[Workshop schedule] G --> B style E fill:#0d7377,color:#fff
Student

Programme batch access (special path)

Concept: When admin allots a student to a programme batch, they may receive separate login credentials — not the normal student email login for that content.

  • Email contains programme user ID and password.
  • Student uses programme login → accesses gated lessons for that batch.
flowchart TB A[Admin allots student to programme] --> B[Credential email sent] B --> C[Student opens programme login] C --> D[Enter batch credentials] D --> E[Access programme lessons] style C fill:#0d7377,color:#fff
Parent

Register as a parent & sign in

Concept: Parents manage K-12 children’s learning. All parent screens live under the Kids area of the site.

  • Register on kids landing — parent details plus optional first child (name, grade).
  • Login with parent email and password.
  • Browser shows an OTP confirmation step (demo OTP in current UI).
  • Land on Parent Dashboard with overview of children.
flowchart TB L[Kids landing page] --> R[Register as parent] R --> LG[Login with email] LG --> OTP[OTP confirmation] OTP --> D[Parent Dashboard] style D fill:#2563eb,color:#fff
Parent

Parent sidebar menu (exact labels)

Concept: Parent sidebar uses three section headings. Menu labels match the application.

  • CHILD MANAGEMENT — Parent Dashboard, My Children, Add Child, Enroll Course
  • TRACKING — View Schedule, Child Progress, View Payments
  • ACCOUNT — Change Password, Logout
  • From My Children (linked actions, not menu items): child profile, child settings, per-child courses.
flowchart TB SEC1[CHILD MANAGEMENT] SEC1 --> D[Parent Dashboard] SEC1 --> CH1[My Children] SEC1 --> CH2[Add Child] SEC1 --> CH3[Enroll Course] SEC2[TRACKING] SEC2 --> TR1[View Schedule] SEC2 --> TR2[Child Progress] SEC2 --> TR3[View Payments] SEC3[ACCOUNT] SEC3 --> ACC1[Change Password] style D fill:#2563eb,color:#fff
Parent

Enroll a child in a kids course

Concept: Only courses marked for kids audience with a matching grade can be assigned.

  • Open Enroll Course → pick which child.
  • System shows eligible kids courses for that child’s grade.
  • Confirm enrollment — child sees course in their My Courses.
  • Parent can later restrict access or learning hours in settings.
flowchart TB A[Open Enroll Course] --> B[Select child] B --> C[System shows grade-matched kids courses] C --> D{Grade matches?} D -->|No| C D -->|Yes| E[Confirm enrollment] E --> F[Child can see course] F --> G[Parent may limit access or hours] style E fill:#2563eb,color:#fff
Child

Child sidebar menu & learning flow

Concept: Children do not self-register. Parent creates the account via Add Child.

  • Child menu: Dashboard, My Courses, Schedule, My Profile
  • Login on shared kids login page with username + password.
  • If parent disabled account or outside allowed hours → access blocked.
  • My Courses → lesson player; parent can block a specific course.
flowchart TB MENU[Child MENU] MENU --> M1[Dashboard] MENU --> M2[My Courses] MENU --> M3[Schedule] MENU --> M4[My Profile] M1 --> FLOW[Login with username] FLOW --> C{Enabled & in allowed time?} C -->|No| X[Access denied] C -->|Yes| MC[My Courses] MC --> F{Parent allowed course?} F -->|No| X F -->|Yes| LP[Lesson player] style M1 fill:#ea580c,color:#fff style MC fill:#ea580c,color:#fff
All roles

How the roles connect

Concept: High-level relationships — who creates whom and who consumes content.

  • Admin creates courses, programmes, workshops; manages all users; configures email and events.
  • Student self-registers, purchases or enrolls, learns workforce courses.
  • Parent registers, creates children, enrolls kids courses, controls access.
  • Child learns only what parent enrolled and allowed.
flowchart TB AD[Admin sets up platform] AD --> COURSES[Courses & programmes published] AD --> USR[Users area] COURSES --> ST[Student enrolls & learns] COURSES --> PAR[Parent enrolls child] PAR --> CH[Child learns] USR --> ST USR --> PAR style AD fill:#7c3aed,color:#fff style ST fill:#0d7377,color:#fff style PAR fill:#2563eb,color:#fff style CH fill:#ea580c,color:#fff
Not included in diagrams: menu-hidden admin features (Communications, Course Approvals, Assignments admin view), and pages with no navigation links in the app.