The staff portal

Your self-service and your school work, in one login.

One workspace for every employee — teachers, bursars, nurses, librarians, wardens and admin. It brings together your own self-service (payslips, leave, attendance, messages) and the school modules your role has been granted, so there’s a single place to work no matter what you do.

Built for Teachers, bursars, nurses, librarians, wardens & admin staff

What the staff portal does

The same live data as the rest of the school, surfaced for the person looking at it.

Payslips & leave

Request payslips and employment letters, raise and track leave, and manage your own HR tasks in self-service — no paperwork, no chasing.

Your timetable & attendance

Your personal timetable and schedule, always current and in sync with the school.

Your clinic & messages

Your own clinic records and wellbeing, plus messages and announcements relevant to you — tracked as carefully as students’.

Assigned: your classes

Form and subject teachers open a class to see headcount, today’s attendance and at-risk students — the starting point every morning.

Assigned: gradebook & results

Enter scores, psychomotor reports and comments, then submit results through the school’s approval flow without spreadsheets.

Assigned: your modules

A nurse gets the clinic, a bursar finance, a warden the hostel, a librarian the library — whatever the school grants your role, in the same workspace.

See it end to end

Where a staff account comes from — and what it carries

Everything below is the real application, running live on this page with sample school data — not screenshots. Start where every employee actually starts: being created by the school. Then watch the same login pick up whichever school modules the role was granted, before the self-service every employee shares.

Step 1 · How you get here

The school creates you

There is no staff sign-up. An employee exists because the school created them in its own Staff module — a record in the directory, a department, and a role. Those three screens are the School portal, not the Staff portal, and they decide everything the person will see when they first sign in.

1

Added to the staff directory

The school office creates the employee record — name, job title, contract, start date — and invites them by email. That invitation is the only way a Staff portal login comes into existence.

Create an employee record, or invite a new hire by email.
Capture job title, contract type, campus and start date.
The invited person activates their own Staff portal login.
Part of the base platform — every school has the staff directory.
2

Placed in a department

Departments are the school’s own structure — Sciences, Admissions, Operations, the Library — and every employee sits in one. It is what reporting lines, HR approvals and school-wide staff reporting are grouped by.

Define the departments the school actually runs.
Place each employee in the department they belong to.
Drives supervisor chains, leave approvals and staff reporting.
3

Given a role — and with it, the modules

The role builder is where the school decides what this person can open. A role is assembled from granular, per-module permissions, and the modules it grants are exactly the sections that will appear in that employee’s sidebar. Everything in the next phase follows from this one screen.

Build roles from granular, per-module permissions.
Grant a librarian the library, a nurse the clinic, a teacher their classes.
Assign the role to the employee you just created.
Change a role and every holder’s workspace updates automatically.
Step 2 · Assigned by your role

If the library is yours

Sign in as Tunde Adeyemi, the school librarian. He is a member of staff exactly like everyone else in this walkthrough — the only difference is the module his role was granted. It arrives in his sidebar as a workspace to run, not a service to use, and nothing else in the school does.

1

Work the issue desk

Circulation is the librarian’s day: issue a book to a borrower, take it back, renew it, and see what is overdue — the counter, in the same login that holds his payslips.

Issue, return and renew loans against a borrower and a copy.
See what is out, what is due and what is overdue right now.
Fines and loan limits follow the school’s own library policy.
2

Keep the catalogue

The catalogue is the stock itself — titles, copies, barcodes and shelf locations — maintained by the person who actually handles the books rather than by the school office.

Add titles and register each physical copy with its barcode.
Track a copy’s status: on shelf, on loan, lost or withdrawn.
Everything borrowers search from their own portals reads this.
Step 2 · Assigned by your role

If the clinic is yours

Now Blessing Eze, the school nurse. Same staff login, same self-service underneath — but her role was granted the Health Clinic, so the sidebar carries a clinical workspace and no library. Health data is some of the most sensitive a school holds, and this is the grant that decides who can open it.

1

Log a visit

A student arrives at the clinic; the nurse records the visit, what was done and how it was resolved. The record is written once, and the student’s own portal and their parents see the parts meant for them.

Record visits with presenting complaint, treatment and outcome.
Trigger a parent notification where the school’s policy requires it.
Builds each student’s clinical history rather than a paper day book.
2

Administer medication safely

Medication held at school is logged dose by dose — who authorised it, who gave it and when — so an administration is an auditable record rather than a note in a drawer.

Register medications a student is authorised to receive.
Log each administration with time, dose and administering staff.
A complete audit trail for the medicines the school holds.
Step 2 · Assigned by your role

If the store room is yours

Musa Ibrahim runs stores. The pattern should be obvious by now: one grant, one workspace. Inventory is the least glamorous module in the platform and the one that quietly answers “where did that projector go, and who signed for it?”.

1

Know what the school owns

The asset register is every tracked item the school holds — its tag, its location, its condition and who it is assigned to — so equipment is accounted for rather than remembered.

Register assets with tags, categories, locations and condition.
Assign an item to a person, a room or a department.
Track value and depreciation across the asset’s life.
2

Buy and receive stock

Requests, purchase orders and receipts run through the same module, so what was ordered, what arrived and what it cost stay attached to the item they created.

Raise requests and turn approved ones into purchase orders.
Record deliveries against the order they fulfil.
Costs feed the asset register and the school’s finance picture.
Step 2 · Assigned by your role

If you teach

Finally Grace Uche, whose role carries the form- and subject-teacher workspaces. Teaching is not a different kind of account — it is another grant, arriving in the sidebar the same way the library and the clinic did. She is a member of staff who happens to teach.

1

Your form class

A form teacher opens their class and sees who is in it, how the day is going and which students need attention — the starting point of most teaching mornings.

Your assigned form class, its roll and today’s picture.
Open any student for a quick profile without leaving the page.
Granted by the form-teacher role — not visible to other staff.
2

Your gradebook

As a subject teacher the same person keeps a running gradebook: assessment columns they define, scores as they are marked, and a controlled publish when the term’s continuous assessment is ready.

Define assessment columns and weightings per class and subject.
Enter and revise scores as work is marked.
Publish to students and parents when the term is ready.
3

Your class broadsheet

At the end of term the form teacher’s broadsheet merges every subject teacher’s marks for the class into one sheet — the view they check and complete before results go to the school for approval.

Every subject’s scores for your form class, merged automatically.
Totals, positions and grades computed against the school’s scheme.
Completed here, then submitted into the school’s approval flow.
Step 3 · Your workspace

The floor every employee stands on

Underneath every one of those roles is the same workspace. Whatever the school assigned them, each of the four people above signs in to this: a home that routes them to their work, their own attendance, and their calendar. It is theirs, not the school’s.

1

Your staff home

The staff overview is the landing page for every employee. It gathers the workspaces this person can open and the signals worth acting on today, so the first click is always obvious.

One home for every employee, whatever their role.
Cards and links route to the workspaces this person is granted.
What is outstanding today, surfaced before it is chased.
2

Your calendar

A personal calendar sitting on top of the school’s: term dates and events that actually involve this person, in one view they can add to.

Personal events alongside the school calendar.
School-wide dates arrive automatically.
Add your own entries without leaving the workspace.
Step 4 · Your employment

HR, self-served

The parts of employment that normally mean a form and a queue outside an office are handled by the employee themselves. Leave, employment details and document requests all run from the staff HR workspace — and land in the school’s HR module for approval.

1

Your HR dashboard

The employee’s own HR picture: leave days remaining, balances by leave type, and anything of theirs currently waiting on a decision — requests, document requests and profile updates.

Leave days remaining and balances broken down by type.
Pending leave, document and profile-update requests in one place.
Everything scoped to this employee — no one else’s records.
2

Request and track leave

Leave is requested here and tracked to its decision. The employee raises a request against a leave type, sees where it is, and can cancel it — while the school approves it in the HR module.

Raise a request against a leave type and date range.
Track it from submitted through to approved or declined.
Cancel a request you no longer need.
Approvals happen school-side; the outcome shows up here.
3

Your employment details

The employment record the school holds for this person — the details HR keeps on file — visible to the person they describe, so errors are spotted by the one who would notice.

See the employment details recorded against you.
Raise a profile update where something is wrong or out of date.
Changes route to HR rather than editing the record directly.
4

Request payslips and letters

Employment letters, payslips and other paperwork are requested here and tracked to fulfilment — the request goes to HR and comes back in the same place, instead of over email.

Request employment letters, payslips and other documents.
Track each request through to fulfilment.
One trail, so nothing is re-requested or lost in an inbox.
Step 5 · The rest of school life

The modules you use as a person

The same modules that arrive as a workspace for the person who runs them arrive as a service for everyone else. Tunde runs the library; every other employee simply has a borrower account in it. That symmetry is the point — one module, two sides of the same data.

1

Messages and announcements

The messages and announcements that concern this person, in their own workspace — school-wide notices and direct conversations, without a separate group chat.

Direct messages and the announcements aimed at staff.
School notices in one feed.
Communication stays inside the platform, with a record.
2

Your own clinic record

The clinic Blessing runs holds a record for every employee too. This is the staff member’s own — their visits, medications and history — visible to them, and to the clinic, and to no one else.

Your own visits, medications and clinic history.
The same clinic module the school runs, from the patient’s side.
Staff wellbeing recorded rather than left informal.
3

Your library account

And the catalogue Tunde keeps is the catalogue every member of staff borrows from: what they have on loan, what is due, and what they are holding.

Your loans, due dates and holds as a library member.
Search the catalogue and place a hold from your workspace.
Appears only where the school has enabled the module.
How it fits together

Two things in one login.

Whatever your job, the Staff portal is a single workspace that combines your own self-service with the school modules your role has been granted.

1

Your self-service

Payslips, leave, messages and clinic records — the things that are personally yours.

2

Your assigned school modules

The slices of the school portal your role grants — a teacher’s classes, a nurse’s clinic, a bursar’s finance — no more, no less.

3

Configured by the school

The school decides what your role can see. Change roles and your workspace changes with them — automatically.

One login, everything connected

No exports. No re-keying. No separate tools.

The staff portal is part of the same connected platform as every other role — so what changes anywhere shows up here, live.

  • Self-service payslips and leave
  • Only the school modules your role is granted
  • At-risk students surfaced per class, for teachers
  • One workspace for every module you touch

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.