Hevra ERP · Product documentation
University Management Module
A complete guide to the academic, administrative, financial and student-service capabilities of the Hevra University module, and to every interface it has with other Hevra modules and third-party services.
Edition 1.0 · November 2026
- 177
- screens in the module
- 1,160+
- API operations
- 294
- permission keys
- 150+
- university data tables
- 3
- academic systems
- 40+
- built-in reports
- 10
- ready-made university roles
- 4
- notification channels
Inside this brochure
- 01Module overviewThe University module runs a higher-education institution end to end: from the first online application to graduation, with fees, exams, services and reporting in one system.
- 02Platform, security and access controlThe backend is the security authority. Every university request passes authentication, tenant resolution, permission checks and data-scope rules before it reaches business logic.
- 03Academic systems and policiesOne installation can run three academic systems side by side, each with its own rules for stages, credits, fees and results.
- 04Setup and administrationThe setup area builds the institution's structure once, so that every other screen can rely on it.
- 05Curriculum and schedulingCourses move from a catalogue to a department plan, then to a semester offering, and finally to classes with teachers, rooms and times.
- 06AdmissionsApplicants apply online through a secure public link; admissions staff review the case, verify documents and accept the applicant as a student.
- 07Student records and lifecycleEvery student has one master record and a history of stages. All academic, financial and service events attach to that record.
- 08Teaching operations and attendanceTeachers record attendance and manage their classes; the system calculates absence percentages and applies attendance-failure rules.
- 09Examinations and resultsMarks flow from teachers to the exam committee through a controlled workflow, and results are published to students only when the institution decides.
- 10Tuition and student financeFees are defined per department, stage and system; each student's charges, discounts and payments are kept in a running student account that posts automatically to Accounting.
- 11Student services, dormitory and libraryNon-academic services are handled in the same system, so clearance and graduation can check every office at once.
- 12Quality assurance and evaluationQuality work and course evaluation are built in, so evidence for accreditation is collected as part of daily operations.
- 13Reports and analyticsMore than forty reports cover academic, financial, administrative and regulatory needs, and a custom report builder lets users design their own.
- 14Student portal and mobile appStudents serve themselves: profile, classes, results, payments, absences, assignments and course selection, on the web or in the Hevra mobile app.
- 15Interfaces with other modules and third-party servicesThe University module is connected to the rest of Hevra ERP through defined contracts, and to outside services through configurable connectors.
- 16Roles and permissionsReady-made roles cover the usual university offices; each can be adjusted with the 294 granular permissions.
- 17Data modelAbout 150 tables hold university data, all stored per tenant and accessed through Prisma.
- 18Implementation and onboardingA new institution can be live quickly: provision the tenant, load the structure, import students and verify with the built-in checks.
- AScreen atlasEvery screen of the University module as captured from the running system: 180 screens.
All screenshots were taken from the live system using a demonstration tenant (Hevra Demo University) filled with fictitious students, staff and amounts.
Chapter 01
Module overview
The University module runs a higher-education institution end to end: from the first online application to graduation, with fees, exams, services and reporting in one system.
Hevra ERP is a multi-tenant enterprise platform. The University module is one of its licensed modules and can be switched on for any tenant (an institution or a group of colleges). It shares the platform's users, security model, accounting, notifications and file storage, so a university does not need separate systems for registration, finance and services.
The module is organised around the student lifecycle. Administrators first build the academic structure (faculties, departments, years, semesters, curricula), then admit students, register them into classes, record attendance and marks, collect tuition, deliver services such as dormitory and library, and finally graduate them. Every step is reported on and audited.
Three user groups work in the module: staff in the back office (registrar, finance, exam committee, deans and heads of department), teachers in their own scoped workspace, and students in the self-service portal on the web or mobile app.
What the module covers
- Academic setup and configuration
- Curriculum, classes, timetables and exam schedules
- Online admission and application cases
- Student records and the full lifecycle
- Attendance for students and teachers
- Examinations, results and grade appeals
- Tuition, installments, discounts, scholarships and payments
- Dormitory, library, clearance and graduation services
- Quality assurance and course evaluation
- More than 40 reports, dashboards and a custom report builder
- Student self-service portal and mobile app
- Interfaces with Accounting, HR, Notifications, AI and external services
In the system
Chapter 02
Platform, security and access control
The backend is the security authority. Every university request passes authentication, tenant resolution, permission checks and data-scope rules before it reaches business logic.
- Hierarchy Scope
- Transaction Logs
- Bulk Status History
- Feature licensing
- Finalised-year lock
- Hidden students
Each request carries the user's session and the active tenant. The module then checks that the tenant has the University feature licensed, that the user holds the permission for the action (for example university.financial.payments.view), and that the record lies inside the user's data scope. Resource-level policies add a further check for sensitive records such as student documents, finance and exam results.
Permissions follow the pattern university.<resource>.<action>. They are grouped into roles, and roles are assigned to users per tenant. Scope rules limit what a role can see: a head of department sees only their department, a teacher only their own classes, and a student only their own record. Full institutional access is reserved for the university.manage_all permission.
Organisational scope is managed on the Hierarchy Scope screen: org units (university, college, department), leadership assignments with start and end dates, and user scope assignments. Changes to records are written to the audit log and the university transaction log, and bulk status changes keep a history that can be reviewed later.
How it works
Key capabilities
Hierarchy Scope
Org units, leadership assignments and user scope assignments that drive department and college level data visibility.
Transaction Logs
A searchable trail of who created, changed or deleted university records, with old and new values.
Bulk Status History
History of mass student status changes, with the batch, the actor and the affected students.
Feature licensing
Each tenant enables the University module and its feature set; pages and APIs that are not licensed are hidden and refused.
Finalised-year lock
Marks and academic records of a finalised academic year can only be changed with an explicit confirmation and the right permission.
Hidden students
Selected student records can be hidden from general lists and reports while staying in the database.
In the system
Chapter 03
Academic systems and policies
One installation can run three academic systems side by side, each with its own rules for stages, credits, fees and results.
- Settings & Configuration Catalog
- Grading Systems
- Constants
Coursat is the credit-hour system: students choose courses each semester within minimum and maximum credit limits, and their progress is measured by earned credits and GPA. Bologna follows the European ECTS model with points per course, levels and Bologna-specific registration payments. Annual is the year-based system, where a student is promoted from one stage (First Year, Second Year and so on) to the next at the end of the year.
The system type is set on semesters, presented departments, department subjects and fees, so different departments can follow different systems. The configuration catalog holds the policy values that drive behaviour, for example the elective course limit per semester, the maximum credits in a short semester, the average groups used for ranking, the default pass grade and the number of failed courses allowed. Each value has a default and a history of changes.
Grading systems translate numeric marks into grades and grade points. Stage settings define the names and order of study stages, and numbering plans control how student codes, usernames and document numbers are generated.
Key capabilities
Settings & Configuration Catalog
General settings, semester settings, stage names, numbering plans and the policy catalog with defaults and change history.
Grading Systems
Mark ranges, letter grades and grade points per grading system.
Constants
Reference values such as study levels, entrance types and status lists used across the module.
In the system
Chapter 04
Setup and administration
The setup area builds the institution's structure once, so that every other screen can rely on it.
- University Setup
- Test Wizard / Complete Test
- Faculties
- Departments
- Teachers
- Educational Years
- Semester Definitions
- Semester Academic Calendar
A guided University Setup page and a Test Wizard walk a new institution through the required order. The Complete Test screen checks each dependency (years, semesters, faculties, departments, subjects, classes, students and so on) and shows what is still missing. Large structures can be loaded in one step from an Excel workbook that covers years, semesters, faculties, departments, teachers, subjects, classes, timetables, exam schedules, fees and installments.
Key capabilities
University Setup
Guided first-time setup of the institution.
Test Wizard / Complete Test
Dependency-aware checklist that verifies each setup step and can seed sample records.
Faculties
Colleges with codes, abbreviations and status.
Departments
Departments per faculty with codes, permanent failed fee, required credits and project criteria.
Teachers
Teaching staff with scientific rank, faculty, login account and optional link to an HR employee.
Educational Years
Academic years with failed-course limits and curve credit.
Semester Definitions
Semesters per year and system with dates, registration windows, add/drop and withdrawal deadlines.
Semester Academic Calendar
The calendar view of semesters, including date overrides and the 'apply available' switch.
Shifts
Morning and evening study shifts with times.
Countries
Countries used for nationality, birth place and qualifications.
Documents
Institution document repository with type, entity and upload.
Clients
The ERP's shared client register (also used by Sales and Accounting), extended with university-specific dynamic fields.
Outcome Mappings
Learning outcomes mapped to courses for outcome-based assessment.
Excel bulk setup
Download a template, validate it and import hundreds of setup records in one operation.
In the system
Chapter 05
Curriculum and scheduling
Courses move from a catalogue to a department plan, then to a semester offering, and finally to classes with teachers, rooms and times.
- Modules (Subjects)
- Department Modules
- Presented Departments
- Presented Modules
- Prerequisites
- Classes
- Classes Management
- Class Info
A subject (module) is defined once. It is attached to a department's study plan with its stage, semester and credits (Department Subjects), then offered in a specific year and semester (Presented Subjects). Each offering is split into one or more classes (sections) with capacity, teacher and timetable. Prerequisites, parallel courses and group classes control who may register and how sections are shared between departments.
Classes Management is the operational hub for a class: its information and teacher description, enrolled students, attendance, midterms, assignments, complaints and the visibility of midterm and final results.
How it works
Key capabilities
Modules (Subjects)
The course catalogue.
Department Modules
The study plan of each department with stage, semester, credits and course type.
Presented Departments
Departments open for a semester, with study level, system and entrance type.
Presented Modules
Courses offered in a semester; can be loaded from the study-plan pattern or imported.
Prerequisites
Pass-required, pass-adequate, concurrent and satisfaction prerequisites between courses.
Classes
Sections of each offered course with capacity and status.
Classes Management
One place to run a class: info, teachers, students, attendance, exams and result visibility.
Class Info
Class description and teacher assignment used by score entry and portfolios.
Time Tables
Weekly schedule per class with day, start and end time, teacher and room.
Class Sessions
Dated lecture and lab sessions with files for students.
Exam Schedules
Midterm and final exam dates and times per class.
Semester Timeline
Published timeline of semester events for staff and students.
Group Classes & Group Class Departments
Shared sections that combine students from several departments.
Parallel Courses
Courses a student is allowed to take in parallel with another course.
Project Criteria
Evaluation criteria for graduation projects per department.
Registration Governance
Registration windows, approvals, waitlists and exceptions.
In the system
Chapter 06
Admissions
Applicants apply online through a secure public link; admissions staff review the case, verify documents and accept the applicant as a student.
- Public Application Link
- Apply Form
- Apply Cases
- Case Attempts
- Case Numbers
- Course Details
- Ministry Exams
- Student Data Entry
The admissions office generates a public application link for its tenant. The public form is protected by a signed security challenge and rate limiting, and creates an applicant account with limited 'apply case' access. Staff then work the application case: personal data, qualifications, preferences, attempts, case numbers and course details. On acceptance the applicant becomes a student with a student code, a stage record, a portal account and, where configured, assessed tuition.
Ministry (national) exam results can be recorded per applicant, by scientific or literary branch, and used in ranking. Student Data Entry and Bulk Import support offices that register many students at once from Excel.
How it works
Key capabilities
Public Application Link
Generate or regenerate the tenant's online application link.
Apply Form
Staff-side registration form for a new applicant or student.
Apply Cases
Application cases with status, verification, preferences and acceptance.
Case Attempts
Each submission or re-submission of an application.
Case Numbers
Pre-issued case numbers for applicants.
Course Details
Requested department and course details per case.
Ministry Exams
National exam subjects and marks per applicant.
Student Data Entry
Multi-step data entry for personal, academic and document information.
Bulk Import
Excel import of students with validation before saving.
In the system
Chapter 07
Student records and lifecycle
Every student has one master record and a history of stages. All academic, financial and service events attach to that record.
- Students
- Student Stages
- Semester Status
- Student Classes
- Transfers
- Student Leaves
- Student Results
- Qualifications
The student master record holds personal data (names, mother's name, gender, date of birth, nationality, IDs and passport), contact details, photo, documents and medical notes. Each academic year or semester creates a stage record with the department, presented department, stage, system, status, GPA, total credits and portal access. Transfers, leaves, withdrawals and reactivations change the stage history in a controlled way, and each action is permission-checked.
Supporting records cover qualifications, other information, work experience, educational references, language qualifications, activities, certificates, research and theses, punishments, academic warnings, scholarships and academic advising. Staff can create or reset a student's login account and generate a university e-mail address from a configurable pattern.
How it works
Key capabilities
Students
Searchable student directory with advanced filters and row actions.
Student Stages
Stage history per student with status, GPA and credits.
Semester Status
Active, postponed, failed and other semester statuses.
Student Classes
Courses a student is registered in.
Transfers
Transfers between departments or institutions with decision workflow.
Student Leaves
Leaves of absence with dates and reasons.
Student Results
Results per course and semester.
Qualifications
Previous school and university qualifications.
Other Information
Additional personal and family information.
Work Experience
Employment history (mainly for postgraduate students).
Educational References
Referees and recommendation letters.
Language Qualifications
Language test results such as IELTS or TOEFL.
Academic Advising
Advisor assignments, advising sessions and records.
Withdrawals, reactivations, medicals, punishments, warnings, activities, certificates, research and theses
Dedicated record types, each with its own permissions and audit trail.
In the system
Chapter 08
Teaching operations and attendance
Teachers record attendance and manage their classes; the system calculates absence percentages and applies attendance-failure rules.
- Attendance Entry
- Teacher Attendance – Full Time
- Teacher Attendance – Part Time
- Teacher Attendance Group
- Withdraw Student
- Student Option Requests
- Choose Credits
Class attendance is taken per session and student. Absence percentages are calculated per course, official (excused) absences are recognised, and students who exceed the limit can be flagged as failed by attendance. Teacher attendance is tracked separately for full-time and part-time staff and grouped by month for finalisation.
During the semester students can submit option requests, choose credits (in the Coursat and Bologna systems) and be withdrawn from a course by their teacher or by administration.
Key capabilities
Attendance Entry
Per-session attendance for a class.
Teacher Attendance – Full Time
Daily attendance of full-time teaching staff.
Teacher Attendance – Part Time
Hours of part-time teaching staff.
Teacher Attendance Group
Monthly groups that are finalised for reporting.
Withdraw Student
Withdraw a student from a course by teacher or by previous decision.
Student Option Requests
Requests submitted by students for review.
Choose Credits
Course selection within credit limits, from staff side or portal.
In the system
Chapter 09
Examinations and results
Marks flow from teachers to the exam committee through a controlled workflow, and results are published to students only when the institution decides.
- Exam Types
- Exam Sessions
- Exam Result Entry
- Class Score Entry
- Midterms
- Change Status
- Complaints
- Assignments & Assignment Files
Exam types define the weight of each assessment (for example midterm 30%, coursework 20%, final 50%). Teachers enter midterm, practical, theory and final marks per class; field-level access decides which role may edit which mark. When a class is complete it is finalised, and the department can then be finalised as a whole. The exam committee can apply status changes and curves, record attendance or cheating failures, missed exams and granted grades.
Result visibility is controlled per class and per exam session, so students see midterm or final results only after release. Students can file complaints (appeals) that are tracked to a decision. Re-sit attempts (second, third and fourth attempt), reforming requests and score matching for transferred students are supported. Assignments with file submissions are graded online.
How it works
Key capabilities
Exam Types
Assessment components and their weights.
Exam Sessions
Examination periods per year and semester with visibility.
Exam Result Entry
Assignment, midterm and final results management.
Class Score Entry
Mark entry for a whole class with automatic totals.
Midterms
Midterm exams and their results.
Change Status
Status changes and curves after results are loaded.
Complaints
Grade appeals with status and review.
Assignments & Assignment Files
Coursework with file submission and grading.
Examination Results
Consolidated assignment, midterm and final results.
Results Showing
Controls which results are visible to students.
Workflow Settings
Approval steps and role field access for score entry.
Reforming & Matching Scores
Re-sit requests and score matching for transferred students.
In the system
Chapter 10
Tuition and student finance
Fees are defined per department, stage and system; each student's charges, discounts and payments are kept in a running student account that posts automatically to Accounting.
- Department Tuition Fee
- Tuition Fees (Student Accounts)
- Installments
- Installment Templates
- Batch Payment
- Discount Types
- Subsidy Settings
- Other Revenue
The finance office sets department tuition fees by academic year, stage and entrance type, in the tenant's base currency or another currency. Installment schedules and templates split the fee into due dates. When a student is registered, the system assesses the tuition and records the receivable. Discounts, subsidies, scholarships and other revenue (for example registration or library fees) adjust the balance, and payments of type Receive, Discount, Return, Credit or Debit settle it.
Each student stage has an accounting summary with total fee, paid, discount and remaining balance. A portal financial lock can stop students with unpaid balances from choosing courses or seeing results, and staff can open the portal manually when needed. Every posting creates a journal entry in the Accounting module, using the posting rules configured there.
How it works
Key capabilities
Department Tuition Fee
Fee per department, year, stage and entrance type.
Tuition Fees (Student Accounts)
Fee, paid, discount and balance for each student.
Installments
Due dates and amounts, with paid, pending and overdue counts.
Installment Templates
Reusable installment plans.
Batch Payment
Record payments for one or many students; each creates a receipt number and journal entry.
Discount Types
Institutional discount and subsidy types.
Subsidy Settings
Subsidy rules by entrance type.
Other Revenue
Non-tuition charges such as registration and library fees.
Department / Student Credits
Credit-based fees for the Coursat and Bologna systems.
Student Accounting
The account statement and summary of a student's stage.
In the system
Chapter 11
Student services, dormitory and library
Non-academic services are handled in the same system, so clearance and graduation can check every office at once.
- Hostel Management, Hostels, Rooms, Student Rooms
- Student Clearance
- Student Graduation
- Unanimous Requests
- Send Notification & Outbox
- Library
- My Library
Dormitory management covers hostels, rooms, capacity and room assignments. Student clearance collects sign-off from departments before graduation or withdrawal, and Student Graduation records graduation details and certificates. Unanimous requests let students order official documents, choosing the items, language and delivery method. Student ID cards are produced with a validity period.
The library sub-module manages libraries, categories and books, lending and returns, borrowing periods, lending limits and fining systems, fines and collected fines, a book-list report and a personal 'My Library' view for students and staff.
Key capabilities
Hostel Management, Hostels, Rooms, Student Rooms
Dormitory buildings, rooms and occupancy.
Student Clearance
Multi-office clearance before graduation or withdrawal.
Student Graduation
Graduation records, orders and certificates.
Unanimous Requests
Student requests for official documents, with the items requested, language and delivery option, tracked to completion.
Send Notification & Outbox
Send messages to students and staff and track delivery.
Library
Books, lending, returns, fines, settings and reports.
My Library
A personal view of borrowed books and due dates.
In the system
Chapter 12
Quality assurance and evaluation
Quality work and course evaluation are built in, so evidence for accreditation is collected as part of daily operations.
- QA Activities, Events, Applies, Information, Attachments
- QA QR Generator
- QA Categories & Assessments
- Portfolios, Publications, CAD Results, Teacher Portfolio
- QA Success Management
- Class Evaluation (Student & Admin)
- Teacher Feedback
The QA area tracks QA activities, events, applications, information, attachments and QR codes for evidence collection, organised by categories and assessments. Portfolios, publications, CAD results and teacher portfolios support academic staff evaluation, and the success management page tracks student success indicators.
Students evaluate their classes through structured questionnaires; administrators see completion rates, average ratings by class and department, and teacher feedback reports. The separate Student Service QA and Accreditation modules read university data for service quality reviews and accreditation self-studies.
Key capabilities
QA Activities, Events, Applies, Information, Attachments
Collection of quality-assurance evidence.
QA QR Generator
QR codes that link to QA forms and evidence.
QA Categories & Assessments
Structure of QA areas and assessment items.
Portfolios, Publications, CAD Results, Teacher Portfolio
Academic staff portfolios and performance evidence.
QA Success Management
Student success indicators and follow-up.
Class Evaluation (Student & Admin)
Course evaluation questionnaires and their analysis.
Teacher Feedback
Feedback history and ratings per teacher.
In the system
Chapter 13
Reports and analytics
More than forty reports cover academic, financial, administrative and regulatory needs, and a custom report builder lets users design their own.
- Custom Report Builder
- Master Sheet
- Advanced Reports
Reports respect the same scope rules as the screens, so a dean sees faculty figures and a head of department sees department figures. Most reports can be filtered by year, semester, faculty, department, stage and system, and exported. Dashboards summarise students, teachers, payments, transfers and hostel occupancy, and manager insights highlight items that need attention. The AI module can also prepare advising plans, exam board reviews and tuition collection plans from the same data.
Key capabilities
Custom Report Builder
Pick fields and joins, filter, group, save, share and run reports; run history is kept.
Master Sheet
The full mark sheet of a department and stage.
Advanced Reports
Revenue summary and cross-module analysis.
Academic
- Class reports
- Master sheet
- All scores list
- Student score sheet
- STA report
- Not finalised classes
- Top ten (exam committee)
- Alleviation
- Attendance fail
- Cheat fail
- Missed exam
- Curve
- Annual report
- Assessment quality
- Exam operations
- Course capacity
- Degree audit
Students
- Student reports
- Student semester biography
- Student record
- Student cards
- Graduation & certificates
- Retention & progression
- Academic risk
- Admissions funnel
- Alumni tracking
- Attendance summary
- Student feedback
Finance
- Financial (payments) reports
- Student finance aging
- Revenue summary
Institution
- Teacher reports
- Dormitory reports
- Performance & analytics
- Administrative reports
- Advanced reports
- Regulatory enrollment
- Custom report builder
In the system
Chapter 14
Student portal and mobile app
Students serve themselves: profile, classes, results, payments, absences, assignments and course selection, on the web or in the Hevra mobile app.
- My Portal
- My Classes
- Results
- Payment
- Absence
- Assignments & Modules
- Student Info
- External Account
The portal home shows the student's current stage, notifications and quick links. My Classes lists registered courses with sessions, files and coursework; Results shows published marks; Payment shows the account statement; Absence shows attendance percentages including official absences; Assignments & Modules lets students submit work. Choose Credits is available in credit-based systems during the registration window. External Account shows the student's university e-mail account details.
Access is self-only: a student can never read another student's data. If the institution enables the financial lock, the portal shows which pages are locked and why. The same portal runs inside the Hevra iOS and Android app (built with Capacitor), and push notifications reach the phone through Firebase Cloud Messaging.
Key capabilities
My Portal
Portal home and shortcuts.
My Classes
Registered courses, sessions, files and coursework.
Results
Published marks and grades.
Payment
Account statement and installments.
Absence
Attendance and absence percentages.
Assignments & Modules
Assignment submission and module material.
Student Info
Personal profile.
External Account
University e-mail account information.
In the system
Chapter 15
Interfaces with other modules and third-party services
The University module is connected to the rest of Hevra ERP through defined contracts, and to outside services through configurable connectors.
Other modules use the University module only through its public contract (publicApi), which exposes services such as the examination engine, student lifecycle, ministry exams, qualifications and the student login identity. In the other direction, the University module calls shared platform services for accounting, notifications, file storage, audit and workflow events. External services are configured per tenant or per environment, and every outbound call is designed to fail safely without blocking the user's work.
How it works
Interfaces with other Hevra modules
Accounting
From UniversityTuition assessments, other revenue charges, discounts and payments post journal entries using the tenant's posting rules: general cash, student tuition receivable, deferred revenue, tuition revenue and tuition discount expense. Payments are refused until the required posting accounts are set, and backdated entries follow the accounting settings.
Human Resources
Into UniversityA teacher record can be linked to an HR employee, so staff data is kept once; one employee can be linked to only one teacher.
System / Notifications
From UniversityIn-app notifications to students, teachers and administrators; the portal reads notifications through the System module's contract.
Core (public routes)
Both waysThe public student application form, its security challenge and the application link are served by the Core module, which creates applicant accounts through the University contract.
AI
From UniversityUniversity events (student record created, updated or deleted, profile updated, student accounting synced, portal opened manually) are published to the ERP event stream. The AI assistant can prepare advising plans, registration exception reviews, exam board reviews, tuition collection plans, graduation eligibility reviews and student follow-ups.
UniQA
Both waysQuality-assurance activities are checked against the university organisational scope and permissions.
Student Service QA
Into UniversityReads students and student activities to measure service quality.
Accreditation
Into UniversityUses university structure and evidence for institutional accreditation work.
Sales / Clients
Both waysUniversity clients are stored in the shared ERP client register, so sponsors and paying parties can be invoiced and reported on like any other client.
Billing
From UniversityThe University module is a billable module in the platform's pay-as-you-go billing catalogue.
Identity & RBAC
Both waysStudent, teacher and applicant logins, permission profiles (Apply Case Access, Student Portal Access) and role synchronisation use the platform's single RBAC system.
Third-party services
Firebase Cloud Messaging
ActivePush notifications to the student mobile app.
How it is configured Per tenant: a Firebase service-account JSON (project id, client e-mail, private key) is entered in University settings and push is switched on; invalid device tokens are cleaned up automatically.
Twilio SMS
ActiveText messages for important student and staff events.
How it is configured Twilio account credentials at platform level; failures are logged and do not block the transaction.
SMTP e-mail
ActiveE-mail notifications with a branded template.
How it is configured SMTP settings at platform or tenant level, with tenant e-mail policy; sending pauses automatically after authentication failures.
Amazon S3 storage
ActiveStudent documents, photos, assignment files and session files.
How it is configured CLOUD_STORAGE_PROVIDER=s3 with a bucket; otherwise files are kept on the server's upload storage. Uploads are type- and size-validated.
Microsoft Excel (XLSX)
ActiveBulk setup, student import, class enrollment import, data exports and report downloads.
How it is configured Built in; templates are downloaded from the relevant screen.
Redis
ActiveCaching of reads and authorisation context for speed.
How it is configured Platform configuration.
Mobile app (iOS / Android)
ActiveThe portal and staff screens on phones.
How it is configured Hevra app built with Capacitor; uses push notifications through Firebase.
University e-mail accounts
ActiveGenerates each student's institutional e-mail address from a pattern (department, faculty, year codes).
How it is configured E-mail format setting in University settings; the mailbox itself is created in the institution's mail system.
Moodle LMS
PlaceholderCreation of LMS accounts for students.
How it is configured An endpoint exists but is not connected yet; it returns 'not configured'.
Chapter 16
Roles and permissions
Ready-made roles cover the usual university offices; each can be adjusted with the 294 granular permissions.
Roles are created per tenant during university provisioning and kept in sync with the module's permission catalogue. Permissions are split by page and action (view, create, update, delete and special actions such as finalise, reset password or upload photo), so access can be granted precisely.
University Admin
Full university administration, including settings and all offices.
Registrar
Admissions, student records, stages, transfers and documents.
Dean
Faculty-wide view of students, classes, results and reports.
Head of Department (HOD)
Department classes, teachers, enrollment and results.
Teacher
Own classes only: attendance, marks, assignments and sessions.
Exam Committee
Score workflow, finalisation, status changes, curves and complaints.
Finance Officer / Cashier
Fees, installments, discounts and payments.
Dormitory Officer
Hostels, rooms and room assignments.
Librarian
Books, lending, returns and fines.
Student
Self-service portal for own data only.
- attendance
- core & settings
- courses & class management (85)
- curriculum
- dashboard
- dormitory
- evaluation
- examinations & student scores (46)
- financial
- library
- logs
- portal
- QA
- reforming
- reports
- scheduling
- services
- student accounts & photos
- students & advising
- teachers
- unanimous requests
- users & admissions
Chapter 17
Data model
About 150 tables hold university data, all stored per tenant and accessed through Prisma.
Structure
Faculties, Departments, Years, Academic Semesters, Shifts, Org Units, Settings, Constants, Grading Systems
Curriculum
Subjects, Department Subjects, Presented Departments, Presented Subjects, Prerequisites, Parallel Courses, Learning Outcomes
Classes
Classes, Class Info, Class Info Teachers, Time Tables, Sessions, Exam Schedules, Group Classes, Student Class enrollments
Students
Students, Student Stages, Stage History, Semester Status, Transfers, Leaves, Withdrawals, Reactivations, Documents, Qualifications
Assessment
Exam Types, Examinations, Student Scores, Final Scores, Midterms, Assignments, Complaints, Exam Status Changes
Finance
Department Tuition Fees, Installments, Payments, Payment Allocations, Student Charges, Discounts, Subsidies, Scholarships, Credits
Services
Hostels, Rooms, Student Rooms, Libraries, Books, Book Loans, Clearances, Graduations, Unanimous Requests
Quality & reporting
Class Evaluations, Outcome Assessments, Custom Reports, Report Runs, Degree Audit Rules and Results
Chapter 18
Implementation and onboarding
A new institution can be live quickly: provision the tenant, load the structure, import students and verify with the built-in checks.
- 01
Provision
Run the university bootstrap for the tenant. It enables the module, creates the role catalogue and the University Admin, sets scope policies, creates the first academic year and semesters, and checks upload storage.
- 02
Configure accounting
Set the chart of accounts and the university posting rules in Accounting so tuition and payments can post.
- 03
Load the structure
Fill the Excel setup workbook (faculties, departments, teachers, subjects, classes, timetables, fees, installments) and import it, or enter records screen by screen.
- 04
Admit students
Open the public application link, or import existing students from Excel and create their portal accounts.
- 05
Verify
Use the Test Wizard and Complete Test to confirm every dependency, then run role smoke tests for Registrar, Cashier, Teacher, HOD, Student and Dean.
- 06
Connect services
Enter SMTP, SMS and Firebase details, choose file storage, and set the student e-mail format.
Appendix
Screen atlas
Every screen of the University module as captured from the running system: 180 screens.
One system for the whole university
Admissions, academics, examinations, finance, services, quality and reporting, connected to the rest of Hevra ERP.
Hevra ERP · University Management · Edition 1.0 · November 2026








