You are a training manager

What that means, and the four things you will actually do.

We are moving compliance training off Lessonly and onto our own system. It holds the same courses and the same completion history, and it runs on our own network at compliance.ifs.com.

You are being asked to look at it before anyone else does. Not to approve it — to try to break it, and to tell us what is confusing. If something looks wrong, it probably is, and we would much rather hear it now than after 128 people are using it.

Signing in

Use your email address and your password, then your second factor. There is no separate username to remember.

If you work on the call floor

You sign in with your security key — the YubiKey you already use for everything else. Touch it when the browser asks. No code will appear, and registering it here does not change how your key works on any other system.

Phones are not permitted on the floor, so floor and Redial accounts cannot use an authenticator app at all. That is deliberate.

Everyone else

An authenticator app or a security key — whichever you prefer. You can add the second one later from Preferences → How I sign in, and you never have to.

Lost your only key or phone? There is no self-service route back in, by design. Ask whoever administers training — they can reset you from the console now, and you will get a fresh link and set everything up again. A reset clears everything: your password, your authenticator and every security key you have registered. Your courses, due dates and completions are untouched.

What you are responsible for

Your group's training. Specifically:

Knowing who is behind. Your group page shows every person and what they owe. If you are set as the group's owner, you also get a weekly email listing anyone overdue.
Chasing it. The system records; it does not nag on your behalf. No reminder, digest or escalation is going out — those are held at the server during the pilot, so nothing is reaching your people unasked. Sign-in links are the exception and are deliberately separate: when somebody issues you or your team a link, that one email does go. Nothing else does.
Assigning the odd extra course. Most training arrives on a schedule and you do not touch it. Occasionally you will give one person one course — that is a one-off, and it shows on the Schedules page so it does not get forgotten.
Telling us what is wrong. Wrong question, wrong answer marked correct, course that does not apply to your team, wording that will confuse a new starter. All of it is worth reporting.

Four things on the screen that are easy to miss

A person's groups are on their panel. Open anyone and the Access tab lists every group they are in, including the automatic ones. Click a group to open it. Most training arrives through a group, so this is usually the answer to “why does she have that course”.
Each course on a person says where it came from. There is a Source column: a group, the schedule, or assigned directly to them.
The Attention board states its own rule. Under the toolbar it says how many failed attempts put somebody on the list. You do not have to go hunting in Settings, and you do not need permission to read it.
Learners can flag a passage they think is wrong or unclear, straight from the lesson. Flagged courses show a count in Reporting and on the course list, so a bad question surfaces as a number rather than as a rumour.

What the system does on its own

Opens each scheduled course in its window and closes it at the due date.
Keeps every attempt, score and completion, including the history imported from Lessonly.
Issues a certificate for a completed course.
Gives every learner their own record — My record on their sidebar — as a table they can sort, search and print. That is the page to point somebody at when they ask what they have done.
Tracks who has not finished, and will escalate to you once learner email is switched on.

What it deliberately does not do

It does not let someone retake a course they have already passed. Completion cannot be improved, and a fresh failing attempt would make a finished person look unfinished.
It does not wipe prior completions when a course is corrected. Fixing a typo does not make 118 people retake anything.
It does not let you see another manager's people unless you have been given that scope.

Trying to break it

Please do. The things most worth poking:

Take a course the whole way through, deliberately fail the quiz, then retake it.
Open a course on your phone and on a desktop.
Look at your group and ask whether the numbers match what you know to be true. They are the numbers an examiner will be shown.
Use the search. Try to reach something you should not be able to see.

How to tell us — use the button, not email

Report a problem is in the sidebar of every page, on the learner side and in the console. Click it, pick whether it is a bug or a feature request, and say what you expected and what happened instead.

Why the button rather than a message to the CIO

It sends the page you were on and any errors your browser recorded. You do not have to describe those, and they are usually the part that identifies the fault.
It lands in the same queue the compliance app uses, so there is one place to look and one place to triage. Nothing gets lost in somebody's inbox.
It is tracked. Reports have a status, and you can see what happened to yours. An email cannot say "fixed in 0.470.0".

A screenshot is still welcome. Send that however you like — but file the report first, so there is something to attach it to.

Feature requests are not a lesser category. "I would expect to be able to…" is exactly as useful as "this is broken", and the same button takes both — change What is this? at the top.