Team and permissions

Your teachers see the course. Only you decide who sees the money

The moment an academy is more than one person, the question stops being "what can the software do" and becomes "what can she see". There are twenty-four answers to that here, and you give them out one at a time.

Eight starting points, then your own ticks

Invite somebody as a teacher, a head educator, a coordinator, a bookkeeper, an accountant or for marketing, and she starts with the set that role normally needs. Then you tick and untick whatever you like — what is enforced is the resulting list, never the label.

  • Nothing in the system decides anything from the role's name, so a custom mix behaves exactly as its ticks say.
  • Ownership is not a role you can hand out; it stays with the login that created the academy.
  • You invite by email and she accepts on a page of her own — no shared password, ever.

What a teacher gets by default

Her own days, her own students, the register, the materials and the messages — and her own pay. Not revenue, not who owes what, not the export, not the settings. That is the founder's own rule for this product and it is the default rather than something you have to remember to restrict.

  • Refusals happen where the data is loaded, not by hiding a menu item — so a link somebody sends her does not open something her keys do not allow.
  • A sensitive student note is its own permission, separate from the professional one.
  • A permission this version does not recognise is ignored rather than honoured, so a renamed key never keeps granting under its old spelling.

Paying your teachers

Each teacher has a pay model: per session taught, per day, per hour, a share of what the courses she led actually took, or nothing computed because you settle it another way. The system works out what she is owed for a period and subtracts what you have recorded as paid.

  • The share model is taken from the recorded payments of her runs, so it moves with reality rather than with a forecast.
  • A teacher can be allowed to see her own line and nothing else — no revenue, no other teacher's rate.
  • Recording a payment to a teacher is a record. No money moves through Slotora, here or anywhere else in the product.

And a record of who did what

Role changes, certificate issues and revocations, exports, deletions and finance actions are written into your academy's own log, with who did it and when. It is yours to read, not ours.

  • The log is a permission of its own, so not everybody who works in the academy can read it.
  • It names the action and the thing it happened to, not somebody's bank account number.
  • It is inside your academy, separate from anything we keep about the platform.

Questions about the team

Can I let a teacher take the register without her seeing what the course earned?

That is the default. A teacher starts with her days, her students, the register, the materials, the messages and her own pay — and none of the four money permissions.

Can two academies share a teacher?

A person can be a member of more than one academy, and each academy's data stays its own. Nothing about one academy is visible from the other, whatever she holds there.

Does Slotora pay my teachers?

No. It works out what each of them is owed from her pay model and your records, and you pay her the way you already do. No money moves through the product.

Set your academy up tonight

Create the workspace, add your first course and send the link. Nobody has to approve you.

The academy side costs an educator nothing: £0 a month, 0% commission, and no cut of what your students pay you.

Look inside before you type anything

There is a demonstration academy in Slotora with everything already in it: courses, students, a register, payments and certificates. Open its page and see exactly what a student sees of an academy that runs on Slotora. And you can go straight in with one press — no password — and see the academy from the educator's own chair.

See a real academy's page

It is a demonstration academy: the courses, the dates, the teachers and the reviews on it are invented, and no place can be booked there. It is a shared demonstration seat, so somebody else may be in it at the same time: you can open every screen and look at everything, and it is read-only — nothing in it can be changed, and nothing you do there reaches a real person.

What have we forgotten? We built this before a single educator had used it. If something you do every week is missing — or is wrong here — write and say so. We read every one. Write to hello@slotora.io

Create your academy

May we measure which pages actually help? “Accept all” also lets us measure our own adverts.

What exactly does this mean?

We'd like to use Google Analytics to see which pages help and which don't, and to remember which poster, flyer or message of ours — or which salon's recommendation — brought you here. Accept all also allows a Meta advertising pixel, so we can tell which of our own adverts brought a salon that signed up — and if you create an account, our server sends Meta your email address scrambled (hashed), never as readable text, with your IP address, your browser's details and Meta's own cookie ids — never your name — purely so it can recognise that the sign-up came from an advert. None of this runs on a salon's own booking page. Everything the service itself needs works either way. Cookie Policy