Running a school with a roster of teachers
What a roster relationship actually is, the three arrangements a school can offer, and why the platform never moves this money.
This is for a School — a company-type workspace, not an individual tutor. A School can build a roster: invite named teachers, let them deliver sessions under (or alongside) its own listings, and settle what they owe each other. A Tutor workspace has no roster page at all, because there is nobody to add one under.
Joining a roster is a separate decision from everything else a teacher owns. Open the workspace's Roster & payouts section (in the workspace menu) to manage it.
What joining a roster does — and does not — do
A roster relationship covers money and affiliation only. It never gives the school access to a teacher's listings, calendar or account, and it never gives a teacher access to the school's — that stays exactly where it already is, for both sides. If you were expecting a roster invitation to also hand over control of a profile or a calendar, it does not; that would be a separate decision for whoever owns it to make.
Beyond that, what a roster relationship actually means is up to the arrangement the school picks when it sends the invitation. Three exist today:
- Affiliation only — the teacher joins the school's roster and nothing else changes. No commission, nothing to settle between you, no money passes through the platform. Useful when the relationship is informal, or the money side is handled entirely off-platform already.
- Commission, settled by invoice — the teacher keeps selling and collecting under their own name, on their own payment setup, and owes the school a commission on each sale they make.
- Fulfilment fee, settled by invoice — the school sells and collects the money itself, the teacher delivers the session, and the school owes the teacher a fee for each sale the teacher delivers.
Whichever arrangement is picked, one thing is true of all three: the platform never moves this money. It records who owes what, from what actually happened on the platform, but the payment itself happens directly between the school and the teacher — the same way it would if they had agreed it on paper.
What is still being worked on
Everything a roster relationship settles today, it settles by invoice, after the fact — the platform records what is owed, and the two of you pay each other directly. That is deliberate, not a stopgap: it needs no payment credential from the teacher and works on every processor a school can connect.
What we do not have yet is the platform splitting a single payment automatically at the moment of sale, so that a teacher's share reaches them directly, without either side raising an invoice. This is still under development. For schools in Ukraine specifically, it is waiting on an unresolved fiscal-receipt question we do not control the timing of, so we are not giving a date for it. If you need per-sale automatic payouts today, no arrangement above provides that — every one of them is invoice-settled, by design, until this ships.