A site of its own
Each client, branch or team gets a site at its own address, with its logo and colours on every page, email and certificate.
Features
Making a course, giving it to the right people, and seeing who has finished, with every feature and question in one place.
Create
Set up a site for each client, branch or team. Then upload the courses you already have, or build new ones in the composer.
Each client, branch or team gets a site at its own address, with its logo and colours on every page, email and certificate.
Make a course in your browser from slides, video, pictures, PDFs and quizzes. Anyone on your team can, starting from a template.
Upload SCORM 1.2 or 2004, cmi5 or xAPI from Storyline, Rise, Captivate or any other tool. Each upload is checked before anyone sees it.
Every course waits as a draft until a site admin has played it through and approved it.
Change a course and build it again. Each version is kept, so you can see what changed, and go back.
Share projects and templates with other authors, and copy an approved course to another of your sites.
No course yet?
Anyone you trust can be a course author: a team leader, a trainer, or the person who wrote the policy. They build courses in the browser from what they already have, and an admin approves each one before anyone sees it.







And when you want more Branching and learner pathways, question banks, questions inside a video, the course map, shared templates, and uploading from Storyline or Rise.
Assign
Bring your people in, put them in groups with their own managers, and give each group its courses.
Every account uses one seat. When someone leaves, remove them and their seat is free for the next person straight away.
Upload a spreadsheet and see a preview before anything changes, connect your work sign-in and directory with the SSO add-on, or use the API.
People confirm their email once, then sign in with a code, or their work account through the optional SSO add-on. Site admins, managers, authors and people from outside add a second step.
Give each team, site or customer its own managers. They add people, give courses and follow progress, and see only their own groups.
Add people from outside with a start and end date. Their access stops on the last day, checked every time they visit.
Give a course to many groups at once, due on a date or a number of days after each person joins, with reminders and renewals.
Deliver
Learners sign in at their site’s address and take their courses on any device. The client sees who has finished, and every pass gives a certificate that proves it.
Learners sign in at your address with an emailed code, or their work account through the optional SSO add-on, on any phone, tablet or computer.
Courses save as they go. Start on a phone at lunch, and finish on a laptop later.
Every page and email is ready to translate. Today they’re in English, and as more languages are offered, each person picks their own.
Emails before a course is due, on the day, and every week while it’s overdue. Managers get a weekly summary.
See who has finished at a glance. Download reports as a spreadsheet or PDF, or have them emailed every week or month.
Every attempt, score and certificate is kept for 3 years, unless you choose anything from 1 to 10.
What a learner sees first: each course with its due date and progress, ready to carry on.
Its lessons, each ready to start or carry on, on any device.
Who’s done, who’s in progress and who’s overdue, by group and by course.
Proof of training
When an auditor asks for proof, a printout is easy to question. TrioLMS gives every certificate and transcript a way to be checked.
Runs on TrioLMS
Your client’s site runs on TrioLMS. That’s the point: you don’t run servers, and they get a platform that’s looked after.
Roles
Each person sees what their job needs, and nothing more.
Everyone gets a short TrioLMS training course for their role, given automatically.
For the technical people
Everything an agency’s developer or a client’s IT team will ask about. There’s more in the technical deployment guide.
Features
Every feature, in plain words. It lists only what’s built and working today.
Type a word, such as certificate or spreadsheet.
No feature matches that.
Questions
Asked the way people ask them in e-learning forums, and answered with what TrioLMS does about it.
A training site of its own, at its own address, such as acme.triolms.com or the client’s own domain. Each has its own people, groups, managers, courses and records, kept apart from your other sites, and its own share of your seats.
You buy a pool of seats. Every account in a site uses one seat from the moment it is added. Remove someone who has left and their seat is free straight away for the next person; their training record stays, read-only, for the audit period.
No. Each site carries your client’s logo and colours, and can have their own address, but the TrioLMS name still shows in places, such as the training course everyone gets and the certificate check at triolms.com/verify. We’d rather say so up front.
Everyone gets a short TrioLMS training course for their role, given automatically. Your TrioLMS administrators and site admins can send us a request from the support form in the app, and anyone else can email hello@triolms.com.
Give them a site of their own at their own address. Upload the course once and add their people. They sign in and take it, you see who has finished, and they never need an LMS.
No. Learners sign in at the site’s address and the course plays there.
Clients never get the package, and the course files are only served to signed-in learners, from a separate address.
They never had the file. Give the course a last day, or end their access, and it stops opening for them. Their records are kept.
The file doesn’t need to. In TrioLMS a course can have a last day, and each certificate an expiry date.
Yes. TrioLMS bills you, and you charge your clients as you choose: a set-up fee, a monthly fee for each site, or course updates.
No. You sell to them as you do today. TrioLMS bills you for your account, and you share out its seats.
Give the company its own site with the number of seats it bought. Their site admin adds their staff, and you can see the take-up.
Publish your courses again as SCORM, cmi5 or xAPI from your authoring tool, and upload them. Each is checked and previewed, then approved like any other course.
A browser on a phone, tablet or computer. There’s no app and no password: they sign in with a code sent to their email, or with their work account through the optional SSO add-on.
Remove them, and their seat is free for the next person. Their record is kept.
Each site shows its seats and every learner’s progress.
No. A manager sees only the groups they manage. Course authors never see learners’ data at all, and each site is kept apart from every other.
Yes. Add them as external accounts with a start and end date, or give them a site of their own.
Yes, with single sign-on, an add-on, which can also keep your people in step with your directory.
No. Spreadsheet files need nothing but a browser, and nothing changes until you’ve seen a preview. Work sign-in and directory sync are there as an add-on when you want them. See every way to set up people
In the region you choose, the UK and EU or the US. All of a site’s records and files stay there, and people’s names and email addresses are encrypted with the site’s own key.
Yes. Start from a template, drop in your content, add a quiz and press Build. TrioLMS checks the course before it’s built, and a site admin approves it before anyone sees it.
No. The composer is part of TrioLMS and runs in your browser. If you already use another tool, upload what you make in it.
Videos with captions, sound, pictures, PDFs, slides you write in TrioLMS, quizzes and surveys.
Yes. Make anyone a course author. They can build and upload courses, but never see anyone’s results.
Every course waits as a draft until a site admin approves it, and a site admin can send it back with a note.
Yes. Your logo and colours go on every course, and site admins can publish house templates for everyone to start from.
Each certificate has a code and a QR code. Anyone can check it at triolms.com/verify.
For each site’s audit period: 3 years, unless you choose anything from 1 to 10.
No. Every site has a learning record store built in, for xAPI 2.0 and 1.0.3, and it’s checked against ADL’s conformance test suite.
TrioLMS plays cmi5, and is checked against the official cmi5 test suite on every change. Courses built in the composer are cmi5 too, so they also play in any other cmi5 LMS.
Yes. Additions start at once, and you pay now only for the time left until your next billing date.
Lower them from your account. Reductions start at your next billing date and aren’t refunded; save one at least 24 hours before that date. You can’t go below what’s in use.
Close it from your account, as long as it isn’t your last site, at your next billing date. Pause it and everything is kept, its seats included, and still charged; restart it whenever you like. Archive it, or delete it for good, and you choose whether its seats stay in your pool for another client or come off your bill. An archived site costs nothing and keeps its records, read-only, for its audit period. Keep its courses in your account’s course library, or copy them to another site, before it closes.
14 days of the basic setup: 5 seats, one site and 1 GB of course storage, with a card. You can’t add seats, sites or anything else during the trial. Buy at any time in two clicks and you have 5 seats, one site and 10 GB, then add whatever you need. If you don’t, the account closes when the trial ends and is kept for 14 days in case you change your mind.
Everyone added to a site: learners, admins, managers, course authors and people from outside, including your own staff in each client site they manage. The account owner uses none until they’re added to a site.
US dollars, euros in the eurozone and pounds in the UK, with tax added at checkout. You keep the currency you first paid in.