Let’s make
things clear.

Nirva is a school platform for management, principals, administrators, curriculum heads, coordinators, class teachers, subject teachers, accounts, front office, transport teams, vendors, parents and students. Each role has focused responsibilities and access.

No. Parent and teaching workspaces are parts of a wider platform connecting academic setup, learning, assessment, admissions, fees, transport, communication, school essentials and management.

Yes. Platform administrators can create and manage schools and shared catalogs. School roles operate within their school, while the Super Admin Reader provides a separate read-only platform role.

Class teachers are responsible for their assigned homeroom section and its class routines. Subject teachers are assigned to particular subjects and sections, where they record teaching activity, homework and assessment work.

A class coordinator oversees a class across its sections. A curriculum head follows the assigned board or curriculum for an academic year. These are different academic scopes, rather than identical access to everything.

Yes. A person can hold compatible school roles and switch the active role. Platform roles and school roles are kept separate.

Yes. Schools can organize multiple curricula, with their own classes, subjects, academic setup and academic leadership assignments.

No. Administrators can control configurable features by role, including chat, internal email, channels, helpdesk and question papers. Introduce the workflows that fit your school.

Yes. Linked parents can switch between their children to see the relevant school information and actions in their workspace.

Students can access their assigned school information, including learning materials, homework, class schedules, attendance and marks. Availability depends on school setup and permissions.

Nirva includes chat, channels, circulars and eMails(Internal). Schools configure access by role. Internal email is communication inside Nirva; it is not a replacement for a public email address.

Yes. Timetable grids and exam schedules can be reviewed and edited before they are saved. Teachers can adjust the relevant dates, periods, times and subjects.

No. AI can suggest questions, syllabus content and answer-sheet marks. Teachers review generated content. Answer-sheet items must be confirmed before the assessment is finalized.

AI features depend on the school’s configuration and the configured provider. Discuss the features and usage your school needs during setup; generated content still needs educator review.

Front-office workflows cover admission enquiries, admissions, student records and early pickup, helping staff follow requests and the next action.

Accounts teams can configure fees and track invoices, payments and receipts. Online payment availability depends on the school’s payment configuration and provider setup.

Transport workflows cover routes, stops, vehicles and boarding records. These help teams organize school transport; live GPS tracking is not promised by these workflows.

Vendors have a dedicated role to manage their own product catalog and fulfill orders. The school marketplace connects families with school essentials such as books and uniforms.

Yes. The platform includes consent, early pickup, wellbeing records, portfolios, feedback and helpdesk workflows, alongside operational areas such as library and meals.

It means twelve hours of customer care each day, seven days a week. Contact us to agree the applicable service window, time zone, contact channels and escalation process for your school. This does not imply a guaranteed resolution time.

Yes. Start a conversation about your academic structure, student and staff data, roles and priority workflows so we can discuss setup and the support your team needs.

Yes. The platform offering includes frequent product releases, feature additions, refinements and fixes. Specific feature availability and rollout timing should be discussed with the team.

Release continuity is a design goal: improvements should arrive with as little disruption as possible. Some infrastructure or database changes may require maintenance. A blanket zero-downtime guarantee is not currently published; discuss maintenance communication and any contractual availability requirements with us.

Use the available feedback and helpdesk workflows, or contact the team to describe the need and who it affects. Suggestions help inform improvements; a request is not a promise of a specific delivery date.

Nirva combines modern web and mobile technologies, cloud deployment and AI-assisted workflows. The focus is on simpler daily operations, connected school information and ongoing improvements with minimal disruption.

The application uses school scope, role checks and assignment-based access in its workflows. Users do not all receive the same visibility. Discuss your institution’s privacy, retention and compliance requirements before onboarding.

The product includes supported import workflows, including student and staff CSV imports. File formats and required fields need to match the application. Review your source data and the available templates during setup.

No. This website doesn’t collect or store anything itself. Its “Let’s talk” links open the Nirva app’s Talk to us page, where the details you enter are sent to the Nirva team so we can get back to you.

Yes. Nirva has mobile apps for Android and iOS, with dedicated screens for families, teaching, administration and operations. The apps connect to the same backend as the web platform. Contact the team for current access, distribution and role-specific feature coverage.

Yes. The mobile apps and web product connect to the same Nirva backend. Your account, role and school assignments determine the information you can access; the mobile interface is designed for touch and smaller screens.

The apps share the same platform purpose and include many dedicated workflows, but screen coverage continues to evolve. Dense setup, imports and some bulk tasks remain web-first. Confirm the mobile workflows your team needs during onboarding.

Contact the Nirva team for the current installation or distribution route for your school. Public app-store download links will be shared when available; the platform badges here describe supported app targets rather than linking to unverified listings.

Plan to use an internet connection for current school information and updates. Full offline operation is not promised. Ask about your specific connectivity needs during setup.

Tell us about your student count, campuses, curricula and priority workflows. We can discuss a walkthrough, configuration, support and pricing for your needs. Exploring this site requires no payment or account.