Why SLS Needs Batch Teacher Enrolment into Class Group

 

Why SLS Needs Batch Teacher Enrolment into Class Group

It was the night before a big SLS PD rollout. Ms Lee, the PD owner, stared at a spreadsheet with 420 names. Her team had already defined roles:

• Owners to lead the session

• Co-teachers to facilitate breakout activities

• Observers to watch and reflect

All ready for an in, with, and through SLS experience.

But first, they had to add every teacher into the SLS class group — manually.

Click: add owner.
Click: add co-teacher.
Click: add observer.

Again. And again.

They even tried advertising the QR code self-enrol feature that SLS provides for joining class groups, but it fell short: teachers who scanned it still couldn’t enter with the correct role. If the teacher wanted to be added as a teacher role, they would have to scan and hope for the correct access mix. If they wanted to join as a student — because some activities were designed to mimic student experience — they would have to switch to their student account first and then scan the QR code. That extra step didn’t solve the problem; it just shifted the friction.

Meanwhile, SLS was meant to be MOE’s one-stop hub for teaching and learning, where curriculum content, collaboration, assessments, and tools all live together in one seamless environment. It supports teachers with a wide range of tools to create meaningful learning experiences.

And through the EdTech Masterplan 2030, SLS plays a key role in enabling technology-transformed learning: strengthening teacher capacity, enabling collaboration across classrooms and schools, and supporting personalised and data-informed learning.

But when every PD session still begins with hours of manual administrative work, that vision is compromised.

Here’s the crux:
PD is meant to happen in SLS, using the platform itself.
It’s meant to happen with SLS, leveraging its tools and data.
And it’s meant to happen through SLS, where teachers embody the learner experience.

Yet the onboarding process still forces teams to use spreadsheets, manual clicks, and workarounds like switching accounts just to align role access.

What if instead…
PD leads could:
✔ upload a simple CSV of teachers,
✔ assign roles (owner, co-teacher, observer),
✔ click “Add teachers in batch.”

In minutes, all teachers — in the right roles — have access. Analytics populate. Discussions begin. PD starts. No QR code confusion. No student/teacher account toggle. No late-night admin.

That small enhancement would make SLS not just a one-stop hub, but a scale-ready hub, aligned to the EdTech Masterplan 2030 by reducing administrative friction and letting educators focus on what matters most — teaching, learning, and professional growth.

If you are interested to run RPA, i have made a TagUI file that automate the process for adding teachers. update 20260224

https://github.com/lookang/TagUI/blob/main/SLSclassAddTeachersasStudent/classAddTeachers2.tag

revert to TagUI to run RPA as maintaining playwright is time consuming.

https://sg.iwant2study.org/ospsg/index.php/sls-t-ug/1325-automating-sls-adding-teachers-as-students-with-playwright-the-sls-pd-of-teacher-challenge