There was a problem loading the comments.

Understanding Grado Modules

Support Portal  »  📚 Knowledgebase  »  Viewing Article

  Print

Overview

Grado is a modular school management system, meaning that every major function—such as enrollment, grading, or finance—is handled by a distinct module.

Modules work together seamlessly, sharing data so administrators, faculty, and students always see the most up-to-date information.

Each module can be enabled, disabled, or restricted by permissions, giving institutions flexibility to match Grado’s structure with their internal workflow.


What Is a Module?

A module in Grado is a self-contained feature set that performs a specific function within the system.
Examples include Academic Years, Courses, Students, Assessments, and Payments.

Each module typically contains:

  • Interface pages (lists, forms, and detail views)

  • Actions or functions (e.g., Edit, Approve, Archive)

  • Associated permissions controlling access


Core Grado Modules

Below is a summary of commonly used modules grouped by operational purpose:

 

Functional Area Key Modules Description
Academic Management Academic Years, Courses, Sections, Subjects, Curriculums, Degree Programs Defines academic structure, schedules, and offerings.
Enrollment & Records Students, Enrollments, Advisers, Dropping, Student Status Handles student registration, advising, and enrollment lifecycle.
Grading & Evaluation Grades, Grade Book, Change Grades, Questionnaires, Reports Supports grade input, approval, and reporting.
Finance & Billing Assessments, Payments, Discounts, Scholarships, Refunds, Tuitions Automates fee computation and payment tracking.
Institutional Setup Divisions, Departments, Disciplines, Buildings, Rooms, School Details Defines the organizational and physical structure.
Administration & Configuration Users, Roles & Permissions, Settings, Signatories Controls access, system configuration, and approval hierarchies.
 
 

💡 Note:
The actual list of modules accessible to each user depends on their role and permissions.
Modules can also vary by version or institutional configuration.


Examples of Module Interactions

Grado modules are tightly integrated. Here are a few examples of how they connect:

  • Courses ↔ Grades ↔ Students – Grades entered in the Courses module automatically update student records.

  • Assessments ↔ Payments ↔ Reports – Fee assessments link directly to recorded payments and generate summaries for reporting.

  • Academic Years ↔ Enrollments – Each enrollment is tied to an active academic year and term.

  • Users ↔ Permissions – Determines which modules and actions a user can access.


Benefits of Modular Design

  • Scalability: Enable new features as your institution grows.

  • Security: Limit access by assigning permissions per module.

  • Ease of Maintenance: Updates and bug fixes apply per module without affecting the whole system.

  • Configurability: Schools can tailor Grado to their operational priorities.


How Modules Appear in the Interface

Modules appear as items in the Side Navigation Pane of the Admin and Faculty portals.
When a module is selected, its List View opens—displaying records that can be filtered, searched, or edited based on user permissions.

 

🧩 Tip:
Modules that are disabled or hidden during initial school system setup will not appear in the user’s sidebar, keeping the interface clean and role-specific.


Share via
Did you find this article useful?  

Related Articles


Self-Hosted Help Desk Software by SupportPal