QR code login
QR code login lets a pupil sign in without typing a username or password: they present their personal QR code to the webcam on the sign-in screen, and it logs them straight in. It's aimed mainly at younger pupils who can hold up a card or badge far more easily than they can type a password.
Before you start
- You must be an admin for the school with the Manage users & groups permission — or a teacher the school allows to reset passwords, who can do everything from Step 2 onwards from the Reset passwords page instead (see Teachers: QR codes from the Reset passwords page).
- QR code login must be turned on for the school before anyone can generate codes — see Step 1.
Step 1: Turn on QR code login
Go to School settings → QR login and turn on Enable QR code login, then save. This is a separate tab from the Password settings page — see Password settings.
Once it's on, a QR codes menu appears in the bulk-actions bar on the Users page (and on the Reset passwords page — see Teachers), and a QR code column becomes available (see Customise columns) showing at a glance which users already have a code.
Step 2: Select the pupils to generate codes for
Go to Users, filter down to the pupils you want — a class, a year group, or any other selection — then select them and open the QR codes menu in the bulk-actions bar.
Step 3: Generate and print
- Generate QR codes — creates a code for any selected user who doesn't already have one. Anyone already holding a code keeps the same one.
- Print QR codes — does the same generation (fills in a code for anyone who doesn't have one yet), then opens a print view with every selected user's current code, ready to print onto badges, stickers, or cards for distribution.
Because both actions work on whatever you've selected, you can distribute by class or year group simply by filtering and selecting that group before printing.
The printed cards come out in registration group order, alphabetical by surname within each group, and each registration group starts on a new page — so a whole-year batch comes off the printer already split into classes, ready to hand to each form tutor. Users with no registration group, such as staff, print at the end.
Large batches — a whole year group or the whole school
There's no limit on how many pupils you can do at once. A big batch takes a while — each code is an image that has to be created and stored — so a progress bar appears above the list showing how far it has got.
- Keep the page open until it finishes. If you navigate away or close the tab, the run stops.
- Nothing is lost if it does stop. Every code created up to that point is already saved. Run the same action again on the same selection and it picks up where it left off — Generate QR codes skips anyone who already has one.
- Printing a very large batch opens a print window with every card in it, which your browser may take a minute to lay out. If you only need one class at a time, filter to that class first.
Step 4: A lost code: regenerate, don't reprint
If a pupil loses their card or badge, don't just reprint their existing code — anyone who found the original could still use it to sign in as that pupil. Instead:
- Delete & regenerate QR codes — replaces the code for every selected user with a brand-new one, immediately invalidating whatever they had before. Use this for the pupil(s) who lost their code, then print and distribute the new one.
This is different from Generate QR codes, which leaves an existing code untouched — regenerate is the action that actually invalidates a lost code.
Removing codes
Delete QR codes removes the code from the selected users entirely, with no replacement. Use this if you want to withdraw QR sign-in from someone without issuing them a new code. On the Users page it runs straight away and shows QR codes deleted., so check your selection first; on the Reset passwords page you're asked to confirm.
Where pupils scan their code
Once QR code login is on, the school's Realsmart sign-in page shows a QR login button under Sign in. The pupil selects it and holds their code up to the camera. Codes scan best when they're printed on a white background. Signing in this way never asks the pupil to change their password.
On Chromebooks, the sign-in screen only opens the Realsmart page, and only lets it use the camera, once a few settings are made in the Google Admin console. See Make Chromebooks sign in with Realsmart.
Teachers: QR codes from the Reset passwords page
Teachers don't have the Users page, but if the school allows them to reset passwords, the Reset passwords page in their sidebar carries the same QR codes menu once QR login is on. From there a teacher can print, generate, replace (Delete & regenerate) or delete codes for the learners on that page — never for staff — using exactly the actions described above. The QR code filter on that page finds the pupils still without a code. See Reset passwords → QR login codes for the step-by-step.
Result
Selected users' QR codes are created, replaced, or removed as chosen. The QR code column on the Users list (see Customise columns) shows who currently has one.
Troubleshooting
The run stopped part way through. You'll see QR generation stopped part way through. Anything already generated is saved — run it again on the same selection to finish. Nothing is lost: the codes already created are saved. Repeat the action on the same selection to finish the rest.
Some codes couldn't be uploaded. The message ends … could not be uploaded — select those users and try again, with how many. Select those pupils again (filter the QR code column for users without a code) and run Generate QR codes once more.
"The print window could not open." Allow pop-ups for the site, then choose Print QR codes again. The codes are already generated and saved.
"QR Code is invalid". The code isn't one the school has now — it was replaced with Delete & regenerate QR codes, deleted, or never printed from this school. Print the pupil's current code.
A code scans but the pupil isn't signed in. A pupil whose account is locked after wrong passwords (Too many sign-in attempts), outside their login hours, or during a holiday pause is refused, with a message, even with a valid code.
Related
Did this work for you?
If a step looked different on your site, tell us and we'll update the screenshots.
Thanks for your feedback.