System
About the software that runs Training System.
About this software
- Version
- 2.12.0
- Designed and created by
- Dean Ciui and Claude (by Anthropic)
Version history
Every update to this software, newest first. Older updates are folded away; select one to read it.
-
Version 2.12.0 Installed version Dean's decisions on the security audit of ciui.co.uk on 2.11.1 (lockout, account enumeration, extra quiz time, mentoring messages on erasure). The same on every site (ciui.co.uk, ciui.ro, on.training, gxp.training), and every change is per workspace on on.training. Four additive migrations; nothing existing is rewritten.
- Dashboard: the "Need help?" box now comes after Courses, Private Sessions and Webinars, and has a "Hide this box" button (Dean, S58). Hiding is saved on the person's account, so it holds on every device; Help stays in the header and menu, and the Help centre has a link to bring the box back. One additive column (users.dashboard_help_hidden_at).
- Security: an account is locked for 15 minutes after 10 wrong passwords in a row, and its owner gets an email (at most one an hour). While it is locked, the right password is refused with the same message as a wrong one. The count starts again after a successful sign-in, and a completed password reset ends the lock. An Admin (users.manage) can unlock the account early on the user's page; the support desk sees the lock. Lock and unlock are in the activity log, by account number only. The per-minute sign-in limit is unchanged. The numbers can be changed with LMS_LOCKOUT_ATTEMPTS and LMS_LOCKOUT_MINUTES.
- Security: "Forgot password" gives the same answer whether or not the address has an account ("If that address has an account, we have sent it a link..."), also when a link was asked for a moment ago. The link is made and sent after the page has answered.
- Security: signing up (also as a school) with an address that already has an account no longer says so. The page says "Verify your email", nothing is created or changed, and the owner of the address gets an email with links to sign in or reset the password (at most one an hour).
- Extra time on timed quizzes: a learner can give themselves up to 50% on My account > Accessibility. More (up to 300%) is set by a teacher on My learners, who can also put it back to the default (no extra time) or let the learner choose again. Once a teacher has set it, the learner sees it but cannot change it. When a learner changes their own extra time, their teachers get a notice, and an email at most once an hour.
- A learner who chose more than 50% before 2.12.0 keeps their choice on record, but it counts as 50% until a teacher confirms it. The teacher sees "asked for N%" on My learners. Nothing is rewritten in the database.
- Mentoring and data deletion: before approving a deletion request, the approver sees how many mentoring messages the person wrote as a mentor and as a mentee.
- Messages the person wrote as a MENTOR are kept for safeguarding for 6 years (LMS_MENTORING_SAFEGUARDING_YEARS), with who wrote them, to whom and when, and are removed from the conversation. Only people with the new safeguarding.view permission (Admin and Super admin; an install can give it to a safeguarding lead role) can read them, on Manage > Mentoring > Safeguarding records; opening that page is logged. The other person in the conversation no longer sees them. A daily job (mentoring:purge-safeguarding, 02:45) deletes them when the period ends.
- Messages the person wrote as a MENTEE are removed, including reported ones. (Before, in 2.11.2, every message was removed except those someone had reported.)
- The email telling the person their data was deleted says what was kept, until when and why.
- Legal basis for keeping a mentor's messages: UK GDPR Art. 17(3)(b) (a legal obligation: child-protection record keeping) and Art. 17(3)(e) (legal claims); where a message holds special-category data, Art. 9(2)(g) (substantial public interest) with DPA 2018 Schedule 1 paragraph 18 (safeguarding of children and individuals at risk).
- Mentoring reports: reporting a message now needs a reason, which staff see. Staff can mark a report "Dealt with", which takes it off the list and records who dealt with it and when.
- Fix round 1 (review and security review of 2.12.0, before release):
- Extra time: an Admin (anyone who manages users) can now set, reset and hand back a learner's quiz extra time on Manage > Users > the learner, also for a learner who is in no group and so has no teacher. When such a learner changes their own extra time, the workspace's Admins get the notice and the email (at most one email an hour) instead. On on.training an Admin reaches only their own workspace's learners. Nobody can set their own extra time.
- Extra time notices: a teacher (or Admin) gets at most one new in-app notice per learner an hour; further changes within the hour update that notice ("changed N times, now X%") and mark it unread again. When a learner's account is erased, the notices staff were sent about them are deleted too.
- Security: signing in with an address that has no account now takes as long as a wrong password (one password check against a dummy hash at the configured cost), so the sign-in page no longer tells, by its speed, whether an address has an account.
- Security: Parents > Add a learner no longer says "The email has already been taken". For an address that already has an account, the parent sees the same message and the same "Waiting for the learner" line as for a new one, nothing is created, and the owner of the address is emailed (at most once an hour) that a parent tried to add them, with a link to invite that parent from their own account if they want to.
- Security (on.training): Start your workspace no longer says "This email address cannot be used" at the details step. At the Pay step an address that already has an account is not charged; the page says "Please check your email ... nothing has been charged", and the owner of the address is emailed (at most once an hour) that a new workspace needs a different address.
- Security:
php artisan user:unlock {id or email}unlocks an account from the server (clears the lock and the wrong-password count) when no Admin can sign in to do it. The activity log records the account number only, never the address. - Data deletion: approving a deletion request is now all or nothing. If a step fails, the request stays pending and nothing is erased, so a retry keeps and reports the mentoring messages exactly as a first attempt would. The outcome email is sent after the approval is saved.
- Mentoring reports: every report is kept in its own history (who reported it, why, when, who dealt with it and when). "Dealt with" no longer loses when a message was reported, and reporting a message again keeps the earlier reason. The kept safeguarding record of an erased mentor's message carries that whole history. One more additive migration (2026_11_13_100004: two new tables and one new column).
- Fix round 2 (second review and security re-check of 2.12.0, before release):
- Migration 2026_11_13_100004: the report date and the waiting-line expiry are stored as dateTime, not timestamp. On MariaDB before 10.10 (or a server set that way) a timestamp column would have been rewritten to "now" whenever the report was dealt with.
- Security: Parents > Add a learner now takes as long for an address that already has an account as for a new one (both spend one password hash), and the address is lower-cased before anything else, so neither the time taken nor the letter case of the "Waiting for the learner" line tells the two apart. A parent's own address is refused whatever its letter case.
- Security: the per-address sign-up limit treats accented and differently-cased forms of an address (ana@, Ána@, àna@) as one address, as the database does.
- Security: the "someone used your address" emails from sign-up, Add a learner and Start your workspace now share one limit: at most one an hour per account across all three (before, one an hour from each). All three are queued instead of sent while the page waits.
- Mentoring and data deletion: once an erased mentor's messages are kept for safeguarding, the reasons given when they were reported, and their report history, are removed from the live tables, so the kept record (6 years, safeguarding.view only) is the only copy. Manage > Mentoring says the reason is in the safeguarding records. Erasing a mentee is unchanged.
- Dean's decisions after the reviews (2026-11-13):
- SA7 B: sign-up stays one step (a new account is signed in straight away, as before), and every sign-up path has a rate limit so a long list of addresses cannot be checked quickly: /register 5 a minute per connection and per address, and 20 an hour per connection (unchanged); school sign-up 5 a minute and 20 an hour per connection (unchanged); register your workspace (on.training) 5 an hour per connection (unchanged); Add a learner and Start your workspace (new) 5 a minute and 20 an hour per connection and 5 an hour per address typed. The hourly figure follows LMS_SIGNUP_HOURLY_CAP_PER_IP.
- SA8 B: safeguarding.view stays with every Admin and Super admin.
- Known limit, for Dean: removing a workspace on on.training deletes its kept safeguarding records with everything else, before their 6 years are up, and the workspace backup keeps them until it is deleted. Not changed in this release.
- Final review fixes:
- Erasing a mentor now locks the messages and reports it copies into the safeguarding record, so a report filed at that moment waits and is kept, never lost between the copy and the clean-up.
- Add a learner refuses the parent's own address whatever its letter case or accents, also when the parent's account was saved in mixed case.
- Manage > Mentoring: the note on an erased author's message no longer claims every such message is kept; only messages written as a mentor are.
-
Version 2.11.2 Fixes from the security audit of ciui.co.uk on 2.11.1, and the small follow-ups to the 2.11.1 code review. The same on every site (ciui.co.uk, ciui.ro, on.training, gxp.training).
- Security: a password reset is never sent to an email address the support desk set until that address is verified, and a reset link for such an account does not work. Before, the public "Forgot password" page did not apply the rule the support desk's own button did, so a support admin could take over a learner's account. An Admin can still send the reset from the support desk; that is now written to the support log.
- Security: a course or lesson title, or a lesson's key facts, can no longer contain text that runs as script on the public course page.
- Security: every Manage screen now checks permission on every action, not only when the page opens. Someone whose admin rights were removed can no longer keep using a page they still had open (for example to approve data deletions, re-enable accounts or change payment keys).
- Security: quiz time limits are enforced on the server. A timed quiz now has a "Start the test" button, and its questions show only after it is pressed. Start records the attempt and its deadline (the time limit, including the learner's extra time, plus a minute's grace). Reloading the page, opening it in another tab, signing out and back in, or coming back later carries on with the same attempt and the same deadline; the clock never starts again.
- An attempt handed in after its deadline is recorded but scores 0, is not passed and does not count towards completion or a certificate.
- An attempt that is started and not handed in before its deadline counts as one of the learner's attempts, with a score of 0, the same as a late one. It is recorded the next time the learner opens that quiz. (A decided default, which can be changed: before, an opened attempt that was left was never counted, so a learner could read the questions, wait and start again.)
- A pre-assessment is a starting point, not a test to pass: a late or unfinished pre-assessment still completes its topic, as any pre-assessment did before, so it can never block a course. It earns no webinar pre-test certificate.
- The countdown on screen now follows the real clock. Before, it fell behind when a phone was locked or the tab was in the background, so it could show more time than the server allowed.
- Untimed quizzes are unchanged. The grace can be changed with LMS_QUIZ_TIME_GRACE (seconds).
- A course reset ends any timed attempt the learner has open on that course: the learner presses Start again and the attempt counts in the new round. Before, an attempt started before the reset and handed in after it counted nowhere.
- An attempt that was started and left is dated at its deadline, with its time counted up to the deadline, not up to whenever the learner came back.
- A test drawn from a question bank keeps the same questions for the whole attempt, also after signing out and back in or in another browser. Before, a new sign-in drew new questions on the same clock.
- A page showing a result no longer hands in a second attempt: a new attempt starts with Retake (and Start).
- A page that was open when this release went live keeps its questions after the learner presses Submit with nothing answered.
- Security: the correct order of a "put in order" quiz question is no longer in the page source. The server now shuffles the items and sends them without anything that shows their order.
- Security: an invited person who accepts her original invitation after the support desk changed her email address no longer has the new address marked as verified, so a password reset still waits for it.
- Security: a course preview's quiz checks permission on every action too, so someone whose author rights were removed can no longer hand in a draft quiz from a page left open and see its answers.
- GDPR: approving a data deletion now also removes the person's community threads and posts (a thread other people replied to stays, without its title or author, with the person's posts blanked), and renames the personal licence account they own to "Deleted user (personal)". A personal licence account they were only given a seat in is left alone. If another owner remains, the account keeps its billing details.
- GDPR: approving a data deletion now also blanks the person's mentoring messages, removes the request they sent to a mentor and the decline notes they wrote, and deletes their mentor profile. A message someone reported is kept as written, as a safeguarding record (a decided default, which can be changed). The mentorship itself stays as the record of who mentored whom.
- Security: "Resend invite" is refused while the invited person's email address is one the support desk set and has not been verified. Before, the invitation could go to an address that was not the person's.
- Security: the course preview checks permission on every click, so someone whose author or support rights were removed can no longer keep reading a draft course from a page left open.
- Support desk: before an Admin sends a password reset to an address the support desk set and nobody verified, a warning explains the risk and asks the Admin to confirm.
- GDPR: "Download my data" now also includes community posts, assignment work, CPD records, uploaded files, notifications, and webinar and Private Session attendance.
- Security: two unused account routes are switched off: one changed the email address without asking for the password, the other changed the password but left other devices signed in. My account is unchanged.
- Security: an account whose email address is not verified can no longer act through a copied page; the verification check now applies to every action.
- Security: guessing the current password on My account is limited to 5 tries a minute.
- Security: private files are no longer marked as cacheable by shared caches.
- The on.training product page no longer lists passkeys (they were switched off in 2.11.1).
- Private Sessions > Live: the learner's screen in the teacher's view shows the site's font again.
- Security: an ordering question only accepts the answer tokens the page was given. Before, raw option numbers, which could be guessed from the other answers on the page, were also accepted, and that handed out the correct order. A page left open across this update loses its one ordering answer.
- Security: after a test is handed in, the result page can no longer be turned back into the test from the browser, or started again on the same questions. A new attempt goes through Retake, which draws the questions afresh.
Micro sessions
Nothing changes while the add-on is switched off.
- While practice is paused after a handed-in week test, the message no longer says the test can still be retaken (it may have no retake left).
- A question whose own picture is on another website now has no picture, instead of the lesson's first picture.
-
Version 2.11.1 Fixes from a bug sweep of ciui.co.uk after 2.11.0 (live logs, a crawl of the public site, and every page and main action tried as each role on a copy), and the small follow-ups to the 2.11.0 micro sessions reviews. The same on every site.
- The site's own font (Figtree) shows again on every page. Bunny Fonts now serves its font files from jsDelivr, which the security policy blocked, so pages fell back to the system font. Brand fonts chosen from Bunny Fonts in Settings are fixed the same way.
- Passkeys were half switched on and only gave errors: they are now off until they are built properly. Nothing changes for anyone signing in (no screen offered them).
- Settings > Licence no longer shows an error page when the licence record leaves a detail out.
- "Connect to QuickBooks" before QuickBooks is set up goes back to Settings with a message instead of an error page.
- Manage > Users: pressing Grant without choosing a role now says "Choose a role to grant first." instead of showing an error pop-up.
- Security (urgent): closed a hole that let a learner read the answers to any quiz in their workspace from the browser console (and so pass a one-attempt final exam at 100%), and let a free-preview visitor read the text of a paid course's other lessons the same way. Helper code that pages use to show questions and lessons could be called directly from the browser; it now runs only on the server. The same was closed for the course builder's "insert from a course" list (a course creator could read another creator's lessons) and the checkout page. Pages look and work exactly as before.
Micro sessions
Nothing changes while the add-on is switched off.
- The "Finish your week test in ... first" banner no longer shows once that test has been handed in. While a handed-in test can still be retaken, practice says it is paused until that week ends.
- A question whose own picture cannot be copied now has no picture, instead of the lesson's first picture (which could be a different one).
- Security: files uploaded by someone who only owns a personal licence, or by the staff of a deleted school, no longer count as library files that can be copied into a micro session.
- Saving a title on a very large programme no longer runs one database query per title sent with it.
-
Version 2.11.0 The dashboard gets separate sections for Courses, Private Sessions and Webinars, the help centre gets guides for Webinars and Private Sessions, and Help is easier to find (Dean, for ciui.co.uk; the same on every site).
- Dashboard: each kind of learning has its own clearly headed section, shown only when the learner has something of that kind. Courses keeps the Enrolled / In progress / Completed / Certificates tabs, now for ordinary courses only; Certificates still lists every certificate. Private Sessions lists each plan with where it stands (live now, open any time, waiting for your teacher, completed) and a link only when it can be opened. Webinars lists the live webinars the learner signed up for (coming up, with Join while live, and past ones; cancelled places and cancelled sessions are not listed) and courses run as a live webinar. A section is hidden while its add-on is switched off. A brand-new learner still sees "Browse the catalogue".
- Help centre: new Webinars and Private Sessions guides, each in a "For learners" and a "For teachers" part. The Webinars guide shows only the steps (and a summary) for courses run as a live webinar where the live-webinar add-on is off; the Private Sessions guide is shown only where that add-on is on. Guides can be filtered by who they are for (Learners, Teachers, Admins, Everyone).
- Help is easier to find: a "Need help?" card on the dashboard with the guides for what that person does, Help as a brand-coloured button at the bottom of the menu, a Help button in the top bar, and "Help with this" links on the webinar and Private Session pages for learners and teachers.
- Fix: the sitemap no longer lists a help guide whose add-on is switched off (that page returns "not found").
- The list of help guides is worked out once per page instead of once per help link, so pages with several help links make fewer database queries.
Micro sessions
Micro sessions, following Dean's answers of 12 November. Nothing changes while the add-on is switched off.
- Week test results show straight away which questions the learner got right and wrong, with their own answers. The right answers and explanations are never shown to the learner (teachers still see everything).
- A session the learner got a question wrong in comes back in a later week, so it is done again and can be tested again.
- A learner must hand in a week's test before moving on: after the Sunday the test stays open and next week's sessions do not open until it is handed in.
- A programme belongs to its school (or the site), not to the teacher who made it: any teacher of that school who can manage micro sessions can edit it. A teacher removed from the school loses it; the programme stays.
- A learner's data download holds their test results only (scores, times, right and wrong counts), never the questions or answers.
- Pictures: generating from a course now brings lesson pictures, and the picture a question refers to; questions in the editor can have a picture. Learners see them in sessions, practice and the week test, and only for programmes they are on.
- on.training: the micro sessions add-on cannot be saved as an extra without a price (at least 0.01) on a package that is on sale. Saving another add-on is not affected.
- A session got wrong in any try of a week's test comes back, even after a full-marks retake.
- When a week test in one programme holds the learner's sessions in another, the message names that programme and links straight to the test.
- Security: pictures and sounds copied into micro sessions (from a course or in the editor) are limited to the course's or the teacher's own library files, never another school's private files or learners' uploads; micro session pictures are served as JPEG, PNG, GIF or WebP only.
- With School content off, a new programme still belongs to its teacher's school; one with no school is shared only on a site with no schools.
-
Version 2.10.1 Micro sessions fixes, needed before the add-on is switched on anywhere. Nothing changes while it is switched off.
- Saving a session or week title on a very long programme (over 500 sessions) no longer blanks the title.
- A learner's week test that was left open after its week ended, or after its time ran out, no longer stops their other programmes' sessions and practice.
- A blank or invalid generate item limit in the settings falls back to 1,000 instead of refusing every generate.
-
Version 2.10.0 Micro sessions: one short session a day and a test at the end of the week. A new add-on, switched off on every site until an admin switches it on (Settings > Features, or Manage > Modules on a workspace whose package has it). Reminders (a new session is ready, the test is open) follow in a later release.
- Teachers build programmes (Manage > Micro sessions): weeks of up to five sessions of 3 to 5 minutes, each with words, flashcards, questions or short lesson content, written by hand, picked from the vocabulary, flashcards, question banks, quizzes and lessons they already use, or generated from a course they can edit. Pieces are copies, so later changes to the originals do not change the programme.
- Each week has a short test made from that week's items. The system suggests questions, the teacher accepts, edits, removes or adds them, and a programme cannot be published until every week's test has been reviewed. A changed item sends its question back for review.
- Teachers put learners on a published programme one by one or as a group, and can take them off again; each learner gets an in-app message. Teachers only ever reach the learners of the schools where they are active staff (or everyone, on a site with no schools); a teacher who reaches nobody cannot manage programmes at all.
- Learners find their programmes on My learning. From the day they press Start, one new session opens each weekday in Monday-to-Sunday weeks; a missed session stays open to catch up until the end of the week, and anything not done moves to the next week. A question says straight away whether the answer was right, and finished sessions can be practised again. Works on phones and with the reading preferences.
- The week test opens once the week's last session is done, or on Saturday, until the end of Sunday, and asks only about the sessions that learner did. Learners see their score as soon as they hand it in and can retake it while tries are left. Which answers were right, the right answers and the teacher's notes show from the Monday after the week ends. From the start of the test until then, that week's sessions are closed, practice included, so a first try cannot be used to find the answers for a retake. Time limits include the learner's extra time and are kept by the server.
- Teachers follow progress (Manage > Micro sessions > Progress): each learner's week, sessions done, last test score and last active, by group or status, with a CSV download and a page per learner. Parents see each child's sessions this week and the last test score, never the questions or answers, on My children and in the weekly email.
- Micro-session data is in a learner's data download (their own rows; test answers only once that week has ended) and is erased with the account; a teacher's programmes stay with the workspace. A help-centre guide explains it wherever it is switched on.
- Generating a programme from a large course takes seconds: hundreds of words no longer run into the server's time limit.
- One generate takes up to 1,000 items (choose some modules or lessons for a bigger course), and while a learner has a week test open on any programme, practice is paused on all of their programmes until that week ends.
- Quiz marking now lives in one shared place, so quizzes and micro sessions mark answers by exactly the same rules. Nothing changes for quizzes.
-
Version 2.9.3 Teachers reach only the schools where they are staff in mentoring, community moderation, groups and course teaching, and Private Sessions follow that reach only (security, follow-up to ISSUE-098).
- Mentoring: until now every teacher could read every mentorship in the workspace, with its messages, reports and mentor applications. Now admins (people who manage users) and teachers on a site with no schools still see them all. Any other teacher sees a mentorship only when the mentee is in a school where they are active staff, and a mentor only when the mentor is.
- Community: a teacher who is a student in another school no longer moderates that school's posts. They cannot hide, unhide, remove, lock or pin them, and they do not see its hidden posts or its reported posts. What a learner sees in a community space is unchanged.
- Groups and course teachers: only active staff of a school can be made a group teacher or helper there, or be assigned to teach a course for it. A student or suspended member can no longer be.
- Private Sessions: a teacher removed from a school no longer sees the sessions they ran. A session shows to a teacher only while its learners are in their reach, so it also stops showing to them when a learner moves to another school.
- Removing a teacher from a school now hands their sessions for that school over to another teacher. The Owner (My organisation > Members) or an admin (Organisations > Members) picks who takes over from the school's teachers, past and upcoming sessions alike. The teacher keeps their other schools' sessions. A teacher who removes themselves, or whom the support desk removes, hands over to the school's Owner.
- The sessions should go to someone who can open every one of them: with school content on they must be able to manage each session's plan, and in every case each learner on it must be in their reach. The picker refuses a choice who cannot when someone else could, and asks you to choose again.
- Removing a teacher is never held up by the handover: taking away their access comes first. When nobody at the school can open every session (for example a session built on the teacher's personal plan, or one with a learner from another school), the sessions still move, to the person chosen or to the Owner, or stay unassigned when the school has no other Owner. The person removing them is told how many only an admin can open now and why, and the case is recorded in the activity log. Removals at the same school happen one at a time, so two at once never hand sessions to someone who has just left. Each move is recorded in the activity log by record numbers only.
- No database change.
-
Version 2.9.2 A teacher removed from their school can no longer reach the learners of every school in the workspace through Private Sessions (ISSUE-098, security).
- Removing a teacher from their school takes away their membership, but they keep their teacher account. Until now Private Sessions treated a teacher with no school as a teacher on a one-school site, so they could find and assign every learner in the workspace, and see every session. Now only admins (people who manage users) and teachers on a site with no schools at all reach the whole workspace. Any other teacher reaches only the learners of the schools where they are active staff, and nobody if they have none.
- Only a staff role in a school counts: school owner, group overseer, teacher, marker or assistant. A teacher who is a student in another school no longer reaches that school's learners. A suspended membership does not count either.
- One-school sites work as before: on a site with no schools, a teacher still reaches everyone. Deleting a site's last school does not turn this back on.
- A session whose learners have all been removed no longer shows to other teachers, so its notes stay with the teacher who ran it.
- No database change. The course group filter in Progress and Homework keeps its own rule and is unchanged.
-
Version 2.9.1 Every table that belongs to a workspace refuses a record that does not say which workspace it is for again (ISSUE-097).
- Since 2026-07-19 the database has refused a record saved without a workspace, so a mistake in the code cannot put a school's data into the first workspace. Fourteen tables added since then had lost that safeguard: Discord links, discount codes and their uses, page layouts and the layout library, the marketplace ledger and payouts, card checkouts, Private Session deliveries, purchase requests, session categories, and live webinar sessions, registrations and activity answers. Every part of the code that saves to these tables already says which workspace, so this was a missing safety net, not a leak. The safeguard is now back on all fourteen.
- An update to the database makes the change when this version is installed. It changes nothing else on those tables and no data is touched.
- An automatic test now checks every table, so a new table cannot lose the safeguard without the test failing.
-
Version 2.9.0 Schools can now sell their own courses to other schools (Part 3).
- A school's owner can put one or more of the school's published courses up for sale as a pack under Manage > Selling: a name, a description, the number of seats (or unlimited), a price and the school's own terms of use. The school decides the seats and the terms. Saving sends the pack to the site's team for approval, and changing it later sends it back for approval again.
- The site's team approves, rejects (with a reason the school sees) or suspends packs under Manage > Marketplace. The school's owners are emailed each decision. Nothing can be approved until the site's percentage and fee have been saved under Manage > Marketplace > Settings (20% and no fee to start with; a change applies to sales from then on).
- Other schools' owners see approved packs under Licences, in "From other schools", and buy them by card through the site's own Stripe account. They must tick to accept the selling school's terms, and discount codes cannot be used. A guest, an individual learner, a learner, or the selling school's own staff never see a pack, and the server refuses the purchase too.
- The site takes the payment and pays the selling school by hand once a month. Each sale is written to a ledger with the site's cut worked out on the price before VAT: the percentage and fee in force at the time of the sale are kept with it. Under Manage > Marketplace > Payouts the team prepares each ended month's statements, marks each one paid with the bank reference (the school's owners are emailed), and records refunds already made in Stripe. A refund after a payout comes off the next one. A payment that arrives twice (the return page and Stripe's notice at once) is recorded once.
- The selling school's owners see their sales, refunds and payouts under Selling > Statement and can download them as a spreadsheet. They see which school bought, never who its learners are.
- Privacy: a school that sells a course never sees the buying school's learners - not on assessment results (page or spreadsheet), course reviews, progress, homework, marking or learner results - and the buying school never sees the seller's. Only the site's own team sees everyone.
- The buying school puts the course into its groups as usual. Each learner takes a seat on the licence it bought; with no licence or no free seat the learner is not added. The buying school can use the course but never edit or copy it.
- While another school holds an active licence for a course, the selling school cannot delete it, unpublish it or move it to another owner ("1 school uses this course"). It can still correct the content, and the changes reach the buyers. If the selling school is suspended or removed, its packs come off sale, but what was bought keeps working.
- Once another school has bought a pack, its list of courses cannot be changed (the buyer keeps exactly what it paid for). Make a new pack for a different set of courses. Everything else can still be changed and goes back for approval.
- Community spaces on a sold course are split per school: each school's staff and learners see only their own school's threads and posts, and moderators only their own school's reported posts. The site's own team sees everything. A school's moderators manage only their own school's course spaces (and general ones). Nobody can move a course space that already has threads off its school course, because that would show its posts to other people: make a new space instead.
- The site's team approves exactly the version of a pack they opened. If the school changes it in the meantime, they are asked to look again.
- Recording a refund with "end the year this order paid for" ends only that year: a school that renewed keeps the year it still pays for. Each order's year can be ended once, and a year already used up cannot be ended. If there is nothing to end, the refund is not recorded and the team is told why; the money can still be refunded with the box unticked. A year counts as gone only when a refund ended it: a year refunded with the box unticked (goodwill) is kept, and ending the last year still running ends the licence.
- If a pack's courses or seats change while a school is paying for it, the paid order is held for the site's team, who are told, instead of delivering something the school did not see.
- A change to a school's payment details is dated, and every owner of the school is emailed. The Payouts screen shows when the details last changed. A payout is not marked paid after a recent change until the team ticks that they have checked the new details with the school.
- A pack comes off sale when one of its courses is deleted, unpublished or no longer the school's own. A suspended pack cannot be changed by the school until the site's team lifts the suspension. The team is emailed once when a pack arrives for approval, not on every save. The licences screen offers schools' packs only while selling between schools is on. Spreadsheet downloads guard against formulas hidden behind spaces. Pack prices show in their own currency.
- On a site with several workspaces, each workspace has its own marketplace, percentage and payouts.
- Off on every site until switched on in Settings > Features ("Selling between schools"; it also needs School content).
-
Version 2.8.0 Parents can now buy a course for their child (B4).
- A learner under 18 cannot buy courses themselves. With the new "Parents buy for their children" switch on, they see "Ask my parent to buy this" on a paid course page. Every parent linked to them is emailed and sees the request on My children, with the course, the price and when the request ends. The learner can cancel their request while they wait.
- The parent presses Buy, sees the price, VAT and any discount code, and pays. The learner is enrolled and told; the parent gets the invoice. Or the parent declines, and the learner is told.
- Safeguards: the learner never pays and never chooses who is asked; nothing they type reaches the parent (the email and notice say "your child"); only a parent linked to that learner can see, pay for or decline a request, and the link is checked again when paying and when the payment is recorded. The paying parent must be 18 or over; a course's minimum age is checked against the learner. Only standard paid courses can be asked for (not webinars, resources, licences or a school's own courses).
- The price is always worked out on the server from the course. A payment that arrives twice (the return page and Stripe's notice) never enrols or charges twice.
- Only one parent can pay for a request at a time: once a parent opens the payment page, another parent (or a second tab) is told someone is already paying, for 35 minutes (the Stripe payment page itself closes after 31). A request about to run out is kept open while a parent is paying. If money still arrives that cannot be used - a second payment, a request closed meanwhile, the learner's account deleted, or the parent link removed - the order is kept, nobody is enrolled, the order is marked for refund in the parent's purchases and shows "Refund needed" with the reason in Manage > Orders, admins get a notice ("Order needs a refund") and the activity log says which order to refund. A discount code used on it is given back. The parent still gets the invoice email and the sale still goes to QuickBooks, because the money was taken: the refund itself is done by an admin in the payment provider.
- A learner can ask at most 5 times a day; a parent receives at most 10 requests a day. A request lasts 14 days and then closes (nightly at 03:30). Removing a learner's last parent link, or deleting their only parent's account, closes their open requests. Discount codes can be tried at most 10 times a minute.
- The learner's purchase history does not show the parent's payment; the parent's shows who it was for. A learner's requests are in their data export and are deleted with their account.
- Off on every site until switched on in Settings > Features (it also needs Progress and parents, and Learners' date of birth).
Also fixed (ISSUE-095):
- When the very first two sales of a site (or of a new workspace) happened at the same moment, the second one could fail while the invoice counter was being set up. Its order was then not recorded: Stripe tried again later, but an Omnipz payment could be left with no order or invoice. The counter is now set up safely, so both sales are recorded with their own invoice numbers.
-
Version 2.7.0 The public demo (demo.on.training) resets every 30 minutes, and its activity log entries are deleted every night (Dean).
- The demo is now reset every 30 minutes, on the hour and the half hour. Before, it was reset after 15 minutes without use (checked every 5 minutes) and again on every hour, which did not give visitors enough time to try things out.
- New nightly job
demo:prune-activity(03:30) deletes the demo workspace's activity log entries. The demo only ever contains sample accounts and visitor play, so its log has nothing worth keeping. Only the demo workspace is touched: it must have the demo address and be marked as the demo, and the demo must be switched on for the install. On ciui.co.uk, ciui.ro and gxp.training the job does nothing. Entries of every other workspace are never deleted. - Each scheduled reset writes one summary entry, "Reset the demo workspace (scheduled reset)", which the nightly job then removes.
demo:reset --if-idlestill works when run by hand.
-
Version 2.6.1 The activity log no longer records email addresses or people's names in the older entries that 2.6.0 had not yet covered. The log is kept for good and a GDPR erasure cannot reach it, so personal details must not go into it.
- People are now named by account number ("user account #12") instead of their email address. This covers a personal licence account being created (every individual purchase), enrolling someone without payment, setting or removing an organisation owner, changing someone's role in an organisation, an admin correcting a name or email or setting a new password, and every support desk action (name or email corrections, password-reset emails, deletion requests, adding or removing someone from an organisation).
- A learner's personal organisation is shown as "organisation #number" in these entries, because it is named after the learner. Company, school and group names are shown as before.
- When an admin or the support desk corrects a name or email address, the log says which details changed ("Changed name and email"), not the old and new values.
- Assigning a Private Session lists the learners by account number, not by name and email address.
- Issuing or editing an install licence still records the customer (business) name, but no longer the customer's email address.
- The support desk still cannot send a password reset straight after changing someone's email address to one that is not yet verified; this safeguard now works without the address being stored in the log.
- Support > Activity now shows, next to each entry about an account, that account's current name and email address with a link to it. These are looked up when the page is shown, not stored in the log.
- The demo workspace reset (every 5 minutes when idle, and hourly) no longer fills the activity log. Since 2.6.0 each reset added about 440 entries, about 127,000 a day on on.training. Now the hourly reset adds one entry ("Reset the demo workspace") and the 5-minute reset adds none.
- Entries written before this version are unchanged. Cleaning them up is a separate decision.
-
Version 2.6.0 Every admin action is now in the activity log, so any change can be traced (Dean).
- Manage > Activity now records every change to courses, modules, lessons, topics, quizzes and questions, licences and seats, organisations and groups, enrolments, certificates, pages, blog posts, email and certificate templates, media, resources, vocabulary, webinars, invitations, parent links, orders, invoices, workspaces and user accounts: who made it, when, and what changed (each field's value before and after).
- Adding or removing people in a group, teachers and assistants, organisation members and their roles, the courses in a group or a licence product, role and permission changes, and which feature switches were turned on or off are all recorded as well.
- Personal details (a person's name, email address, phone and date of birth) are recorded only as "changed", never with the details themselves. The same goes for a learner's personal organisation (shown as "organisation #number"), the names of uploaded files, and who switched a module off. Copying a course is one entry ("Copied course ..."), not one per lesson and question. Passwords, security codes and keys are never recorded at all. Long page and lesson text is shown as "changed" rather than copied into the log.
- Editing the same page or lesson many times in a row is recorded once every 10 minutes per person, listing everything that changed, so the log stays readable.
- Learners working through their courses do not fill the log: their progress keeps its own records, as before.
- The Activity screen has new filters: search, who did it, type of record, record number, kind of action (created, updated, deleted, other), log, school, and from/to dates (UK dates, both days included). Each entry opens to show a table of what changed. The filters are kept in the page address, so a filtered view can be bookmarked or shared with another admin.
- "Download CSV" exports the filtered list (up to 10,000 entries, newest first); every download is itself recorded.
- New "History" links open the log for one course, user account (also "Actions by this person"), organisation or group.
- On on.training, each workspace now sees only its own entries, including automatic (system) ones, which were shown to every workspace before.
- Entries are still kept for ever (needed for GxP audits). Only Admins see the Activity screen, as before.
-
Version 2.5.1 Member imports send their emails gradually, and show people who already have an account (Dean, ISSUE-042).
- Invitations from a school's member import, the single "Add a member" form and "Resend invite" are now sent gradually instead of all at once, so the email provider does not block them. The pace is "Bulk emails per minute" in Settings > Email (1 to 60, default 10: 500 invitations take about 50 minutes). Workspaces that share one email account share one pace.
- The import results now list every row: "Imported - new account, invitation queued", "Imported - existing account, asked to confirm", "Already a member" or "Not imported" with the reason, plus about how long the emails will take.
- Someone who already has an account is never added straight away. They get an email asking them to confirm joining the school, and join (with the role the school chose) only when they sign in and confirm; they can also decline. Until then they appear under "Waiting to confirm" on the Members page, where the school can withdraw the request. Asking again does not send a second email while the first is unanswered.
- An import never changes an existing account's name or date of birth.
- Confirming a request after already joining the school some other way changes nothing and grants no role. The package's Teacher places are checked both when someone is asked to join as a Teacher and again when they confirm.
- An address used in another workspace is shown as "cannot be used here", without saying why, and nothing is sent to it.
- Each import is recorded in the activity log with its counts (never the email addresses), as are joining and declining.
- The
org:invite-staffdry run now says what--commitwould really do with each address: invite, ask to join, skip (already a member) or fail (cannot be used here).
-
Version 2.5.0 School content: each school can have its own courses, banks, media and more (Dean).
- New "School content" switch in Settings > Features (off by default). When it is on, a course, Private Session, webinar, question bank, vocabulary theme, media file, saved section or session category made by a school's staff belongs to that school, and only that school's staff see it in their lists and pickers. Content made by the site's own staff stays site-wide as before.
- School courses never appear in the public catalogue, sitemap, AI summary (llms.txt), checkout or course pages; their direct links show "not found".
- The school's owner chooses, per course, which of the school's teachers may edit it ("Who can edit this course" on the course page). Only the owner (or site staff) publishes a school course, changes who sees it or deletes it.
- Site Private Sessions and webinars are now for the site's own staff only; school staff work on their own school's.
- Someone who works in more than one school picks the school they are working in from the name menu ("Working in"). It only narrows lists and marks new content; it never gives extra access, and it is checked again on every page so a removed teacher loses it at once.
- Site staff see an "Owner" choice when making or editing content, to make it site-wide or give it to a school; every change of owner is logged.
- A school's group admins can give their groups the school's own published courses as well as the site's courses (no seat licence is used for the school's own courses).
- Vocabulary: site staff can share a site theme with schools ("Share with schools" on Manage > Vocabulary; shared themes show a "Shared" badge, and every change is logged). A school's staff then see that theme and its words read-only and can use it in their school's courses; they cannot change or delete it. Stopping sharing takes it out of the choices, but a course that already uses it keeps it. The site's question banks are never offered to schools.
- A course bundle imported from another system arrives as site content; a copy of a school course stays the school's (its editors are chosen again).
- New command
php artisan content:assign-organisation <organisation> --user=<id>gives a school the courses and media its staff made before the switch was turned on. It shows what it would change and changes nothing unless--applyis given. - With the switch off everything works as before, except that a school's own content is still kept out of other schools' pickers and off public pages.
- The media library never lists learners' personal files (CPD evidence, assignment submissions), with the switch on or off.
Also in this release:
- Security: an Admin can no longer change a Super Admin's (or a workspace owner's) email address or send them a password reset from the support desk. Only another Super Admin can (ISSUE-090).
- Security: only the admin roles count as site staff for Private Sessions and webinars; a teacher removed from a school, or an independent course creator, manages only their own.
- Deploys put the site into maintenance mode ("back in a moment") for the few seconds of the update, instead of one visitor getting an error page (ISSUE-086).
- New
php artisan install:check: after every deploy and every morning it checks the roles are set up, an active admin exists and the licence answers as valid, and fails loudly if not (ISSUE-062). - The catalogue's "Free" badge and the "Draft" label are easier to read (colour contrast, ISSUE-072).
- The nightly database backup no longer depends on one exact minute: it is asked every hour, runs once a night in the 03:00 hour, catches up a missed night the same day, and runs in the background (ISSUE-093, ciui.co.uk's backup had stopped on 30 October).
- The demo reset now removes the reset accounts' role and permission rows instead of leaving them behind (ISSUE-087).
- A database backup is written under a temporary name, checked, and only then given its final name, so a backup cut off half-way is never mistaken for a good one; leftovers of a cut-off run are cleared on the next run. After a missed night is caught up in the day, the next backup still runs in the 03:00 hour.
- The background queue worker's lock now clears after 5 minutes instead of 24 hours, so a worker stopped by the host cannot hold up queued jobs for a day.
- The gxp.training deploy no longer stops half-way (leaving the site in maintenance) when it checks that its temporary cache-reset file is gone.
-
Version 2.4.0 Question banks from a spreadsheet (Dean).
- Question banks: a "Download the sample CSV" link with one worked example of every question type, and an "Import questions from a spreadsheet" upload. Staff fill the sheet in Excel, Numbers or Google Sheets, save it as CSV and upload it into the bank on screen, or into a new bank. Rows with a problem are skipped and listed by row number with the reason; the rest go in. Uploading the same sheet again updates those questions instead of adding them twice. Reads comma, semicolon or tab separated files in UTF-8 or the older Windows encoding.
- The empty Question Banks page no longer tells staff to run a server command.
php artisan assessment:import-banknow uses the same import rules as the upload; a one-answer or several-answers question also needs at least two answers to choose from.- Fixed: adding a question in a new category made the Question Banks page stop updating (the question only appeared after a reload).
-
Version 2.3.2 Each organisation has its own media library (Dean).
- The page builder's media picker and Manage > Media library no longer offer every file on the site to a school's staff. A school's owner, teachers and other staff see their own uploads and each other's, plus the files that belong to their own course. Learners' and parents' uploads are not shared.
- People who manage the site's content (admins, Ana) still see everything.
- Only the person who uploaded a file can delete it; colleagues can see and use it.
-
Version 2.3.1 Removed licences leave the organisation's Licences page (Dean).
- Organisation Licences page (My Organisation > Licences & seats): a removed licence now disappears from the list instead of staying as a greyed-out card marked Removed, which was confusing (Dean). The record is still kept in the database and every action still refuses a removed licence.
-
Version 2.3.0 Group names, editing accounts and accessibility at a glance (Dean).
- Rename a group: a teacher of the group (My learners > Rename) and an organisation owner or admin (the group's page > Group name). Members, courses and enrolments are untouched; every rename is in the activity log.
- Manage > Users > a user: admins can correct the name and email address, and set a password. The password is typed twice and never shown again. At their next sign-in the user must choose their own before using the site, and they are signed out of every other session straight away. A changed email address counts as verified and the old address is told. Admins cannot change their own account here (My account does that); only a Super Admin can change a Super Admin, and on on.training only the owner or a Super Admin can change the workspace owner. Setting a password also cancels any reset link already sent. Everything is in the activity log; the password never is.
- Until they have chosen their own password, nothing else on the site opens for that user (except signing out). Choosing it - here or in My account - signs them out of every other browser, so whoever used the old password is out.
- Accessibility at a glance: a learner who has changed anything in My account > Accessibility (font, text size, spacing, colours, contrast, text-to-speech, extra quiz time, or a note for their teacher) shows an Accessibility label next to their name on My learners, the group page, the organisation members list, the learner's progress page and Manage > Users. It opens to list exactly what they set. My learners also says how many of your learners use them. Shown to a group's teachers, not its overseers; on the members list, for learners only. The Accessibility page now tells learners who can see their settings, and the privacy page has a short "Your accessibility settings" section saying the same.
- Database: one new column, users.must_change_password (default off). No existing account changes.
-
Version 2.2.1 Settings > Features as cards (Dean).
- Each feature is a card, two columns on wider screens (one on a phone), with space between them.
- On/off is a slider switch with an On/Off label. It is the same setting as before and is still saved with Save features.
-
Version 2.2.0 Settings > Features grouped and explained (Dean).
- The feature switches are now in five sections: Learning, Progress and parents, Community, Website and content, and System.
- Each feature says what it does, who it is for, how it works and where to find it, and has a button straight to its page once it is switched on (VAT opens the Company tab, where the VAT rate is set).
- The switches and how they are saved are unchanged. The text lives in
App\Support\FeatureGuide; a test fails if a switch is added to Settings without an entry there, or if a button points at a page that does not exist.
-
Version 2.1.1 Privacy notice for Learner results (Dean).
- While Learner results is switched on, the privacy page gains a section "Your answers and scores in lessons": what is saved, who can see it (teachers, and - only while Progress and parents is on - linked parents: scores and answers, or scores only, following the "Parents see answers" switch), that each result is kept for one year and is included in the learner's data download. It goes before a "Changes to this policy" heading when the page has one, otherwise at the end. Switched off, the page is exactly as written. Only pages of type privacy get it.
-
Version 2.1.0 Learner results are kept for one year (Dean).
- Every night (03:50) results older than a year are deleted, on every workspace, whether or not the module is on (
learner-results:prune). - Settings and the learner page say so.
- Every night (03:50) results older than a year are deleted, on every workspace, whether or not the module is on (
-
Version 2.0.0 Learner results: teachers and parents see how a learner did on every part of a course, not just which parts are done (Dean). A major release by Dean's decision; nothing existing breaks and the module arrives switched off.
- New module Learner results: Settings > Features, and an add-on on licences and packages (Manage > Licences, Plans, Modules).
- Every attempt at the LMS's own activities is kept: the score (6 / 8), what the learner gave in readable words, and when. Activities with no right answer (memory game, hotspots, flashcards ...) are kept as done. A practice activity that checks each move keeps only whole answers; each interactive video question is kept as it is answered.
- The exercises built into a lesson's own page (the Check buttons in imported lessons) are recorded by the lesson player as the learner uses them: the score line they show, a typed answer marked right or wrong, and what the learner typed or picked. Lesson content is not changed. A running score in one visit counts as one attempt.
- Manage > Progress > a learner: each part has a Results list, with latest, best and every try. Teachers see their own learners, admins everyone.
- Parents: each course on My children opens the child's results on it. "Parents see answers" (on) shows what the child gave; off shows scores only.
- In the learner's data export, and erased with their account. On anything the learner can read (their export, the parent page), a scored activity that only ever tells the learner pass or fail still shows pass or fail, not how many parts were right; teachers see the count. The parent page shows right or wrong per quiz question only where the quiz shows its learners that.
- Kept on standard courses only, with limits per minute, per day and per part.
- Recording starts when the module is switched on; earlier attempts were never kept. Nothing is recorded in a preview or a free preview.
-
Version 1.12.0 A school's Licences page now has a Buy licences button, and the licence catalogue explains Seats and Licences (Dean).
- My organisation > Licences & seats shows Buy licences, which opens the licence catalogue (also in the side menu under Commerce > Buy licences).
- Only shown to someone who buys for that school: its own admin, once the school is approved. An admin looking at another school's page does not see it, because the catalogue buys for the buyer's own organisation.
- The licence catalogue starts with a short "Seats or licences?" note: a seat comes back when a learner leaves and can be given to someone else; a licence is used up once a learner starts a course.
-
Version 1.11.0 Admins can now edit and remove a school's or organisation's licences (Dean).
- On Manage > Organisations > an organisation > Licences, each licence has Edit and Remove (admins only; the organisation's own admin sees neither).
- Edit changes how many seats or licences it has (or makes it unlimited), when it ends (or no end date), and whether it is Seats (a released seat is reused) or Licences (each is used up when the learner starts the course).
- Learners already on it keep their place. A new end date applies to them too: a later date re-opens access that had ended, an earlier one closes it on that date. It cannot go below the number already in use.
- Seats and Licences can only be switched while none have been given out, because a seat covers every course and a licence covers one.
- Remove takes everyone off the licence and ends the access it gave. Finished courses and certificates are kept, and the licence stays listed as "Removed" with its order and invoice. Nothing is refunded.
- Every edit and removal is recorded in the activity log.
- Fix: renewing or upgrading seats no longer re-opens a webinar for a learner who was taken off it on purpose (passed, or used up their attempts). The same rule applies to a new end date.
-
Version 1.10.0 Progress now opens a full detail page for any learner (Dean).
- On Manage > Progress, click a learner's name (or "View details") to open everything they have done on the course: every module, lesson and topic, marked Done with the date or Not done, and the best quiz score beside a topic that has a quiz.
- Underneath, every attempt at each quiz and test: the date, the score and whether it passed, and, opened with a click, each question with the answer the learner gave, whether it was right, the points, and the right answer where theirs was wrong. Written answers show in full, including ones still waiting to be marked, with the marker's feedback.
- A course picker on the page switches between the learner's courses.
- Manage > Users > a learner has a "Details" link beside each course.
- Who sees what is the same as the Progress dashboard: admins see every learner; a teacher sees only learners on the courses they are assigned to. Anyone else gets "not found". It needs the Progress module switched on.
- Sign in no longer shows "Session expired" when the sign-in page was left open, restored by the browser or tapped twice: it fetches a fresh token just before sending, and an out-of-date one returns to the form (or goes straight in when already signed in). Made on ciui.co.uk by Ana's session and now part of the codebase so it is kept on every update.
-
Version 1.9.0 The System page now shows the full version history of the software (Dean).
- System (the link in every page footer) has a new "Version history" section listing every update, newest first, with its version number, date, a one-line summary and the list of what changed.
- The version installed on this site is marked "Installed version". The three newest updates are open; older ones are folded away and open with a click.
- It is read from the list of changes that ships with every update, so a new version appears there as soon as it is installed. If that list is missing the page still works, without the history section.
- The self-hosted download now includes the list of changes too (it was being left out of the download), so the history shows on every install.
-
Version 1.8.0 Learners' date of birth (Dean, P7 and P4).
- New setting "Require learners' date of birth" (Settings > Features, or Manage > Modules on on.training), off on every install until it is switched on. While it is off nothing below asks, shows or blocks anything.
- Everyone gives their date of birth when they create an account. Signing up as a parent, making a parent account from a parent invite, and registering a school or organisation each need a date of birth showing 18 or over ("You must be 18 or over to register as a parent"). A learner under 18 cannot accept a parent invite. A parent who makes an account for their child gives the child's date of birth.
- Organisations give a learner's date of birth when they add one, and the members CSV has a new
date_of_birthcolumn (YYYY-MM-DD or DD/MM/YYYY; the template includes it). A learner row with a missing or wrong date is not added and is listed by row number; the other rows are still imported. - Learners who have not given it are asked once, on their next page after signing in, and then carry on where they were going. Anyone else without one (a parent, an organisation admin, a teacher) is asked before they enrol or buy; only the site's own staff (super admin, admin, support admin, trainer, course creator) are never asked. Only the page itself is redirected, never an image, a frame, a form post or a Livewire call.
- Courses can have a minimum age (Manage > Courses > edit). A learner under it cannot enrol on or buy the course; the catalogue and the course page tell them why.
- Learners under 18 cannot buy anything: courses, licences, resources and webinar places. They see "Ask a parent or your school to buy this course" instead of the Buy button (on the course page, the free-preview lesson, the licence catalogue, resources and webinars), and every checkout address refuses them on the server too. Parents (18 or over) buy as before. Free enrolment is not a purchase and stays open (minimum age still applies). Age is worked out on the UK date and a birthday counts on the day.
- Dates in the future, more than 120 years ago or less than 3 years ago are refused.
- Privacy: the learner sees their date of birth on My account (staff correct it on Manage > Users); teachers on Manage > Progress see only "Under the minimum age" or "Age not given", never the date. It is in "Download my data", cleared when an account is erased, never in a serialised user record, and the activity log records only that it was set or changed. Only admins (Manage > Users) see it on staff screens.
- The members CSV checks a learner's date of birth before it looks for an existing account, so a wrong date is reported the same way for every address and the import still reveals nothing about who already has an account.
-
Version 1.7.0 Dean's decisions on teachers, schools and parents, and vocabulary punctuation (P2, P3, P5).
- Teachers see the learners of the courses they teach (P3). Manage > Courses > a course's builder > Teachers: admins and the course's managers assign people with the Teacher role to the course, either for every learner on it or only for the learners in one of the teacher's organisations, and remove them. Manage > Progress (and its CSV and group filter) and homework (setting it, Manage > Homework and its CSV) now show a teacher only the courses they are assigned to and, on each, only the learners it reaches. Admins still see everyone. A teacher with no courses sees "You have not been assigned to any courses yet. Ask an admin." Private Sessions keep their own rule, and the marking queues are unchanged.
- On upgrade, teachers keep what they saw on existing courses: a data migration recreates each teacher's previous reach (the 1.4.0 rule, where a teacher reached their organisation's members, or everyone when in none) as course assignments. Every account holding progress.view, homework.set or parents.manage without users.manage is assigned to every standard course of its own workspace: once for each organisation it is an active member of, or for every learner when it is in no organisation. A teacher whose memberships are all suspended or left gets none (the old rule gave them the whole workspace). The rows are marked, so a rollback removes only them; running it again adds nothing. Admins can narrow them in Manage > Courses > Teachers. Courses created after the upgrade have no teachers until an admin assigns them there.
- A teacher's assignment counts only while it still describes them (security review): one limited to an organisation only while they are an active member of it (removed, suspended or left: it stops counting), and one for every learner only while they belong to no organisation. Removing a teacher from an organisation (My organisation > Members, Manage > Organisations, the support desk) also deletes their assignments for it. A teacher who belongs to an organisation can only be assigned for one of their organisations: the Teachers screen no longer offers "Every learner" for them and picks their first organisation.
- Spoken answers: a marker hears and marks an answer only on a course they are assigned to, from a learner that assignment reaches (the same rule as Progress). A teacher removed from or suspended in their organisation no longer reaches every child's recording in the workspace. A Marker role, which cannot be assigned to courses, reaches no spoken answers; admins still reach them all. Livewire's temporary copy of a recording is deleted as soon as it is sent or refused, and rolling the release back deletes the recordings (rows and files) with the tables.
- When a teacher sets homework for a group, members who are not on the course are now counted ("1 person who is not one of your learners") rather than named, as they are not the teacher's learners there.
- Homework a teacher set on a course they no longer teach leaves their Manage > Homework list and CSV; admins still see it.
- Schools link their own parents (P2). An organisation admin can invite a parent for, and remove the parent links of, the learners who are active members of an approved organisation they run: My organisation > Members > Parents. New permission
parents.manage_org(organisation admins). Staff are never linked, every new link is still emailed to the learner and their other parents, and the daily invite limits still apply. Workspace admins keep full access. Nobody can invite their own address as a parent, a staff account (any role besides learner and parent roles) can be neither invited nor accept, and a personal organisation never counts as one an admin runs. - Vocabulary: question and exclamation marks now count (P5). Updates the 1.3.0 rule that ignored all punctuation around a word: "¿Qué tal?" needs its ¿ and ?, and "¡Hola!" its ¡ and !. A missing, extra or misplaced mark is wrong; when it is the only mistake the learner sees "Nearly - check the punctuation", like the accent message. Full stops, commas, semicolons, colons, quotes and brackets around a word are still ignored, and a space before ? or ! (as typed in French) still counts as the same answer. Fullwidth ? and ! count as ? and !. Word lists stored without their ¿ ? ¡ ! (for example "Qué tal" for a question) now mark a learner who types the marks as "Nearly - check the punctuation": add the marks to those words in the vocabulary bank.
-
Version 1.6.0 Spoken answers (Dean, L3).
- New module "Spoken answers" (Settings > Features, or Manage > Modules on on.training), off on every install until it is switched on.
- New activity "Spoken answer", for any course (a course can be made only of these): in the Page builder's Activities, or as a "Spoken answer (marked)" topic. The teacher asks in writing, as audio (uploaded or recorded in the editor) or both, with optional instructions, the longest answer allowed (2 minutes unless changed, up to 5) and the mark it is out of (10 unless changed). It counts toward completing the topic unless the teacher switches that off.
- Learners record their answer in the browser (iPhone Safari and Chrome alike), listen back and record again as often as they like, or choose an audio file (mp3, m4a, wav, ogg or webm, up to 10 MB). Nothing leaves the device until they press Send; after that the answer is locked until the teacher returns it. They see whether it is sent, marked or returned, with the teacher's mark and comment.
- Teachers mark spoken answers in Manage > Marking, alongside assignments, for the learners they can reach (the same rule as Progress and Homework). They listen, give a mark and a written and/or recorded comment, and accept it (completing the topic) or return it for another try. The learner is told in the app and by email.
- Homework on a spoken-answer topic is done when the answer is accepted, judged by when it was sent.
- Recordings are private: only the learner, the teachers who can reach them and admins can play them, through short-lived links; parents cannot. They never appear in the media library. They are in the learner's "download my data" export, and are deleted (with the teacher's recorded replies to them) when the learner's deletion request is approved. When a teacher's account is deleted, their replies stay with the learners.
- In author preview and free preview, learners can record and listen back, but nothing is sent or saved.
-
Version 1.5.2 Payments: each site only acts on its own Stripe checkouts.
- Several sites can share one Stripe account (ciui.ro and ciui.co.uk do), and Stripe sends every payment event to every site's webhook. A payment made on one site could have enrolled the person with the same account number on the other. Every checkout now records which site created it, and a site ignores any checkout that is not its own, on the webhook and on the return page.
- Checkouts created before this update are judged by the page they return the buyer to, so payments already in progress still complete.
- The buyer is now sent to Stripe as
buyer_id(wasuser_id), so a site on an older version that shares the Stripe account ignores the newer site's checkouts. - A checkout ignored for belonging to another site is noted in the log, and
www.and the bare domain count as the same site.
-
Version 1.5.1 Fixes.
- A page link whose query value does not fit the page (for example
?topic=abcon the lesson player, or a text category on the course catalogue) no longer shows an error page: the visitor goes to the same page without it, and it is not logged as an error. Seen live on ciui.co.uk. - Every log entry written during a web request now names its method and path (never the query string), so an out-of-memory error says which page caused it.
- A homework test that could fail on a slow machine now fixes the clock.
- A page link whose query value does not fit the page (for example
-
Version 1.5.0 Set as homework (Dean, A3).
- New module "Homework" (Settings > Features, or Manage > Modules on on.training), off on every install until it is switched on.
- Manage > Homework > Set homework: choose a course, one of its topics (a lesson topic, a quiz, an activity or a vocabulary block), the learners and/or a group, a due date and time and an optional note. Teachers can set it for the learners they can reach (the same rule as Progress and Private Sessions) who are enrolled on the course; anyone else is skipped and the teacher is told who. New permission
homework.set(teachers and admins). - Manage > Homework lists the homework a teacher set (admins see all of it), filtered by course, group and status, with each learner's status (due, overdue, done, late) and a CSV download. Teachers change the due date and note, or cancel it.
- Learners see a Homework panel on their dashboard: overdue, due soon and recently done, each opening the topic in the course. It is done when the topic is completed after it was set (for a quiz, when an attempt is submitted), and marked late after the due date. A topic finished before it was set shows a "Mark homework done" button.
- Emails: one to the learner the day before it is due and one when it is overdue; linked parents get the overdue one too. Each is sent at most once, never for done or cancelled homework, and anyone can turn them off from the link in the email (learners also from their dashboard).
- Manage > Progress shows each learner's homework due, overdue and done, and My children shows each child's homework.
- Homework is in the "download my data" export and is removed when a learner's deletion request is approved. When a teacher's account is deleted, the homework they set stays with their learners.
- Due dates and times are typed and shown in UK time (Europe/London) on every install, in emails too, the same as live sessions and webinars.
- A learner whose work for the topic's assignment is already handed in (waiting for marking or accepted) is skipped when the homework is set and named as "already handed in". If such work predates homework that already exists, the player says "Already handed in before this was set" instead of showing a button that cannot work.
- Moving homework's due date clears both of its reminders, so the new due time gets its own due-soon and overdue emails, and linked parents get the overdue email again if it goes overdue again. Cancelled homework still gets none. (Default chosen in review; it can be changed.)
- Late is worked out against the due time at the moment the homework is handed in, even if a teacher moves it at the same time.
- A topic completed again keeps its first completion date (so it is not rewritten), and "Last active" on Manage > Progress now follows the latest completion.
- Fix (1.4.0 parents, never released): the expiry of a parent invitation and of a parent account claim is now a DATETIME. As a TIMESTAMP, MariaDB servers older than 10.10 would reset it to "now" whenever the row was updated.
-
Version 1.4.0 Progress dashboard and parents (Dean, L4).
- New module "Progress and parents" (Settings > Features, or Manage > Modules on on.training), off on every install until it is switched on.
- Manage > Progress: choose a course to see each of your learners' progress, topics done out of the total, when they were last active, and the best and latest score of every quiz and assessment. With Vocabulary on it shows the words each learner has due. Filter by group or by learner, and download the filtered view as a CSV file. Teachers see the learners they can reach (the same rule as Private Sessions: their organisation's members, or everyone when they are in no organisation); admins see everyone. Free-preview visitors, who are not enrolled, are not shown or counted. New permission
progress.view(teachers and admins). - Parents: a learner (Account > My parents) or an admin invites a parent by email. The parent creates an account from the link, or signs in if they have one; the link works once and lasts 7 days. Learners and admins can remove a parent link (new permission
parents.manage, admins only). - Registration has an "I'm a parent or guardian" option. A parent can create a learner account for their child with the child's own email address. The parent never sets or sees the password: the child gets an email saying who made the account, and either chooses their own password and accepts, or says "this wasn't me" and the account is deleted. Until the child accepts, the account cannot sign in and the parent sees nothing of it; an account nobody accepts is deleted when the 7-day link expires. Up to 10 a day per parent and 50 a day per site.
- My children: each linked child's courses, progress, recent scores and last activity, for the parent's own children only.
- A weekly summary email to each parent on Monday mornings, about the last 7 days, with a link to stop it (also a switch on My children).
- Parent links and invites are in the "download my data" export of both the parent and the child, and are removed when either one's deletion request is approved. Deleting a parent does not delete their children's accounts (only accounts the child never accepted).
Security review before release (safeguarding first; many learners are children):
- Every new parent link is emailed to the learner and to every parent already linked, saying who was linked and how to remove it.
- Only learner accounts can have parents linked: staff accounts are refused, when the invite is sent and again when it is accepted.
- Parent invites are capped at 100 a day per site (20 per person). Email subjects never contain names typed by users.
- The activity log records ids for parent invites and links, not children's names.
- Parents see only standard-course activity: Private Session plans and webinars are not shown.
- On the progress dashboard a teacher in an organisation is only offered their own organisation's groups.
- Two parent invites open in two browser tabs now both work.
- The new tables' migration rolls back cleanly on MariaDB.
Security re-audit follow-up:
- A parent-created account is only ever deleted (when its link expires, when its owner says "this wasn't me", or when the parent is erased) if nothing else has been added to it. Otherwise its link is closed for good and the account is kept, and admins see a note on the learner's Parents page and in the activity log. The nightly clean-up carries on past a failure, and reports it.
- An account that was made staff before its owner accepted is activated as their own account, with no parent linked.
- An address whose owner said "this wasn't me" cannot be used for a learner account by that parent again, or by anyone for 30 days. Only a fingerprint (hash) of the address is kept.
- "Forgot password" on an account still waiting for its owner sends a new activation link (the old one stops working). The page's answer is the same as for any other address.
-
Version 1.3.0 Vocabulary word bank and daily review (Dean, S3).
- New module "Vocabulary" (Settings > Features, or Manage > Modules on on.training), off on every install until it is switched on.
- Manage > Vocabulary: one word bank in Spanish, English, Romanian and French. Each word is typed once per language, so its translations stay together, and sits in a theme (Family, School, Food ...) and a tier (Foundation or Higher). Words are kept exactly as typed, accents included. Teachers, course creators and admins can add, edit and delete words, themes and translations (the new
vocabulary.managepermission). A spelling that learners are reviewing cannot be cleared from a word (that would silently drop it from their review); correct the spelling instead. - Every word can have audio in each language: upload an mp3, m4a, wav, ogg or webm file (up to 5 MB) or record it in the browser. With an ElevenLabs API key in Settings > Vocabulary, a "Make audio" button records it for you. The key is stored encrypted and never shown again. "Make audio" is limited to 30 words an hour per teacher and 200 an hour per workspace, so a stuck button or a refused key cannot run up the ElevenLabs bill.
- In the course builder, Vocabulary chooses the language learnt, the language of the translations, and the themes and tiers the course uses. A new Vocabulary block in a topic shows those words with their translation and audio, as a word list, flashcards, and a type-the-word check.
- Accents count, as at GCSE: an answer with a missing or wrong accent shows "Nearly - check the accent" and is marked wrong. Accent buttons under every answer box type the letter where the cursor is.
- Marking ignores what is not part of the word: curly apostrophes (as phones type them) count as straight ones, any spacing counts as one space, and punctuation around a word is ignored, so "qué tal" is right for "¿Qué tal?". Apostrophes and hyphens inside a word still count ("aujourd'hui", "porte-monnaie"). This punctuation rule is a default chosen for Dean to confirm.
- Daily review: the words a learner meets in a lesson come back on a new review page, linked from the dashboard ("12 words to review today"). A right answer brings a word back after 1, 3, 7, 14 and then 30 days; a wrong one brings it back the next day and starts again.
- Previews save nothing: an author's preview and a free preview add no words to anyone's review. The learner's review record is in their data download and is deleted when their account deletion is approved.
-
Version 1.2.1 on.training pricing wording (Dean).
- The package cards say "All included" instead of "All 7 included", and the self-hosted card says "every activity" instead of a count, so adding a module no longer changes the wording.
-
Version 1.2.0 Free preview lessons (Dean, S1 and Q6).
- New module "Free preview lessons" (Settings > Features, or Manage > Modules on on.training), off on every install until it is switched on.
- In the course builder of a paid course, a "Free preview" tick on each lesson (every topic in it becomes free) and on each topic (that topic on its own). Not offered on Private Session plans, webinars or free courses.
- The course page marks the free lessons "Free" with a "Try it free" link. A visitor first creates a free account (or signs in) and is then taken straight to that lesson, so every free preview comes with an email address.
- Someone who is not on the course can open only the free lessons, under a banner with the course's buy button. Nothing they do there is saved: no enrolment, progress, quiz attempts, completion or certificate.
- A free lesson keeps the course's assessment rules: a main or module assessment, or a quiz that draws from a question bank, shows "Buy the course to take this assessment" instead of its questions; other quizzes show the score but never the answers, and accept at most 5 tries a minute; scored activities keep their limit on attempts per minute.
- If a topic is unticked while someone has it open, they move to a lesson that is still free (or the page closes when none is left). Someone who buys the course while a free lesson is open is taken back in as a learner, so their work is saved from then on.
-
Version 1.1.0 Course reviews (Dean, "S2, yes please").
- New module "Course reviews" (Settings > Features, or Manage > Modules on on.training), off on every install until it is switched on.
- A learner on a course can give it 1 to 5 stars and an optional short comment, once per course. They can edit it; an edited review is checked again.
- Nothing shows until someone with the new
reviews.moderatepermission approves it on Manage > Reviews (given by default to the roles that moderate the community). Each approval or rejection is recorded in the activity log. - The course page shows the average rating, the number of approved reviews and the reviews themselves (first name and initial only), and adds the rating to the page's structured data for search engines.
-
Version 1.0.0 First full release (Dean, Discord 1566386747523334224).
- System page (
/system): software version, credits (Dean Ciui and Claude, by Anthropic) and a "Report a technical issue" form that goes to the system's technical contact (dean@ciui.co.uk) on every install. - Every footer links to the System page with the running version.
- The version comes from the
VERSIONfile and is also what the install reports in its daily licence check with on.training. - Baseline: everything on main at this release, including ciui.co.uk's live-only edits merged on 2026-11-01.
- System page (
Report a technical issue
Something not working as it should? Tell us what happened and which page you were on. This goes straight to the system's technical contact. For questions about a course, please contact Training System instead.