Everything you need
to run the lab.
Plain-language guides for every role. The flow is simple. Tap a PC first, sign in once if you're new, and your session activates. Tell us who you are below.
The 30-second version
If you read nothing else, read this.
Tap first
Touch the tag on any PC. It opens Lab Nexa and knows exactly which seat you're at before you even sign in.
Sign in once
If you're not logged in, sign in once. After that first sign-in, every future tap is instant.
You're live
Your session activates, your seat glows on the map, and everything records itself.
Quick start
Tick these off as you go. Your progress is saved on this device.
Tap the PC
Touch the NFC tag on any PC. Lab Nexa opens and identifies your seat.
Sign in (first time)
If asked, sign in once. Later taps skip this step entirely.
You're active
Your session starts, your seat glows, and your time is tracked.
How a tap works
Follow the orange dot. Tap first, sign in once, then you're live.
You tap
Card or phone touches the tag
NFC tag
Says "I am PC-07"
Sign in
Only if not logged in yet
Activates
Seat claimed, timer starts
Live everywhere
Map and monitor update
Guides by role
Your day, in four steps. Pick your role.
Student
"I just want a working PC and proof I was here."
- Tap the tag on any PC. Lab Nexa opens and identifies your seat.
- Sign in if asked. First time only. Later taps are instant.
- Work. Your session is active. The timer runs in My Sessions.
- Tap out when you leave so the seat frees for the next person.
- Something broken? File a complaint from that exact PC.
- Your history equals your attendance proof. Export it anytime.
Lecturer
"I need the room open and I need to see who's in it."
- Tap the Main PC to open the lab for your class.
- Watch the monitor. Names, seats and durations, live.
- Review complaints. Approve real faults, deny the rest.
- Close the class from the monitor when you're done.
- Export a class summary for your records in one click.
- Check Lab Availability before you book a room.
Supervisor
"I keep the machines alive and the map honest."
- Pair tags to PCs when new machines arrive.
- Test a tap after pairing. The seat must flip to busy.
- Mark broken PCs red so nobody wastes a tap on them.
- Resolve tickets that route to you. Escalate what you can't fix.
- A red seat with no ticket? Mark it broken directly.
- Clear orphan sessions after a power cut.
School Admin
"I run the building and I need to know what to fix first."
- Create labs and assign a supervisor to each.
- Read the priority board. Highest score means fix first.
- Watch analytics for utilisation and peak hours.
- Download reports for your school each term.
- The priority board mixes usage plus complaints, so it's fair.
- Review the school complaint queue weekly.
University Admin
"I onboard hundreds of people and own the campus numbers."
- Bulk-import cohorts with the Excel template.
- Manage schools and the users inside them.
- Read campus reports for utilisation and complaints.
- Suspend or reactivate accounts as needed.
- Excel import default password equals IC number. Users change it on first login.
- Audit logs show every change, by whom, when.
Platform Admin
"I run the whole network of universities."
- Provision universities and their first admins.
- Monitor health across all institutions.
- Handle escalations that schools can't resolve.
- Read platform audit for compliance.
- Deletions have a 1-hour grace period. Recoverable.
- Cross-university stats live on your dashboard.
NFC tag setup
One tag per PC. Four steps from box to live.
Rule of thumb: if a seat behaves wrongly, it's almost always a pairing problem, not a hardware problem. Re-pair first.
Encode
Write the tap URL (below) with any NFC writer app.
Stick
Fix to the PC bezel at tap height, right of the monitor.
Pair
Supervisor: My Labs → PCs → Pair tag. Binds tag to seat.
Test
Tap with a test account. The seat must flip to busy.
https://labnexatechnologies.com/nfc/tap.php?tag=TAG_IDfull_name,ic_number,email,role_name,school_name,status| Problem | What it means | Fix it like this |
|---|---|---|
| Tag not reading | Tag unpowered or metal blocking it | Re-stick on plastic away from metal. Re-test. |
| Wrong PC opens | Tag paired to the wrong seat | Unpair and re-pair under My Labs → PCs |
| Two seats light up | Same tag ID written twice | Re-encode one tag with a fresh TAG_ID, re-pair |
| Session won't end | Tap-out missed or NFC off | Tap again, or supervisor ends it from monitor |
| Seat stuck "busy" | Orphan session after power loss | Supervisor: clear orphan sessions |
Reading the lab map
Four colours. That's the whole language.
Green equals free
Sit here. Tap to claim it.
Dark equals busy
Someone's session is running.
Orange equals fault
Broken. Don't waste a tap.
Ringed equals you
Your current seat, highlighted.
Complaints, simply
Built so nobody routes a ticket they regret.
Two safety windows: you can cancel for 15 minutes after filing, and there's a 30-minute undo after approval. Only then does it route.
You file it
From the exact PC. The tag pins the ticket to that seat.
Cooling-off
Changed your mind? Cancel here. Most faults fix themselves.
Lecturer reviews
Approve real faults, deny the rest, with a reason.
Undo then route
Undo closes, then it auto-routes to the right fixer.
LN Intelligence
The system reads the week for you. Three outputs, zero effort.
Weekly digest
A plain-English summary of the week, written every Monday 06:00.
Anomaly watch
Flags weird patterns before they become problems.
Priority score
Usage plus complaints per lab. Highest gets fixed first.
Reports and exports
Every admin role gets the reports it actually needs.
| Role | You get | Export |
|---|---|---|
| School Admin | Utilisation, peaks, priority, complaints | Excel |
| University Admin | Campus utilisation plus cohort reports | Excel |
| Platform Admin | Cross-university stats plus audit logs | Excel |
Security and privacy
In plain words: who can see what, and how it's protected.
Only your role
Six roles, strict permissions. You only ever see what your role is allowed to see.
Passwords are safe
Stored hashed (bcrypt). New imported accounts must change password on first login.
Data stays put
Each university and school is partitioned. Every change is written to an audit log.
Frequently asked
Short answers to the questions we hear most.
No. Any NFC-capable phone reads the tag in the browser, or use a physical NFC card. Nothing to install.
Tap first. The tap opens Lab Nexa and identifies your seat. If you're not signed in, it asks you to sign in, then your session activates. After the first sign-in, taps are instant.
Your session keeps running on the PC. Tap out with a card, or ask the supervisor to end it from the monitor.
A seat holds one active session. A second tap ends the first and starts the new one. The ledger always shows who had it, and when.
You, your lecturer (class scope), and admins (audit scope). Never shared across institutions.
University Admin → Users → Excel bulk import. One row per student. Default password is the IC number, changed on first login.
Supervisor can mark it broken directly. It turns red on the map immediately so nobody wastes a tap.
Yes. Within the 15-minute cooling-off. After approval there's still a 30-minute undo before it routes.
Glossary
The few words worth knowing. Filter by letter.
Changelog
What shipped, and when.
Public launch
- Tap-first flow: tap, sign in, activate
- NFC tap-in and tap-out with live lab map
- Main PC class activation plus live class monitor
- Complaint pipeline with cooling-off plus undo windows
- LN Intelligence digest plus priority scores
Closed beta
- Supervisor tag pairing plus PC fault marking
- School and university analytics
- Audit logging across all roles
Internal pilot
- First NFC tap prototype on two labs
- Session ledger plus basic reporting
Support
Docs can't cover every lab. Talk to a human.
Still stuck?
Include your lab code and PC number for the fastest help. We usually reply the same day.