Docs/Full App Handbook

Plain English CodeCanyon buyer ready Screenshots and flows Developer notes

LearnX AI Full App Handbook

This page explains the whole LearnX AI LMS in simple language. It shows what the app does, who uses each part, how the modules connect, what a buyer should inspect, and where a developer can extend the system.

8role workspaces

13connected LMS modules

3report export formats

1guided buyer demo layer

What LearnX AI Is

LearnX AI is an online academy system. An academy owner can create courses, teachers can build lessons and assignments, students can learn and take exams, and staff can track results, payments, certificates, support issues, reports, and automations from one protected workspace.

Simple example An academy sells a Laravel course. A teacher builds the lessons, students enroll, the system tracks progress, students take CBT exams, submit assignments, receive feedback, and earn a QR-verifiable certificate when the rules are met.

Developer note The full LMS is Blade/Laravel based. Keep public pages, logged-in LMS routes, student routes, certificate verification, guided demo scripts, and API docs separate so private learner data is not exposed publicly.

Who Uses It

Each person sees a different dashboard and workflow. This is important for buyers because a real LMS is not one admin page; it is a set of role-specific workspaces.

Admin / Super AdminRuns the whole platform, checks dashboards, settings, AI, reports, tenants, and system health.

Academy AdminManages one academy: branding, teachers, learners, courses, reports, certificates, commerce, and readiness.

Teacher / InstructorBuilds courses, creates lessons, reviews student work, grades assignments, answers questions, and reviews performance.

StudentLearns from the dashboard and course player, asks the tutor, takes exams, submits assignments, and downloads certificates.

Reviewer / ModeratorReviews courses, question bank items, community posts, certificate approvals, and flagged tutor content.

Support StaffHelps with enrollment access, failed payments, certificate verification, notifications, and activity logs.

Corporate ManagerWatches team progress, compliance, course completion, certificates, and assessment bands.

GuardianGets a read-only learner progress view when guardian links are configured.

Role example Use an authorized account in a dedicated demo environment, then switch roles to verify each workspace remains scoped.

Full App Flow

The product starts from a public showcase, moves into a role dashboard after login, then follows the normal academy lifecycle from course creation to learning, testing, certification, reporting, and automation.

Public proof: a buyer opens /showcase and sees what the product can do before login.
Protected login: staff signs in from /login. Normal login writes logs and database notifications; it does not send email.
Role dashboard: each user lands on the right dashboard for their role, not a generic KPI wall.
Course building: teachers build course profile, media, SEO, curriculum, lessons, resources, AI assists, and review readiness.
Student learning: enrolled learners open the dashboard, course hub, lesson player, notes, bookmarks, resources, tutor, quizzes, and assignments.
Assessment and work: CBT exams, assignments, grading, corrections, result sheets, and exports feed progress and reports.
Completion proof: completion rules can issue certificates with PDF, certificate ID, QR code, and public verification page.
Operations: reports, Ask LMS, commerce, automations, community, notifications, and activity logs keep the academy running.
SaaS and mobile readiness: tenant limits, package usage, API docs, and Sanctum-ready endpoints prepare the app for future SaaS/mobile use.

Day In The Life

These short stories show how a non-technical buyer can understand the app without reading code.

Academy owner Logs in, checks academy readiness, reviews revenue, certificates, learner risk, automation runs, and AI quota.

Teacher Opens Teacher Dashboard, improves a course, adds a lesson, creates an assignment, checks CBT results, and replies to Q&A.

Student Continues a course, watches a lesson, saves notes, asks the tutor, takes a one-question CBT exam, submits work, and views released results.

Support staff Searches a student, checks activity logs, confirms payment or certificate status, and sends a reminder without seeing private data outside scope.

Buyer example In a sales call, show the teacher story first if the buyer runs a training business. Show the student story first if the buyer cares about learner experience.

Module-by-Module Explanation

Each module below has a plain purpose, a real user, an example, AI support, and a page to inspect.

Role DashboardsWhat it does: gives every role a focused command center. Who uses it: all roles. Example: admin sees platform signals; teacher sees grading and course work. AI: shows AI usage and alerts. Open: /dashboard. Course + Lesson BuilderWhat it does: builds the learning product. Who uses it: teachers and admins. Example: create "Laravel SaaS Platform Builder". AI: drafts descriptions, lessons, SEO, and readiness fixes. Open: /lms/courses. Student LearningWhat it does: lets learners continue courses, track progress, use resources, and finish lessons. Who uses it: students. AI: study coach and tutor actions. Open: /student/dashboard. CBT AssessmentsWhat it does: manages question banks, papers, one-question exams, marks, corrections, and result sheets. Who uses it: teachers, students, admins. AI: paper and question quality drafts. Open: /lms/assessments. AssignmentsWhat it does: handles practical student work, file submissions, rubrics, feedback, and resubmissions. Who uses it: teachers and students. AI: assignment, rubric, and feedback drafts. Open: assessment assignments area. AI TutorWhat it does: gives enrolled students a private course tutor with source citations. Who uses it: students and staff reviewers. AI: explanations, examples, flashcards, quizzes, and study plans. Open: course tutor pages. CertificatesWhat it does: issues completion certificates with PDF, certificate ID, QR code, and public verification. Who uses it: students, admins, public verifiers. AI: title and achievement text suggestions. Open: /lms/certificates. Reviews, Q&A, DiscussionWhat it does: creates course interaction through reviews, lesson questions, discussions, solved flags, and moderation. Who uses it: students, teachers, moderators. AI: summaries and reply drafts. Open: /lms/community. CommerceWhat it does: supports free/paid courses, coupons, bundles, invoices, sandbox payments, earnings, and manual payouts. Who uses it: admins, students, instructors. AI: pricing and revenue summaries. Open: /lms/commerce. Reports + Ask LMSWhat it does: turns progress, results, revenue, certificates, and risks into reports. Who uses it: staff. AI: safe report summaries and natural-language Ask LMS answers. Open: /lms/reports. AutomationsWhat it does: sends reminders, creates intervention cards, tracks runs, and auto-issues certificates only when rules pass. Who uses it: admins. AI: suggested rules and message drafts. Open: /lms/automations. SaaS + APIWhat it does: prepares tenant packages, limits, usage health, billing placeholders, and mobile REST API readiness. Who uses it: Super Admin and developers. AI: tenant usage and health summaries. Open: SaaS/API pages. Guided DemoWhat it does: explains the app through a draggable, restartable, refresh-safe tour panel. Who uses it: buyers, staff, developers. AI: not required. Open: /lms/demo-studio.

Connected Workflows

The strongest buyer proof is that modules are connected. A course is not isolated from exams, assignments, certificates, reports, commerce, and automation.

CBT exam flow — CBT exams save skipped, answered, marked, random order, marks, visibility, and result sheet data.

Assignment grading flow — Assignments move from instructions to submission, rubric grading, feedback release, and student progress.

Reports and automation flow — Reports detect risk, Ask LMS explains it, and automations create reminders or intervention cards.

SaaS tenant and API flow — SaaS packages, tenant health, academy limits, AI usage, and API readiness stay connected.

Connected example A student fails a quiz topic. The result sheet updates the performance band, Reports marks the learner at risk, Ask LMS can summarize the issue, and Automations can send a reminder. AI can draft suggestions, but staff stays in control.

Buyer Demo Checklist

Use this only in a dedicated internal demo environment. Demo identities are provisioned by the environment owner and are never published in documentation.

Open /showcase and show public-safe product proof.
Open /login and explain that normal login does not send email.
Sign in with an authorized demo account and open /lms/demo-studio.
Start the Full Product Demo, pause it, refresh the page, and resume it.
Open System Dashboard and show a page header, focused KPIs, charts, and attention queue.
Open Course Builder and show the wizard, readiness checks, AI assist, resources, and approval workflow.
Open CBT runtime and show Answered, Skipped, Unanswered, and Marked counters.
Open Result Sheets and show marks, bands, correction history, XLSX/PDF/CSV exports.
Open Assignments and show protected submissions, rubric grading, feedback release, and resubmissions.
Open AI Tutor and show source-backed answers, citations, transcript review, and source gaps.
Open Certificates and show QR verification, PDF download, revoke/reissue, and public verify page.
Open Commerce and show coupons, bundles, sandbox invoices, earnings, and payout requests.
Open Reports and ask: Which students are inactive?
Open Automations and preview an audience before running a rule.
Open SaaS/API docs and show tenant package limits and mobile-ready API documentation.

Shortcut Open Buyer Demo Path for the exact CodeCanyon inspection sequence with proof points and developer checks.

Screenshot Proof

LearnX AI public showcase screenshot — Public showcase: buyer-safe product proof before login.

System dashboard screenshot — System dashboard: role-specific command center, not a generic admin page.

Course builder screenshot — Course builder: course setup, readiness, curriculum, resources, and AI assist.

Assessment console screenshot — Assessments: question bank, papers, result sheets, marking, corrections, and exports.

Reports command center screenshot — Reports: Ask LMS, charts, risk signals, exports, and intervention cards.

Demo Studio screenshot — Demo Studio: module tours, role tours, health checks, and proof timeline.

Developer Notes

This section is for technical buyers and developers. Layman users can skip it.

Routes to inspect /lms/demo-studio, /dashboard/system, /lms/courses, /student/dashboard, /lms/assessments, /lms/reports, /lms/automations, /certificates/verify/{code}, and /api/docs.

Permission proof Admin and Super Admin should see everything. Academy Admin, Teacher, Reviewer, Support, Corporate, Guardian, and Student views must remain scoped by role, academy, ownership, or enrollment.

Seed data Required seeders stay production-safe. Verification/demo seeders should create isolated sample records only in an authorized demo environment; identities must not be published in documentation.

Extension points Use module services for business logic, Blade components for UI, route permissions for access, activity logs for audit, database notifications for login/security signals, and explicit email actions only for verification/reset flows.

Need	Where to look	Safe rule
Install and setup	Installation and Settings	Keep production seeders clean.
Auth and email	Authentication and SMTP Setup	Normal login never sends email.
Roles	Roles & Permissions	Staff access must be scoped.
Guided demo	Guided Demo	Safe actions only; no auto-save/delete/payment/grade.
Internal demo appendix	Demo environment checklist	Use an authorized demo account.

Troubleshooting + FAQ

Does login send email? No. Normal login only authenticates, redirects, writes activity logs, and creates database notifications. Verification and password reset emails are sent only after the user explicitly requests them.

Why do I need demo data? Buyer-grade demos need real-looking courses, students, exams, reports, certificates, and automation runs. Required seeders should stay clean; verification seeders create the sample proof.

What if screenshots are missing? Run the verification/demo data, open the target route, capture the screen, and place it under documentation/assets/media/learnx/screenshots/. Then update the screenshot manifest.

What if a guided demo step cannot highlight a control? Check the route, permission, demo reference, and data-demo-anchor. The Demo Studio health panel should report missing anchors or sample data.

What if SMTP returns authentication required? Fix SMTP settings for explicit verification/reset emails, but do not wire email into login. Login security notices must use logs and database notifications.

What should I run before packaging? Run php artisan test, php artisan view:cache, route discovery, docs link checks, screenshot checks, and browser QA for docs, showcase, login, dashboards, CBT, reports, automations, and certificate verify.