Browse the manual
Overview
Manual/Roles
Guide by role

Super administrator guide

How the super administrator manages schools, maintainers, features and themes.

A role-specific guide: everything this kind of ApexityEdu user can see and do.

The super administrator (also called a maintainer) runs ApexityEdu itself, across all schools. You sign in on the /superadmin page — not through a school login.

First-time setup

On a fresh install, the setup wizard:

  1. Creates the control-plane structure (schools, maintainers, features and so on).
  2. Creates the first maintainer account.

After that, you create schools and manage them from the superadmin console.

Schools

Open Schools to:

  • Create a school — give it a name and a short code (used in the login URL, /login/CODE), and provide its own database connection details.
  • Edit school details, including the school’s logo.
  • Activate / deactivate schools.
  • View a school’s status and statistics.

One database per school

Each school runs against its own database, so a school’s data is fully isolated from every other school’s.

Maintainers

Open Maintainers to manage the people who can sign in to the superadmin console: add maintainers, edit them, and remove access.

Features

Open Features to control which modules each school can use. Feature flags include attendance, fees, homework, quizzes, exams, library, notices, feedback, SMS, health cards, syllabus, admissions, inventory, routines, biometric devices, payments, guardian portal and leave management.

  • Enabling a feature makes its tab appear in that school.
  • Disabling a feature hides the tab entirely for everyone in the school.

Themes

Open Themes to customise how each school’s app looks. Each school has two slots — a light and a dark theme file:

  1. Choose the school.
  2. Upload (or paste) the CSS for light and/or dark mode.
  3. Save — the change is live immediately for that school’s app and login page.

See the theming section of Settings for what a theme file can change.

Migrations / updates

Open Migrations to apply schema updates to schools:

  • Apply migrations to a single school.
  • Apply migrations to ALL schools in one click — this iterates every active school and brings it up to date.

Users and credentials

  • Users — view and manage users across schools.
  • Credentials — manage connection details for schools and gateways.

Audit logs

Open Audit logs (if available) to review activity across the platform — useful for answering “who changed what, and when”.

Statistics / overview

The Stats / Overview tabs summarise activity across all schools.

Order of operations

For a new school: (1) create the school in , (2) apply migrations via , (3) enable the features it needs in , (4) optionally upload a theme in . Then the school administrator signs in at and configures the rest.