All modules & pricing
PremiumStaff portal

School Groups & Districts

Run several schools as one organisation — a shared roll-up of every campus, one set of people who oversee them, and one bill instead of four.

Get startedTalk to us₦7,900.00/mo · on top of your base package

What this module is

An organisation that runs more than one school ends up running more than one of everything: a login per campus, a spreadsheet that adds the numbers up by hand, a separate invoice from every supplier, and a head-office team that finds out what happened at a school when somebody emails them. The schools work; the group does not.

School Groups adds the missing layer. A group is its own record, with its own members, its own view of every campus in it, and its own billing relationship. The schools underneath keep running exactly as they did — same dashboards, same staff, same students — but head office finally has a place to stand where all four of them are visible at once.

It divides into six surfaces: the group list you start from, the overview and analytics that answer "how are we doing", the schools and members rolls that define who and what is in the group, and the billing screen where a group decides what every member school gets by default. Membership carries a role — Owner, Admin or Viewer — and every screen respects it, so read-only oversight is a first-class arrangement rather than a promise not to click anything.

What you get

The whole portfolio on one screen

Total schools, students, staff and members across the group, with each campus’s plan, status and population beside it. No spreadsheet, no monthly data-gathering email.

One billing relationship

The group chooses the module set every member school inherits, sees the monthly position per campus and the group total, and can push its defaults onto a school in one action.

Head-office access without head-office risk

Owner, Admin and Viewer are real roles with defined powers. A regional director gets the numbers; only an Owner can change billing, suspend or delete the group.

Schools stay schools

Nothing about a campus’s own dashboard changes. A school can even stay on its own subscription inside a group — joining is not an all-or-nothing switch.

Comparison that is actually comparable

Every campus is on the same platform with the same definitions, so a population or plan comparison across sites means something for the first time.

Growth without re-onboarding

A new campus is added to the group and inherits its defaults, rather than being set up from scratch and then reconciled by hand.

Every flow, every role

How School Groups & Districts actually works

Everything below is the real application, running live on this page with sample school data — not screenshots. Each screen is the same one your team would use.

Group operator / Head office

The person who runs the organisation rather than a single school. These screens are the whole job: see the portfolio, define what is in the group, understand how it is performing, decide what every campus gets, and control who else may touch any of it.

1

Start from the portfolio

The workspace opens on the groups this person belongs to — not a list of schools. An operator can hold several: a trust that runs two brands, or a district and a foundation.

Every group with its school count and the role this user holds in it.
Search across groups when an organisation runs more than a handful.
The controls shown depend on the role — a Viewer sees the same list with nothing to press.
Deleting a group is an Owner-only action, and it is confirmed before anything happens.
2

Create the group

A group is a real record, not a tag on some schools: it has a name, a short code, contact details and an address of its own. Whoever creates it becomes its Owner.

Name and short code identify the group across the platform.
Contact email, phone and address belong to head office rather than to any campus.
The creator is written in as Owner in the same transaction — a group is never left without one.
Schools and members are added afterwards, so a group can exist before the campuses are ready.
3

See the whole organisation

The overview answers the four questions a board asks first — how many schools, students, staff and people with access — over a filterable list of every campus.

Live totals across the group, computed from the member schools rather than typed in.
The school table filters by status and plan, so "which campuses are still on trial" is one click.
Each row opens that school, so the group view is a way into a campus rather than a dead end.
4

Define what is in the group

The schools roll is the membership itself. Adding a school here is what makes it part of the organisation; removing it releases it without touching anything inside it.

Add an existing school to the group, or remove one that has left.
Plan, status, student count and staff count per campus, side by side.
Managing schools requires the Owner or Admin role — a Viewer sees the roll and no buttons.
A school belongs to at most one group, so the roll-ups can never double-count.
5

Decide who may see and who may act

Group membership is separate from school access: these are the head-office people, each with a role that says exactly what they can do.

Owner — everything, including billing, suspension and deletion.
Admin — manage settings, schools and members, but not billing or the group’s lifecycle.
Viewer — read the group and its analytics, change nothing.
Only an Owner can appoint or demote another Owner, and the last Owner cannot be demoted.
6

Compare campuses honestly

The analytics screen is the argument for running schools on one platform: because every campus uses the same definitions, the comparison across them is real.

Population per campus — students and staff — as a single chart rather than four reports.
The spread of schools by operating status and by plan.
How head-office access is distributed across Owner, Admin and Viewer.
Filters by school status and plan, so a segment can be isolated without exporting anything.
7

Bill the group, not the schools

This is where a group stops being an organisational chart and starts saving money and time: one subscription, one default module set, one monthly total.

Choose the add-on modules every member school inherits by default.
See each campus’s subscription model, active modules and monthly amount in one table.
Push the group defaults onto an individual school in one action.
A school can remain on its own subscription inside the group — the table shows which are group-managed and which are not.
Billing is Owner-only; an Admin can run the group without being able to change what it spends.
8

Hold the group’s lifecycle

Profile, branding and the three actions that change what a group *is*. They are deliberately fenced behind the Owner role.

Update the group’s name, contact details and address.
Group branding — logo, primary colour and tagline — kept separate from any campus’s own brand.
Suspend and reinstate the group; delete it when an organisation dissolves.
The Settings tab is not even listed for a member whose role cannot manage settings.
9

What a member school sees

The last screen is the other side of the arrangement — the campus’s own Subscription workspace, where group-managed billing is stated plainly rather than silently locking controls.

The school is told its billing is group-managed and which group subscription it belongs to.
Module selection, interval changes and settlement are locked at school level, and the page says so.
A link back into the group workspace, for the people who have access to it.
A school that is not group-managed sees a different message entirely, with no half-disabled controls.

Head-office staff (read-only)

Most people at head office need the numbers and should never be able to change the organisation. Viewer is a real membership role rather than a promise: the same screens load, and every control that would alter something is simply absent.

1

The same workspace, without the controls

A regional director or finance lead opens School Groups and sees the groups they belong to. It is the operator’s screen with the management actions removed, because the API tells the page what this person may do.

Their groups, with school counts and their own role shown as Viewer.
No create, no delete — the capability set that governs those comes back false.
Access is granted by adding them as a group member; it is not a separate product or a second login.
2

Full visibility of the numbers

Read-only does not mean thin. A Viewer gets the same cross-school analytics an Owner does — which is the entire reason to give a board member or an auditor an account.

The same population, status, plan and role charts, computed the same way.
The same filters, so they can answer their own questions without asking head office.
Nothing they can press changes a school, a member or a bill.

How it connects to the rest of the platform

  • Schools come from the platform

    A group is assembled from schools that already exist on EaseAcademia. Nothing is duplicated: the campus keeps its own students, staff, dashboards and settings, and the group reads across them.

  • Roll-ups are computed, not reported

    Student and staff counts on the overview and analytics screens are read from the member schools’ live records, so the group total moves when an admission is processed rather than when someone submits a return.

  • Group branding sits above school brandingrequires Branding & Customization

    A group carries its own logo, colour and tagline. Where Branding & Customization is switched on, each campus still wears its own identity — the group’s brand does not overwrite it.

  • Group billing drives the school’s subscription

    Choosing default modules at group level and applying them to a school changes that school’s own subscription record, which is why its Subscription workspace reports the arrangement instead of pretending nothing happened.

  • Access control is the group’s own

    Group membership is separate from any school’s access profiles: being a school administrator does not grant group access, and holding a group role does not grant access inside a campus.

Common questions

Do our schools have to change how they work?+

No. Each campus keeps its own dashboard, staff, students and settings. The group layer sits above them and reads across; it does not reach into a school and rearrange it.

Can a school be in more than one group?+

No — a school belongs to at most one group. That is deliberate: it is what keeps the group’s totals from double-counting a campus.

Does joining a group mean giving up control of our billing?+

Only if you choose to. A group sets default modules and can apply them to a school, but a member school can remain on its own school-managed subscription; the group billing table shows which campuses are group-managed and which are not.

Who can see our schools’ data?+

Only the people added as members of the group, and only what the group screens show — portfolio-level roll-ups, campus population, plan and status. Group membership does not grant access inside a school’s own dashboard.

Can we give someone read-only access?+

Yes. The Viewer role reads the group and its analytics and can change nothing — not settings, not schools, not members, not billing. It is enforced by the API, not by hiding buttons.

What happens when we add a new campus?+

It is added to the schools roll and can inherit the group’s default module set in one action, so it starts configured like its sibling campuses rather than being set up from scratch.

Is there a discount for running several schools?+

The billing model supports volume discounting by school count, but no volume tiers are configured in the current price list, so the discount shown is zero. Multi-school pricing is a conversation to have with us directly.

Run your whole school on one connected platform

Start with the base package, switch on the modules you need, and give every parent, student and staff member a single place to log in.