One register, and it survives the course that created it
Most academies have a student list per course, in a spreadsheet per course, and no way to answer "has she been here before?". Here a student is a person, and a course is something that happened to her.
The paper sheet that went round the room
A twenty-person class is twenty forms if you type them one at a time. Paste the sheet instead: the columns are matched for you, you fix what is wrong on a preview, and then it goes in. The preview runs the same code the import does, so it cannot promise what the import will not do.
- Names, addresses and phone numbers in whatever order your sheet has them.
- People you already have are recognised rather than duplicated.
- What you will get is shown before anything is written, with the problems named.
A student is a person, not a row on a course
Her record holds every course she has done with you, what she paid, what she was given and what was photographed. When she comes back in two years for the advanced course, it is the same person and the same history, not a new line in a new file.
- Move her to a later group and everything she has paid and done comes with her.
- She has no account and no booking page in your register — she is your record, not a Slotora user, unless she signs into her own portal.
- Her pictures keep the consent they were taken under, and she collects them from a link of her own.
Who on your team may read what
Seeing every student, seeing only the ones assigned to you, exporting the list and reading a sensitive note are four different permissions. A teacher starts with her own students and the professional notes, and without the sensitive ones.
- The sensitive note is separate on purpose: not everything an educator writes down should be readable by everybody who takes a register.
- Export is its own key, so a person who may read a list is not automatically a person who may take it away.
- Every export, every role change and every deletion is written into the academy's own log.
Whose data it is, and how it leaves
The register belongs to your academy and travels with it. Closing a salon does not touch it — and an educator who never had a salon still has a full deletion path, which is the part most systems forget.
- Erasing the academy erases its students, applications, payments, certificates and the models' signed consents with it.
- A student can be exported on her own, for a request you have to answer.
- Contact details are never published anywhere by the product.
Questions about the register
I have three years of courses in spreadsheets. Can I bring them?
Yes, class by class. Paste each sheet, check the preview and import. People who appear on more than one sheet are recognised as the same person rather than duplicated.
Do my students need a Slotora account to be in my register?
No. A student in your register is your record: no account, no booking page, nothing she has to sign up for. Her own portal is separate, and she gets into it with a link sent to her address.
If I close my salon, do I lose my academy?
No. They are two separate things on one login, and the academy's records are erased only when the academy is. An educator who never runs a salon has an academy and a deletion path of her own.
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.
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