Skip to main content
Kralis supports both one-by-one student creation and bulk import workflows.

Capabilities

The student area supports:
  • student creation
  • bulk import
  • export to CSV, Excel, JSON, or PDF
  • class and section placement
  • archive review
  • creator tracking where supported

Student workspace

The Students page is designed for day-to-day student-list management. Select a class from the school navigation, then use the page to:
  • search students by name and other account details
  • switch between card and table views
  • browse additional records with pagination and Load more
  • filter active, inactive, repeating, and non-repeating students where the user’s role permits those filters
  • select multiple students for supported bulk actions such as changing class or section, changing active status, deleting records, or resetting access credentials
Authorized deans and administrators can select Edit to enter table edit mode. The table separates last name, first name, and other names, and allows the student’s gender and date of birth to be corrected together. Kralis tracks only changed rows and saves them in one operation. Student saves require a first name, last name, valid gender, and date of birth. The page also provides import and export tools. Export the currently loaded student records for review or reuse, or import a CSV, Excel, or JSON file for bulk creation. Imported rows are previewed before saving, and row-level validation identifies missing required data so incorrect rows can be corrected or removed before submission. PDF export is available when a printable student list is needed. The optional fuzzy-match tool highlights records that may represent the same student. It normalizes names and compares the complete name, including other names, while allowing common differences in casing, punctuation, spacing, accents, and name order. Results are grouped visually with a related-record indicator; Kralis does not merge, delete, or modify records automatically. Use this review as a prompt for human checking. Similar names can belong to different students, and a student with incomplete or inconsistent historical data may still need manual review.

Core student data

A student record usually includes:
  • name
  • current class
  • current section when applicable
  • admission and identification details
  • contact details

Choose the right operation

Class and section rules

When assigning a student section:
  • a global section can be used with any class
  • a class-bound section must match the selected class
The same validation also applies to related annual academic records.

Creation tracking

Kralis stores created_by on student records when the creation path provides a signed-in user context. This answers who created the student record. Older records and some import/system-created records may not have this value.

Imports

Bulk imports should be reviewed carefully before commit because student identity is not something a system can deduplicate perfectly from names alone. Use duplicate checks and operator review as support, not as a guarantee. Task pages: