Admissions and user records
Manage schools, users, roles, classes, student records, guardians, documents, and tenant-specific access from one platform.
School ERP and AI learning platform
Run attendance, user management, school analytics, teacher content generation, lesson planning, and student text-doubt support from role-based workspaces built for real school workflows.
A production-safe snapshot of supported workflows, without fabricated dashboards or vanity numbers.
Admins manage schools and users, teachers generate and store learning content, students ask text doubts and follow-ups, and school leaders review attendance, usage, and learning activity.
The page now talks about what the EDU and StudentERP codebases actually support, keeping unfinished capabilities out of the main sales promise.
Manage schools, users, roles, classes, student records, guardians, documents, and tenant-specific access from one platform.
Record attendance by class and date, review attendance statistics, and keep daily school operations tied to the right school account.
View summaries for users, teaching content, student doubts, attendance, feature usage, popular topics, and AI cost tracking.
Give super admins, school admins, teachers, and students only the workspace and data their role is allowed to access.
Sikhsha keeps AI practical: help teachers prepare lessons and help students continue learning through text doubts, follow-ups, and practice prompts.
Generate and store structured teaching decks from topic, subject, grade level, and slide requirements.
Create lesson plans with objectives, concepts, teaching sequence, assessments, and resources.
Generate activity ideas with materials, steps, duration, learning outcomes, and classroom instructions.
Use curriculum-aware teacher tools for question generation and content preparation workflows.
The safe production promise is text-first doubt support with history, follow-ups, weak-area tracking, and similar practice problems.
Text-based doubt solving with subject detection and related concepts
Follow-up questions on previous doubts using stored context
Doubt history for students to revisit past explanations
Weak-area signals and similar problems for extra practice
The sales message is now anchored in operational pain buyers already understand, then connects that pain to existing product workflows.
A production landing page should build trust by being specific, restrained, and honest about what is ready now.
Image and voice doubt endpoints exist, but OCR/transcription solving is not marketed here as production-ready.
Bulk user import is present as an admin workflow but should be described carefully until final CSV import handling is complete.
The page avoids invented school names, customer counts, fee totals, attendance percentages, and unsupported testimonials.
Use the demo to show school setup, role-based access, attendance, analytics, teacher AI workflows, and text-doubt support with the current product state.