Threads scoped by relationship
Not everyone can message everyone. A teacher reaches their own students and those students' parents; a center reaches the people subscribed to it. No relationship, no door.
Mathematics — Grade 12 · Wednesday session
Lesson price
120.00EGP
Platform commission15%
−18.00EGP
Center share15%
−18.00EGP
Teacher's share
84.00EGP
Every lesson gets a line.
Edura runs a center or a tutor from the first booking to the last pound: check-in recorded at the counter, cash or online collection, and each lesson's takings split the moment it closes — written once, and beyond anyone's reach to erase.
- Commission on delivered lessons only
- Cash is recorded exactly as online is
- Arabic first, not translated later
The account
The money is split once, by one formula.
What a single lesson is worth is derived by one function for the whole system. The screen that shows you the split before you confirm, and the engine that writes it into the ledger afterwards, call that same function. There is no second copy to disagree with the first.
Settlement basis — chosen by the group's owner
On a 12-lesson course at 1,200 EGP with a single-lesson price of 120 EGP, one lesson is worth:
- Course priceDefault
- Full price divided by the planned session count.
- Session price
- The price of one lesson, as set — for pay-as-you-go.
- Subscription
- Each attending student settles at what their own coverage paid, counted from the real schedule.
100.00EGP
120.00EGP
per student
The first two differ because both numbers are real: a full-term enrolment amortises cheaper per lesson than a drop-in. That is why the choice is recorded on the group, rather than decided by whichever function reads the row first.
An unpriced lesson refuses to close.
Distributing zero to everyone looks like a success and is a permanent loss: the ledger is append-only, so the lesson stays closed and nobody was ever paid. The system refuses and rolls the whole thing back until a price exists.
Two rails, one ledger
Online — the amount is read from the server-side payment intent, never from the browser.
Cash at the counter — written into the same ledger, in the same moment. Not a lesser second record.
By role
Six screens, each answering one question.
- The center
How much came in today, and who still owes?
Halls and schedules, front-desk staff on bounded permissions, collection sheets, and off-system teachers entered by hand who still land in the same reports as everyone else.
The center's board: today's takings and who still owes. - The teacher
What have I earned on the lessons I delivered?
Your groups, your schedule, your attendance, and a wallet that moves only when a lesson closes. Hand the daily running to an assistant; the money authority stays with you.
- The parent
Is my child actually attending, and what am I paying for?
Attendance, absence and grades, payment for a lesson or a month from your own wallet, and read-only sight of your child's threads with adults.
- The student
What do I have, and when?
Subjects assigned automatically from your year and track, your schedule, your wallet, and a card carrying an eight-character code the counter can read.
- The assistant
What exactly am I delegated?
Everything the teacher does, except the money. And every action is recorded under your name on their behalf — never under theirs.
- Center staff
Can I see only my own job, not the whole center?
A preset decides the screen: receptionist, manager or accountant. A receptionist cannot reach finance, and an accountant cannot reach collaboration requests.
The counter
The most-used screen of the day, built for standing up.
The clerk opens it and the lesson running right now is already selected. Search by name or code, or read the card, take the cash, and record the check-in — one flow, without leaving the page.
Two attendance modes — a per-teacher setting
- Counter onlyA single check-in at the desk marks the student present for the session they chose.
- Counter, then doorA second check-in at the hall door. Anyone who checked in at the desk but never walked in stays in their own visible state — never quietly upgraded to present.
Communication
The system reaches people without anyone handing out a number.
Messaging inside the product is not a nicety: it is what lets a teacher keep their personal number private, a parent ask a question, and a minor stay within their guardian's sight.
A minor stays in their guardian's sight
If the student is a minor, their guardian can read their threads with adults — read-only, never writing as them. And minor is the default: without a verified date of birth, the account is treated as a minor.
WhatsApp for whoever has not signed in yet
A student registered at the counter gets a WhatsApp message with their student ID and a secure link to finish their own details — instead of standing at the desk filling in forms.
The owner's Monday email
A weekly summary of the week that ended: lessons, collections, and who still owes. Not a report you open when you remember — it arrives.
Guarantees
These promises live in the database, not on a marketing page.
A ledger that cannot be erased
The money and audit tables have UPDATE and DELETE revoked at the database level — for the whole application, back office included. A correction is written as a new entry, and the wrong one stays visible.
Every center isolated
Isolation is enforced as row-level policies inside the database, not as a clause every query must remember. One endpoint that forgets its condition still cannot reach another center's rows.
An audit trail on control
Every administrative operation writes its row in the same transaction that performs it — so a change cannot commit without leaving a trail.
Minor is the default
A student is a minor unless a date of birth exists, is verified, and puts them at 18 or over. Otherwise adult-facing messaging stays locked until a guardian address is confirmed — without stopping a single lesson, payment or sign-in.
Open your ledger.
Registration is free, and commission is only ever charged on lessons actually delivered.