IoT Class
  • All Modules
  • Dashboard
  • Badges
  • Login

Teacher setup

  • The five-minute teacher setup
  • What students see
  • Progress visibility for teachers
  • Privacy story for minors
  • Printable brief

Teach with IoTClass

A five-minute setup guide for creating an IoTClass classroom, sharing a join code, and understanding student progress and privacy.
Instructor adoption kit

Your IoT classroom, ready in five minutes.

Choose a short learning path, share one join code, and see where students need help. The setup below matches what the live platform asks teachers and students to do.

Apply to teach Jump to printable brief
8-character codeNot case-sensitive; regenerate it if it is shared too widely.
100 studentsDatabase-enforced maximum per classroom.
5 active classesArchive an old class before creating another.

The five-minute teacher setup

Allow extra time for the one-off teacher approval. Once your account is approved, creating a classroom and sharing its code is a short in-browser workflow.

Sign in and apply once

Use Google sign-in, then provide an institutional email, institution, role/title, and intended use. An administrator approves or rejects the request.

one-off
Name the class

Open Create a classroom. Add the classroom details students will recognise.

1 minute
Choose the curriculum

Pick units from the IoTClass catalogue and review the ordered learning path before creating it.

2 minutes
Share the join code

Copy the generated 8-character code into your usual classroom channel. Students enter it at iotclass.org/join/.

1 minute
Check the roster

Open the Teacher Dashboard to confirm joins and review progress for the selected curriculum.

1 minute

Approval is not automatic. The application is linked to the Google identity used to sign in; approving it grants the teacher role in the same server-side operation. A rejected application does not grant classroom-creation access.

1 · Apply to teachThe one-off application asks only for the information needed to verify the teaching role.
2 · Copy the codeThe creation wizard ends with the classroom code and a direct copy action.
3 · Students consent and joinThe visibility statement appears beside a required checkbox before the join action.

Screenshots use the platform’s verified demonstration states; the example identities and code are not live classroom credentials.

What students see

Students first see a Google sign-in prompt. After signing in, they enter the 8-character code and must tick this statement before joining:

Your teacher will be able to see your progress and quiz results for this classroom’s curriculum.

After joining, the classroom home shows the teacher’s selected units as an ordered rail. A student can see their own overall completion, each unit’s state (not started, in progress, or completed), earned unit badges, and a continue action. If the teacher enabled Focused Mode, enrolled students also see the focused classroom navigation state.

The boundary is the classroom curriculum. Joining does not give the teacher general access to everything a learner does on IoTClass. The consent text and database access rules scope teacher visibility to the curriculum selected for that classroom.

Progress visibility for teachers

The Teacher Dashboard lists only classrooms created by the signed-in teacher. For a selected classroom it provides:

Roster view

  • student display name;
  • join date and last activity;
  • units completed;
  • quiz accuracy; and
  • badges earned for the selected units.

Unit view and controls

  • a per-student, per-unit completion grid;
  • CSV export of the roster summary;
  • copy or regenerate the join code; and
  • archive or unarchive the classroom.

Regenerating the join code invalidates the old code immediately for students who have not yet joined. Archiving prevents new joins; existing students keep their learning progress.

Privacy story for minors

Under 13

All learning content is readable without an account. A child under 13 must not create their own account; they may use IoTClass only under the supervision of a parent, guardian, or teacher.

Under 18

A classroom for students under 18 must be created by an admin-approved teacher acting for their institution. The teacher or institution remains responsible for any consent required in its context.

IoTClass uses Google OAuth, so the platform does not receive or store a password. It does not sell personal data or use it for advertising. Classroom membership, learning progress, and quiz results are stored in the platform backend; database row-level access rules limit a teacher to their own classroom roster and that classroom’s curriculum. The current retention policy says classroom rosters are kept until archive and then for 12 months.

For the complete account, analytics, service-provider, rights, deletion, international-processing, and children’s provisions, read the Privacy Policy and Cookie Notice. Privacy or deletion requests are handled at admin@iotclass.org.

Operational note: this kit summarises the controls and published policy currently present in the repository. It is not a substitute for your institution’s safeguarding, consent, or data-protection process.

Printable brief

IoTClass · teacher quick brief

Set up, share, check, protect.

IOTCLASS.ORG

Before class

  1. Sign in with Google and apply at iotclass.org/classrooms/apply.html.
  2. After approval, create a classroom and choose its units.
  3. Copy the generated 8-character join code.

Student instructions

  1. Open iotclass.org/join/ and sign in.
  2. Enter the code (capitalisation does not matter).
  3. Read and tick the teacher-visibility statement, then join.

What you can see

Roster, join/last-active dates, units completed, quiz accuracy, curriculum badges, and a per-unit completion grid — only for your classroom's curriculum.

Write the code here

_ _ _ _ _ _ _ _

Privacy check

  • Under 13: no child-owned account.
  • Under 18: use an approved institutional teacher account and follow local consent rules.
  • Students see the visibility statement before joining.
  • No advertising or sale of personal data.

Useful links

  • Dashboard: iotclass.org/classrooms/dashboard.html
  • Policy: iotclass.org/legal/privacy-policy.html
  • Help/privacy: admin@iotclass.org

Limits: 100 students per classroom; 5 active classrooms per teacher.

Back to top