GSMS is a complete school management system built for all types of schools. Handle districts/circuits/groups, schools, classrooms, assessments, report cards, attendance, fees, and communications all in one place.
Modern, intuitive interface for school administrators
Manage districts/circuits/groups, schools, and classrooms with clear permission boundaries for each level.
Classes, sections, courses, continuous assessment, exam scoring, and automatic report card generation.
Real-time dashboards, attendance monitoring, behavior tracking, and comprehensive reporting tools.
Integrated email (Brevo) and SMS (SMShub) messaging system with credit management and logging.
School fees collection, disbursements, payment tracking, and financial reconciliation tools.
Role-based access control, audit logging, data encryption, and compliance with international standards.
Join institutions using GSMS for efficient, modern school administration.
GSMS gives every user a role. Each role only sees the sections its permissions unlock, and they're ordered to match how the system is actually set up - earlier sections are prerequisites for later ones (you need a Group before a School, a School before Classes, Classes before enrolling Students, and so on). Click a role to open its full walkthrough.
Manages Districts and District-tier accounts only - it does not see or act on any Circuit, School, or lower-tier record. Every Circuit/School/staff decision belongs to the District tier and below.
Districts / Circuits - Administration → Districts (superadmin) or Circuits (District Administrator/IT)
Start here. Every School sits under a Circuit, and every Circuit sits under a District - this two-tier structure is the top-level container everything else belongs to.
Schools - Administration → Schools
Requires a Circuit to already exist — every School belongs to one.
You can browse the schools in your scope, but creating or editing one is reserved for higher administration roles.
Users - Administration → Users
Requires a School (and, for students, a Class to enroll into). Staff accounts are typically set up early; Student and Parent accounts once Classes exist so students can be enrolled.
Parent / Guardian Links - Administration → Parent Links
Requires both the Parent and Student user accounts to already exist under Users. Without this link, a Parent's portal shows "0 Children Linked" and the linked Student data (attendance, report cards, fees, etc.) is invisible to them — this is normally done right after a Parent account is created.
Audit Logs - Administration → Audit Logs
Runs a District: creates and manages its Circuits and Circuit-tier staff (Circuit Administrator/IT/Accountant), with full Finance across every school under the District. Cannot create a School or a Teacher/Parent/Student directly - that belongs to the Circuit and School tiers below.
Districts / Circuits - Administration → Districts (superadmin) or Circuits (District Administrator/IT)
Start here. Every School sits under a Circuit, and every Circuit sits under a District - this two-tier structure is the top-level container everything else belongs to.
Class Types - Administration → Class Types
District Administrator/IT only. Every School under this District shares the same list (e.g. Primary, JHS, SHS) - a Class picks one, which then determines its Grading Categories and Grading Scale.
Grading Categories - Administration → Grading Categories
Requires a Class Type to already exist. Replaces a single fixed CAT1/CAT2/CAT3/Project scheme with categories your District defines per Class Type.
Grading Scale - Administration → Grading Scale
Requires a Class Type to already exist. One scale per (District, Class Type) - a JHS class commonly needs a different scale (BECE 1-9) from an SHS class (WASSCE A1-F9).
Schools - Administration → Schools
Requires a Circuit to already exist — every School belongs to one.
You can browse the schools in your scope, but creating or editing one is reserved for higher administration roles.
Users - Administration → Users
Requires a School (and, for students, a Class to enroll into). Staff accounts are typically set up early; Student and Parent accounts once Classes exist so students can be enrolled.
Parent / Guardian Links - Administration → Parent Links
Requires both the Parent and Student user accounts to already exist under Users. Without this link, a Parent's portal shows "0 Children Linked" and the linked Student data (attendance, report cards, fees, etc.) is invisible to them — this is normally done right after a Parent account is created.
Bulk Uploads - Administration → Bulk Uploads
An alternative to creating Schools or Users one at a time — useful during initial setup or enrollment season.
Audit Logs - Administration → Audit Logs
Academic Years - Academics → Academic Years
Requires a School to exist. This is School Administrator (or School IT) work — a Circuit Administrator sets up the School and its School Administrator account, then the School Administrator creates the Academic Year themselves. Set this up before creating Terms, Classes, Assessments, or Score Windows — they all belong to an Academic Year.
Calendar - Academics → Calendar
Requires an Academic Year to already exist. Set this up before creating Classes, Assessments, or Score Windows — they all belong to a Term.
Classes - Academics → Classes
Requires a School to exist, and is normally set up before Students are enrolled or Courses tied to a specific class are created. Class Type (a separate field from the free-text Level) determines which Grading Categories and Grading Scale apply - a Class with none assigned can't have classwork assessments created for it until your District sets one up.
You can browse the class list, but creating or editing one is reserved for staff with academic-management access.
Courses - Academics → Courses
A Course can optionally be tied to a specific Class, which needs to already exist first if so.
You can browse the course list, but creating or editing one is reserved for staff with academic-management access.
Enrollments - Academics → Enrollments
Requires the Class (and, if used, Section) to already exist and the Student's user account to already be created. A student with no enrollment has no data anywhere — Attendance, Assessments, Report Cards, and the Student/Parent portal all depend on this being set up first.
You can browse the enrollment list, but creating or editing one is reserved for staff with academic-management access.
Score Windows - Academics → Score Windows
Requires a Term to exist. Set this up before Teachers try to score Assessments — scoring is blocked outside an open window.
Assessments - Academics → Assessments
Requires a Class, Section, Course and Term to already exist, and the Teacher must already be assigned to the Course under Teacher Assignments — assessment creation is rejected otherwise.
You can browse each course's score grid, its class/teacher/term and how many categories are scored so far — creating grids and entering scores are reserved for School Administrators and Teachers.
Report Cards - Academics → Report Cards
Requires scored Assessments to exist for the enrollment.
You can open a report to review its Overall Percentage, Grade and Course Breakdown, and use Export PDF — publishing is reserved for School Administrators.
Report Design - Academics → Report Design
One design applies to every School under every Circuit under a District — only the template marked "default" is actually used.
Course Content - Academics → Content
Requires a Course to exist.
You can browse published Syllabus, Module, Video and Resource items — uploading is reserved for staff with content-management access.
Messages - Communications → Messages
Notification Settings - Communications → Notification Settings
Requires a School to exist. Separate from Messages' communication.manage permission - a Teacher can send an ad-hoc message but cannot touch these automatic triggers or spend SMS credits.
SMS Credits - Administration → Schools → (a school's) SMS Credits
Reached from a specific school's row on the Schools list, not a standalone sidebar link - credits are purchased for and belong to one school, not shared across the Circuit. Actually sending SMS also requires a superadmin to have set the District's SMSHub API key (Administration → Districts → Edit).
Collections & Disbursements - Finance
Requires a School to exist.
Student Fees - Finance → Student Fees
Requires a Student (enrolled User) to exist.
Same Circuit/user scope as a District Administrator, but Finance is view-only.
Districts / Circuits - Administration → Districts (superadmin) or Circuits (District Administrator/IT)
Start here. Every School sits under a Circuit, and every Circuit sits under a District - this two-tier structure is the top-level container everything else belongs to.
Class Types - Administration → Class Types
District Administrator/IT only. Every School under this District shares the same list (e.g. Primary, JHS, SHS) - a Class picks one, which then determines its Grading Categories and Grading Scale.
Grading Categories - Administration → Grading Categories
Requires a Class Type to already exist. Replaces a single fixed CAT1/CAT2/CAT3/Project scheme with categories your District defines per Class Type.
Grading Scale - Administration → Grading Scale
Requires a Class Type to already exist. One scale per (District, Class Type) - a JHS class commonly needs a different scale (BECE 1-9) from an SHS class (WASSCE A1-F9).
Schools - Administration → Schools
Requires a Circuit to already exist — every School belongs to one.
You can browse the schools in your scope, but creating or editing one is reserved for higher administration roles.
Users - Administration → Users
Requires a School (and, for students, a Class to enroll into). Staff accounts are typically set up early; Student and Parent accounts once Classes exist so students can be enrolled.
Parent / Guardian Links - Administration → Parent Links
Requires both the Parent and Student user accounts to already exist under Users. Without this link, a Parent's portal shows "0 Children Linked" and the linked Student data (attendance, report cards, fees, etc.) is invisible to them — this is normally done right after a Parent account is created.
Bulk Uploads - Administration → Bulk Uploads
An alternative to creating Schools or Users one at a time — useful during initial setup or enrollment season.
Report Design - Academics → Report Design
One design applies to every School under every Circuit under a District — only the template marked "default" is actually used.
Messages - Communications → Messages
Notification Settings - Communications → Notification Settings
Requires a School to exist. Separate from Messages' communication.manage permission - a Teacher can send an ad-hoc message but cannot touch these automatic triggers or spend SMS credits.
SMS Credits - Administration → Schools → (a school's) SMS Credits
Reached from a specific school's row on the Schools list, not a standalone sidebar link - credits are purchased for and belong to one school, not shared across the Circuit. Actually sending SMS also requires a superadmin to have set the District's SMSHub API key (Administration → Districts → Edit).
Runs the org structure for a Circuit (a group of schools under a District) - schools, staff accounts, and audit oversight, with full Finance across the Circuit. No Students section - attendance, behaviour, trips and clubs are managed at the school level. Academics and Course Content are view-only for oversight; hands-on management of those belongs to School Administrators and Teachers.
Districts / Circuits - Administration → Districts (superadmin) or Circuits (District Administrator/IT)
Start here. Every School sits under a Circuit, and every Circuit sits under a District - this two-tier structure is the top-level container everything else belongs to.
You can browse the Districts/Circuits in the system, but creating or editing one is reserved for higher administration roles.
Schools - Administration → Schools
Requires a Circuit to already exist — every School belongs to one.
Users - Administration → Users
Requires a School (and, for students, a Class to enroll into). Staff accounts are typically set up early; Student and Parent accounts once Classes exist so students can be enrolled.
Parent / Guardian Links - Administration → Parent Links
Requires both the Parent and Student user accounts to already exist under Users. Without this link, a Parent's portal shows "0 Children Linked" and the linked Student data (attendance, report cards, fees, etc.) is invisible to them — this is normally done right after a Parent account is created.
Bulk Uploads - Administration → Bulk Uploads
An alternative to creating Schools or Users one at a time — useful during initial setup or enrollment season.
Audit Logs - Administration → Audit Logs
Classes - Academics → Classes
Requires a School to exist, and is normally set up before Students are enrolled or Courses tied to a specific class are created. Class Type (a separate field from the free-text Level) determines which Grading Categories and Grading Scale apply - a Class with none assigned can't have classwork assessments created for it until your District sets one up.
You can browse the class list, but creating or editing one is reserved for staff with academic-management access.
Courses - Academics → Courses
A Course can optionally be tied to a specific Class, which needs to already exist first if so.
You can browse the course list, but creating or editing one is reserved for staff with academic-management access.
Enrollments - Academics → Enrollments
Requires the Class (and, if used, Section) to already exist and the Student's user account to already be created. A student with no enrollment has no data anywhere — Attendance, Assessments, Report Cards, and the Student/Parent portal all depend on this being set up first.
You can browse the enrollment list, but creating or editing one is reserved for staff with academic-management access.
Assessments - Academics → Assessments
Requires a Class, Section, Course and Term to already exist, and the Teacher must already be assigned to the Course under Teacher Assignments — assessment creation is rejected otherwise.
You can browse each course's score grid, its class/teacher/term and how many categories are scored so far — creating grids and entering scores are reserved for School Administrators and Teachers.
Report Cards - Academics → Report Cards
Requires scored Assessments to exist for the enrollment.
You can open a report to review its Overall Percentage, Grade and Course Breakdown, and use Export PDF — publishing is reserved for School Administrators.
Report Design - Academics → Report Design
One design applies to every School under every Circuit under a District — only the template marked "default" is actually used.
Course Content - Academics → Content
Requires a Course to exist.
You can browse published Syllabus, Module, Video and Resource items — uploading is reserved for staff with content-management access.
Messages - Communications → Messages
Notification Settings - Communications → Notification Settings
Requires a School to exist. Separate from Messages' communication.manage permission - a Teacher can send an ad-hoc message but cannot touch these automatic triggers or spend SMS credits.
SMS Credits - Administration → Schools → (a school's) SMS Credits
Reached from a specific school's row on the Schools list, not a standalone sidebar link - credits are purchased for and belong to one school, not shared across the Circuit. Actually sending SMS also requires a superadmin to have set the District's SMSHub API key (Administration → Districts → Edit).
Collections & Disbursements - Finance
Requires a School to exist.
Student Fees - Finance → Student Fees
Requires a Student (enrolled User) to exist.
Handles account provisioning and bulk operations for a Circuit - Finance is view-only, and Circuits is view-only. Academics and Course Content are view-only for oversight; a Circuit IT officer doesn't create classes, terms, or course content.
Districts / Circuits - Administration → Districts (superadmin) or Circuits (District Administrator/IT)
Start here. Every School sits under a Circuit, and every Circuit sits under a District - this two-tier structure is the top-level container everything else belongs to.
You can browse the Districts/Circuits in the system, but creating or editing one is reserved for higher administration roles.
Schools - Administration → Schools
Requires a Circuit to already exist — every School belongs to one.
Users - Administration → Users
Requires a School (and, for students, a Class to enroll into). Staff accounts are typically set up early; Student and Parent accounts once Classes exist so students can be enrolled.
Parent / Guardian Links - Administration → Parent Links
Requires both the Parent and Student user accounts to already exist under Users. Without this link, a Parent's portal shows "0 Children Linked" and the linked Student data (attendance, report cards, fees, etc.) is invisible to them — this is normally done right after a Parent account is created.
Bulk Uploads - Administration → Bulk Uploads
An alternative to creating Schools or Users one at a time — useful during initial setup or enrollment season.
Classes - Academics → Classes
Requires a School to exist, and is normally set up before Students are enrolled or Courses tied to a specific class are created. Class Type (a separate field from the free-text Level) determines which Grading Categories and Grading Scale apply - a Class with none assigned can't have classwork assessments created for it until your District sets one up.
You can browse the class list, but creating or editing one is reserved for staff with academic-management access.
Courses - Academics → Courses
A Course can optionally be tied to a specific Class, which needs to already exist first if so.
You can browse the course list, but creating or editing one is reserved for staff with academic-management access.
Enrollments - Academics → Enrollments
Requires the Class (and, if used, Section) to already exist and the Student's user account to already be created. A student with no enrollment has no data anywhere — Attendance, Assessments, Report Cards, and the Student/Parent portal all depend on this being set up first.
You can browse the enrollment list, but creating or editing one is reserved for staff with academic-management access.
Assessments - Academics → Assessments
Requires a Class, Section, Course and Term to already exist, and the Teacher must already be assigned to the Course under Teacher Assignments — assessment creation is rejected otherwise.
You can browse each course's score grid, its class/teacher/term and how many categories are scored so far — creating grids and entering scores are reserved for School Administrators and Teachers.
Report Design - Academics → Report Design
One design applies to every School under every Circuit under a District — only the template marked "default" is actually used.
Course Content - Academics → Content
Requires a Course to exist.
You can browse published Syllabus, Module, Video and Resource items — uploading is reserved for staff with content-management access.
Messages - Communications → Messages
Notification Settings - Communications → Notification Settings
Requires a School to exist. Separate from Messages' communication.manage permission - a Teacher can send an ad-hoc message but cannot touch these automatic triggers or spend SMS credits.
SMS Credits - Administration → Schools → (a school's) SMS Credits
Reached from a specific school's row on the Schools list, not a standalone sidebar link - credits are purchased for and belong to one school, not shared across the Circuit. Actually sending SMS also requires a superadmin to have set the District's SMSHub API key (Administration → Districts → Edit).
Collections & Disbursements - Finance
Requires a School to exist.
You can view collection and disbursement totals and history — adding new entries is reserved for finance-management access.
Student Fees - Finance → Student Fees
Requires a Student (enrolled User) to exist.
You can browse student fees and their payment status — assigning a fee or recording a payment is reserved for finance-management access (your School Accountant).
Runs day-to-day operations for a single school. No Groups section; Schools and Users are view-only.
Schools - Administration → Schools
Requires a Circuit to already exist — every School belongs to one.
You can browse the schools in your scope, but creating or editing one is reserved for higher administration roles.
Users - Administration → Users
Requires a School (and, for students, a Class to enroll into). Staff accounts are typically set up early; Student and Parent accounts once Classes exist so students can be enrolled.
Parent / Guardian Links - Administration → Parent Links
Requires both the Parent and Student user accounts to already exist under Users. Without this link, a Parent's portal shows "0 Children Linked" and the linked Student data (attendance, report cards, fees, etc.) is invisible to them — this is normally done right after a Parent account is created.
Bulk Uploads - Administration → Bulk Uploads
An alternative to creating Schools or Users one at a time — useful during initial setup or enrollment season.
Audit Logs - Administration → Audit Logs
Academic Years - Academics → Academic Years
Requires a School to exist. This is School Administrator (or School IT) work — a Circuit Administrator sets up the School and its School Administrator account, then the School Administrator creates the Academic Year themselves. Set this up before creating Terms, Classes, Assessments, or Score Windows — they all belong to an Academic Year.
Calendar - Academics → Calendar
Requires an Academic Year to already exist. Set this up before creating Classes, Assessments, or Score Windows — they all belong to a Term.
Classes - Academics → Classes
Requires a School to exist, and is normally set up before Students are enrolled or Courses tied to a specific class are created. Class Type (a separate field from the free-text Level) determines which Grading Categories and Grading Scale apply - a Class with none assigned can't have classwork assessments created for it until your District sets one up.
Courses - Academics → Courses
A Course can optionally be tied to a specific Class, which needs to already exist first if so.
Enrollments - Academics → Enrollments
Requires the Class (and, if used, Section) to already exist and the Student's user account to already be created. A student with no enrollment has no data anywhere — Attendance, Assessments, Report Cards, and the Student/Parent portal all depend on this being set up first.
Teacher Assignments - Academics → Teacher Assignments
Requires the Course to exist and the Teacher's user account to already be created. A teacher cannot create an Assessment for a course they haven't been assigned to — do this before Assessments are needed.
Score Windows - Academics → Score Windows
Requires a Term to exist. Set this up before Teachers try to score Assessments — scoring is blocked outside an open window.
Assessments - Academics → Assessments
Requires a Class, Section, Course and Term to already exist, and the Teacher must already be assigned to the Course under Teacher Assignments — assessment creation is rejected otherwise.
Report Cards - Academics → Report Cards
Requires scored Assessments to exist for the enrollment.
Report Design - Academics → Report Design
One design applies to every School under every Circuit under a District — only the template marked "default" is actually used.
Course Content - Academics → Content
Requires a Course to exist.
You can browse published Syllabus, Module, Video and Resource items — uploading is reserved for staff with content-management access.
On Report - Students → On Report
Requires students enrolled in a Class.
Clubs - Students → Clubs
Requires a School to exist.
Messages - Communications → Messages
Documents - Communications → Documents
Consent Forms - Communications → Consent Forms
Dinner Menus - Communications → Dinner Menus
Store - Communications → Store
Notification Settings - Communications → Notification Settings
Requires a School to exist. Separate from Messages' communication.manage permission - a Teacher can send an ad-hoc message but cannot touch these automatic triggers or spend SMS credits.
SMS Credits - Administration → Schools → (a school's) SMS Credits
Reached from a specific school's row on the Schools list, not a standalone sidebar link - credits are purchased for and belong to one school, not shared across the Circuit. Actually sending SMS also requires a superadmin to have set the District's SMSHub API key (Administration → Districts → Edit).
Collections & Disbursements - Finance
Requires a School to exist.
Student Fees - Finance → Student Fees
Requires a Student (enrolled User) to exist.
Technical/administrative role for one school - no Finance or Students (attendance/behaviour/trips) access. Manages Classes, Courses, Enrollments, Teacher Assignments, Calendar/Score Windows, and views/exports Report Cards, alongside account and communications management - the same academic structure work as School Administrator, minus creating assessments/entering scores and publishing report cards.
Schools - Administration → Schools
Requires a Circuit to already exist — every School belongs to one.
You can browse the schools in your scope, but creating or editing one is reserved for higher administration roles.
Users - Administration → Users
Requires a School (and, for students, a Class to enroll into). Staff accounts are typically set up early; Student and Parent accounts once Classes exist so students can be enrolled.
Parent / Guardian Links - Administration → Parent Links
Requires both the Parent and Student user accounts to already exist under Users. Without this link, a Parent's portal shows "0 Children Linked" and the linked Student data (attendance, report cards, fees, etc.) is invisible to them — this is normally done right after a Parent account is created.
Academic Years - Academics → Academic Years
Requires a School to exist. This is School Administrator (or School IT) work — a Circuit Administrator sets up the School and its School Administrator account, then the School Administrator creates the Academic Year themselves. Set this up before creating Terms, Classes, Assessments, or Score Windows — they all belong to an Academic Year.
Calendar - Academics → Calendar
Requires an Academic Year to already exist. Set this up before creating Classes, Assessments, or Score Windows — they all belong to a Term.
Classes - Academics → Classes
Requires a School to exist, and is normally set up before Students are enrolled or Courses tied to a specific class are created. Class Type (a separate field from the free-text Level) determines which Grading Categories and Grading Scale apply - a Class with none assigned can't have classwork assessments created for it until your District sets one up.
Courses - Academics → Courses
A Course can optionally be tied to a specific Class, which needs to already exist first if so.
Enrollments - Academics → Enrollments
Requires the Class (and, if used, Section) to already exist and the Student's user account to already be created. A student with no enrollment has no data anywhere — Attendance, Assessments, Report Cards, and the Student/Parent portal all depend on this being set up first.
Teacher Assignments - Academics → Teacher Assignments
Requires the Course to exist and the Teacher's user account to already be created. A teacher cannot create an Assessment for a course they haven't been assigned to — do this before Assessments are needed.
Score Windows - Academics → Score Windows
Requires a Term to exist. Set this up before Teachers try to score Assessments — scoring is blocked outside an open window.
Report Cards - Academics → Report Cards
Requires scored Assessments to exist for the enrollment.
Report Design - Academics → Report Design
One design applies to every School under every Circuit under a District — only the template marked "default" is actually used.
Messages - Communications → Messages
Notification Settings - Communications → Notification Settings
Requires a School to exist. Separate from Messages' communication.manage permission - a Teacher can send an ad-hoc message but cannot touch these automatic triggers or spend SMS credits.
SMS Credits - Administration → Schools → (a school's) SMS Credits
Reached from a specific school's row on the Schools list, not a standalone sidebar link - credits are purchased for and belong to one school, not shared across the Circuit. Actually sending SMS also requires a superadmin to have set the District's SMSHub API key (Administration → Districts → Edit).
Finance-only role - no Academics, Students, Communications or Users access. A Group Accountant also sees Audit Logs; a School Accountant does not.
Collections & Disbursements - Finance
Requires a School to exist.
Student Fees - Finance → Student Fees
Requires a Student (enrolled User) to exist.
Audit Logs - Administration → Audit Logs
Manages the classes/courses assigned to you. No Calendar/Score Windows (an admin controls those), no Trips/Clubs, no Finance, no Administration.
Classes - Academics → Classes
Requires a School to exist, and is normally set up before Students are enrolled or Courses tied to a specific class are created. Class Type (a separate field from the free-text Level) determines which Grading Categories and Grading Scale apply - a Class with none assigned can't have classwork assessments created for it until your District sets one up.
You can browse the class list, but creating or editing one is reserved for staff with academic-management access.
Courses - Academics → Courses
A Course can optionally be tied to a specific Class, which needs to already exist first if so.
You can browse the course list, but creating or editing one is reserved for staff with academic-management access.
Enrollments - Academics → Enrollments
Requires the Class (and, if used, Section) to already exist and the Student's user account to already be created. A student with no enrollment has no data anywhere — Attendance, Assessments, Report Cards, and the Student/Parent portal all depend on this being set up first.
You can browse the enrollment list, but creating or editing one is reserved for staff with academic-management access.
Assessments - Academics → Assessments
Requires a Class, Section, Course and Term to already exist, and the Teacher must already be assigned to the Course under Teacher Assignments — assessment creation is rejected otherwise.
Report Cards - Academics → Report Cards
Requires scored Assessments to exist for the enrollment.
You can open a report to review its Overall Percentage, Grade and Course Breakdown, and use Export PDF — publishing is reserved for School Administrators.
Report Design - Academics → Report Design
One design applies to every School under every Circuit under a District — only the template marked "default" is actually used.
Course Content - Academics → Content
Requires a Course to exist.
Attendance - Students → Attendance
Requires students enrolled in a Class.
Behaviour & Detentions - Students → Behaviour / Detentions
Requires students enrolled in a Class.
On Report - Students → On Report
Requires students enrolled in a Class.
Trips - Students → Trips
Requires students enrolled in a Class.
Messages - Communications → Messages
Read-only access to your own child/children. Everything lives under My Child, plus report cards and content under Academics.
Report Cards - Academics → Report Cards
Requires scored Assessments to exist for the enrollment.
You can open a report to review its Overall Percentage, Grade and Course Breakdown, and use Export PDF — publishing is reserved for School Administrators.
Report Design - Academics → Report Design
One design applies to every School under every Circuit under a District — only the template marked "default" is actually used.
Course Content - Academics → Content
Requires a Course to exist.
You can browse published Syllabus, Module, Video and Resource items — uploading is reserved for staff with content-management access.
My Child - My Child (Portal)
Everything here is read-only and only appears once a School has enrolled your child and linked your account as a guardian.
Same self-service access as a Parent, scoped to your own record - there's no child switcher since it's just you.
Report Cards - Academics → Report Cards
Requires scored Assessments to exist for the enrollment.
You can open a report to review its Overall Percentage, Grade and Course Breakdown, and use Export PDF — publishing is reserved for School Administrators.
Report Design - Academics → Report Design
One design applies to every School under every Circuit under a District — only the template marked "default" is actually used.
Course Content - Academics → Content
Requires a Course to exist.
You can browse published Syllabus, Module, Video and Resource items — uploading is reserved for staff with content-management access.
My Child - My Child (Portal)
Everything here is read-only and only appears once a School has enrolled your child and linked your account as a guardian.
Have a question or need help with GSMS? Reach out to us directly:
Effective date: 28 July 2026
Global School Management System ("GSMS", "the Platform") is owned and operated by Iakrotech ("Iakrotech", "we", "us", "our"). These Terms of Use ("Terms") form a binding agreement between Iakrotech and the group, school, or individual user accessing the Platform ("you", "User"). By creating an account, logging in, or otherwise using GSMS, you accept these Terms in full. If you are accepting on behalf of a school or group, you confirm you have authority to bind that organization.
"Group" means a district or mother-school organization with one or more affiliated schools. "School" means an individual educational institution using the Platform, whether independently or as part of a Group. "Account" means a set of login credentials issued to a User. "Content" means any data, records, or files submitted to the Platform by a School, Group, or User.
Accounts are provisioned by an authorized School or Group administrator, not through public self-registration. You must provide accurate information when requested and promptly notify your administrator of any change that affects your access rights (for example, a change of role or departure from the School). You are responsible for maintaining the confidentiality of your login credentials and for all activity that occurs under your Account, whether or not authorized by you, except to the extent caused by Iakrotech's failure to meet its security obligations under these Terms.
Subject to these Terms, Iakrotech grants each School or Group a limited, non-exclusive, non-transferable, revocable license to access and use GSMS for internal school administration purposes for as long as the applicable subscription or access arrangement remains active. No ownership interest in the Platform, its software, or its underlying technology is transferred to you.
You agree to use GSMS only for legitimate educational administration purposes and agree not to: (a) access or attempt to access data, accounts, or systems you are not authorized to use; (b) upload unlawful, defamatory, or harmful content; (c) reverse engineer, decompile, or attempt to extract the source code of the Platform, except where permitted by law; (d) introduce malware or attempt to disrupt, overload, or compromise the security of the Platform; or (e) use the Platform to send unsolicited bulk communications unrelated to school administration.
Each School and Group is responsible for: (a) determining who receives Accounts and at what permission level; (b) the accuracy of academic, attendance, behaviour, and financial data it enters; (c) obtaining any consents required under applicable law before submitting personal data of students, parents, or staff to the Platform; and (d) promptly deactivating Accounts for users who leave the School or Group.
As between Iakrotech and the School or Group, all Content - including academic records, attendance, behaviour, financial, and communication data - remains the property of the School or Group that submitted it. Iakrotech does not claim ownership of Content and will only process it as necessary to provide, maintain, and support the Platform, or as otherwise described in our Privacy Policy.
The GSMS software, design, branding, and documentation are the property of Iakrotech and its licensors and are protected by applicable intellectual property laws. Nothing in these Terms grants you rights in Iakrotech's trademarks, logos, or brand assets except as necessary to use the Platform as intended.
GSMS integrates with third-party providers to deliver certain features, including email delivery (Brevo) and SMS messaging (SMShub). Use of these features is subject to the acceptable-use requirements of those providers in addition to these Terms. Iakrotech is not responsible for outages or errors originating solely from a third-party provider's systems.
We aim to keep GSMS available and performant, but we do not guarantee uninterrupted or error-free operation. We may suspend access temporarily for maintenance, upgrades, or emergency security reasons, and will make reasonable efforts to minimize disruption and provide advance notice where practical.
We may suspend or terminate an Account or a School/Group's access if we reasonably believe these Terms have been violated, if required by law, or if continued access would pose a security risk to the Platform or other Users. A School or Group may stop using the Platform at any time; certain obligations (including Sections 7, 12, 13, and 14) survive termination.
The Platform is provided "as is" and "as available." To the fullest extent permitted by law, Iakrotech disclaims all warranties, express or implied, including fitness for a particular purpose and non-infringement. We do not warrant that the Platform will be free of defects or that all data processed will be error-free.
To the fullest extent permitted under the laws of the Republic of Ghana, Iakrotech's aggregate liability arising out of or relating to these Terms or use of the Platform shall not exceed the fees paid by the relevant School or Group to Iakrotech in the twelve (12) months preceding the claim, and Iakrotech shall not be liable for indirect, incidental, special, or consequential damages. Nothing in these Terms limits liability that cannot lawfully be limited, including liability for fraud or gross negligence.
You agree to indemnify and hold Iakrotech harmless from claims, damages, and expenses (including reasonable legal fees) arising from your breach of these Terms or your unlawful use of the Platform.
These Terms are governed by the laws of the Republic of Ghana, without regard to conflict-of-law principles. The parties will first attempt to resolve any dispute in good faith through direct negotiation; unresolved disputes shall be subject to the exclusive jurisdiction of the courts of Ghana.
If any provision of these Terms is found unenforceable, the remaining provisions continue in full force. These Terms, together with any applicable subscription or service agreement, constitute the entire agreement between you and Iakrotech regarding use of the Platform.
We may update these Terms from time to time to reflect changes in the Platform or applicable law. Material changes will be notified through the Platform or by email to administrator accounts. Continued use of GSMS after a change takes effect constitutes acceptance of the revised Terms.
Questions about these Terms can be sent to info@iakrotech.com or +233 50 707 9501.
Effective date: 28 July 2026
Global School Management System ("GSMS", "the Platform") is provided by Iakrotech ("Iakrotech", "we", "us", "our"), which acts as a data processor on behalf of the Schools and Groups that use the Platform, and as data controller for limited administrative data described below. For any privacy question, contact us at info@iakrotech.com or +233 50 707 9501.
This Privacy Policy explains how personal data is collected, used, shared, and protected when a School, Group, staff member, parent, or student uses GSMS. Each School or Group remains the data controller for the personal data of its own students, parents, and staff; Iakrotech processes that data on the School's or Group's instructions to provide the Platform.
Depending on your role, GSMS may process:
GSMS is used by schools to administer records belonging to minors. Student accounts and records are created and managed by the School, not directly by the child, and parents/guardians are given their own Account to view their child's records through the Parent Portal. We limit student data collection to what is necessary for academic administration and do not knowingly permit students to submit personal data beyond what their School enters or approves. Schools are responsible for obtaining any parental consent required under applicable law before enrolling a student's data on the Platform.
Personal data is processed on the basis of: (a) performance of the service agreement between Iakrotech and the School or Group; (b) the School's or Group's legitimate interests in administering education services; (c) compliance with legal or regulatory obligations (for example, academic record-keeping); and (d) consent, where a School or Group has obtained it for a specific purpose (such as optional communications).
Information is used to: operate core features (academics, attendance, behaviour, finance, communications, reporting); authenticate users and enforce role-based permissions; send transactional emails and SMS on behalf of a School (for example, report card notifications); maintain audit logs for security and accountability; and diagnose and fix technical issues.
We do not sell personal data. We share data only as follows: with the School or Group that owns the data and its authorized staff (per role-based permissions); with sub-processors engaged to operate the Platform, currently Brevo (transactional email delivery) and SMShub (SMS delivery), each of whom is only given the data needed to send the relevant message; with our hosting provider, which stores data on our behalf; and where required to comply with a legal obligation, court order, or lawful request from a competent authority.
Where a sub-processor stores or processes data outside the country where your School operates, we require that sub-processor to maintain security and confidentiality protections consistent with this Policy and applicable data protection law.
We apply technical and organizational safeguards including role-based access control, encrypted connections (HTTPS/TLS) in transit, password hashing, and audit logging of sensitive actions. No system can be guaranteed 100% secure, but we work to promptly identify and remediate vulnerabilities.
Records are retained for as long as the School's or Group's account remains active, or as required by applicable academic record-keeping or tax/financial regulations. When a School or Group's account is closed, data is deleted or anonymized within a reasonable period, except where retention is required by law.
Subject to applicable data protection law (including Ghana's Data Protection Act, 2012, Act 843, where applicable), you may have the right to: request access to your personal data; request correction of inaccurate data; request erasure or restriction of processing, where applicable; object to certain processing; and lodge a complaint with the relevant data protection authority. Requests should first be directed to your School or Group administrator, who controls your records; you may also contact us directly at info@iakrotech.com and we will route your request appropriately.
GSMS uses a small number of essential cookies, described in our Cookie Policy (see the "Cookies" link in the footer).
We may update this Privacy Policy from time to time. Material changes will be communicated through the Platform or by email to administrator accounts before they take effect.
For privacy questions or to exercise your rights, contact us at info@iakrotech.com or +233 50 707 9501.
Effective date: 28 July 2026
Cookies are small text files placed on your device by a website to store information such as your session state or preferences. This policy is issued by Iakrotech, the operator of Global School Management System ("GSMS").
GSMS only uses strictly necessary and functional cookies:
| Cookie | Purpose | Duration |
|---|---|---|
global_school_management_system_session | Keeps you signed in and links your browser to your authenticated session. | Session / until logout |
XSRF-TOKEN | Cross-Site Request Forgery (CSRF) protection - verifies that requests originate from our own forms. | Session |
remember_web_... | Optional cookie set only if you tick "Remember Me" at login, so you don't need to sign in again on that device. | Up to 5 years or until logout |
GSMS does not use cookies for advertising, profiling, or cross-site tracking, and does not sell or share cookie data with advertisers.
Some pages load fonts and icons from third-party content delivery networks (Google Fonts, jsDelivr). Loading these resources causes your browser to make a direct request to those providers, which may receive your IP address as part of a standard web request, but GSMS does not instruct them to set tracking cookies on our pages.
Because the strictly necessary cookies are required to keep you signed in and to protect your session, disabling them in your browser will prevent you from using the Platform. You can control or delete cookies through your browser settings at any time; consult your browser's help documentation for instructions.
We may update this Cookie Policy if the cookies we use change. Material changes will be reflected here with an updated effective date.
Questions about this Cookie Policy can be sent to info@iakrotech.com or +233 50 707 9501.