Every feature, on its own card
Open a card to see that feature, and which apps have it. The list is one card per feature.
Sign in with email, phone, or roll number and a password. Each app then opens the home screen for that person's role.
Guests sign into the mobile app with a one-time code. The public website also texts a code to confirm a phone number on an inquiry or partner-college form.
Guests can enter with a Google account on the phone. The website uses the same Google sign-in when someone checks out a paid course.
A person who forgot the password can request a reset and set a new one.
A new faculty account, or any account flagged by the office, must set a new password before the rest of the app opens.
Fingerprint or face unlock on the phone hides fees, students, and other office data when the app is left in the background.
The person can sign out on the device. The server can also end a session immediately, which the phone, portal, and desktop drop in real time.
Admin, faculty, student, and guest each land on their own home. The portal and desktop cover office and faculty. The website covers the public visitor and a signed-in learner.
Office staff record a student's identity, course, photo, fees, and installment plan, then save the admission.
The phone camera reads a printed admission form and fills the student fields. Google ML Kit does the text recognition on the device.
Staff capture a passport photo, crop it, and take the student's signature on the touchscreen for the admission papers.
A searchable list of students. Opening one shows the profile, courses, fees, and payment history.
The office logs a visitor enquiry and can turn it into a full admission.
The public site's contact and course forms create a lead. Office staff read, update, and delete those leads on the phone, portal, and desktop.
Classroom courses with modules, topics, fees, and a brochure. Visitors browse them on the website. Staff edit them on the other three apps.
Staff build self-paced courses. Learners watch lessons on the website and can buy them on the phone or the website.
A batch has a name, teacher, seats, days, and class time. Staff create and edit batches, and teachers see the batches assigned to them.
Staff place a student into a batch. A website or phone purchase of an online course also creates an enrollment.
A Zoom, Google Meet, or YouTube Live link sits on the batch so students can open the class from their schedule.
Teachers post assignments and students open them. Faculty on the portal and desktop use the same job.
Notes and files are grouped by course. Staff control who may open each folder.
Notes, brochures, and receipts open in a built-in viewer. The website has its own PDF page for uploaded files.
A student can save a PDF on the phone. It stays encrypted and can be read with no network.
The office keeps a book catalog and can add a title. Students and staff reach it from the phone.
Free study cards for guests and students. Staff publish and reorder that content from the portal and the desktop.
Staff write practice tests. Learners take them on the phone, on the portal's mock-test page, and on the website.
A built-in bank of programming patterns with an access switch so the office can decide who may practice.
Guest learners get interview problems plus Flutter, Android, web, machine-learning, and design question sets stored in the app.
Teachers mark Present, Absent, or Late for a batch. Students not marked in the class window can be set absent automatically.
Employees punch in and out. The phone's HR area and the portal attendance screen record the time.
A faculty-only account on the phone is locked to the institute Wi-Fi name before the teacher can work.
Students and staff apply for leave with dates and a reason. The office approves or rejects the request.
The institute holiday list is shown to students and edited by the office.
Staff create exams, add objective questions, and choose which batch or student may see the paper.
A student sits a countdown exam, moves between questions, and gets an instant score on objective answers.
Scores, pass or fail, and a subject-wise marksheet are stored and can be opened after the exam.
If the phone loses the network during an exam, answers stay on the device and are sent when the connection returns.
Staff generate a print-ready certificate or marksheet PDF with the student photo, seals, and a verification code.
On the portal, staff drag text, the seal, the signature, and the QR block around a certificate template, then save it.
An employer opens the code on the certificate and the website says whether that credential is valid or revoked. No login is required.
The cashier records a desk payment, prints or shares a receipt, and sees what the student still owes.
A payment saved as pending waits for the office to approve or reject it before it counts as collected.
Invoices, payments, fee rules, and overdue balances. The phone has a separate ledger for cashiers. Money writes are never queued offline.
The office sees who is past the due date, the penalty, and can send a reminder with the real amount owed.
A learner pays for an online course by UPI, card, or net banking. The price includes the discount, a platform fee, and GST.
The desktop app sends a vector receipt straight to a thermal or laser printer. The phone and portal produce a PDF receipt.
Staff manage teacher profiles. The website also publishes a public faculty page for visitors.
The phone stores company, package, and designation for placed students. The website shows those stories to visitors.
Each partner school gets its own admission form and student list. The public page lives on the website. Staff manage it on the other three apps.
The office reads student feedback. The website shows testimonials on the marketing pages.
A list of student and staff birthdays so the office can send a greeting.
Campus photos are uploaded by the office and shown to visitors on the website.
Attendance, fees, and student lists can be exported. The phone writes an Excel master report. The desktop uses ClosedXML for spreadsheets.
Charts of admissions, fees, and enrollments for the office. The desktop overview is drawn from the same server screen as the portal.
Admin, faculty, and student each get a home with today's counts. The website home is the public marketing page, not an office dashboard.
A record of sensitive office actions, so a manager can see who changed what.
A personal history of recent actions, including the faculty activity page on the portal.
Institute name, UPI terminals, faculty Wi-Fi name, and other office switches.
A manager turns modules on or off per role and assigns staff to a role. The sidebar then hides what that role cannot use.
The office shows or hides student tabs such as notes, self-study, and materials. Phones pick up the change without an app-store update.
An admin can see devices that signed in and revoke one of them.
Practice accounts whose data is kept apart from real students. Test and demo rows are hidden from normal lists.
Students, teachers, and the office message each other. Group owners can add and remove members, and new messages arrive live.
The office sends one notice, such as an exam alert or a holiday, to many students at once.
The office sends birthday greetings, admission confirmations, and fee reminders on WhatsApp from the portal and the desktop.
Android alerts for chat, exams, and other events. Tapping the alert opens the matching screen.
Shaking the phone opens a short form so a user can report a problem with the app.
The HR area on the phone lists centers, departments, and job titles.
Staff records, KYC files, onboarding checklists, and company documents.
Job openings, candidates, and interview results.
Shift definitions and a weekly roster for employees.
Salary structures, advances and loans, and payslips worked out from attendance.
Work tasks, goals, reviews, expense claims, training, company assets, and resignations.
Head office tracks centers, agreements, and the royalty each center owes.
Flags unusual enrollment spikes, duplicate identities, and odd fee waivers across centers.
Staff assemble a marketing site from ready blocks and publish it. This editor is only in the web portal.
Hero, about, services, director's message, NGO work, and government-scheme pages for visitors.
A visitor sends a message from the site. It becomes a lead in the office inbox.
A public question-and-answer page about courses and the institute.
Search pages such as computer courses in Indore, written for visitors who find the institute on the web.
A learner collects courses and pays from the cart. The phone keeps the same cart for guests.
Signed-in learners on the website open reward points and badges they have earned.
A signed-in learner sees purchased courses, profile details, and account settings.
The public site can change the language of its marketing copy.
The phone reads saved screens with no network and queues edits until it can reach the server. A status pill lists anything still unsent.
Layout, cards, and the bottom bar can be changed from the server. The phone and the desktop both draw those screens.
Light, dark, or match-the-device appearance. The phone saves the choice. The portal and the website have a dark theme as well.
The desktop stores the sign-in token with Windows Data Protection, tied to the current Windows user.
The desktop reads and writes multi-sheet workbooks for rosters and reports. The phone can export the master report.
QuestPDF on the desktop sends receipts and invoices to an office printer without a browser print dialog.
The Android app asks the user to update from the store, with a Later option, at most once a day.