What Are Teaching Spaces in EduGenius? Organizing Classes, Sections, and Rosters
A Teaching Space in EduGenius is a container for one class you teach. Inside it, you create one or more Sections — say, separate class periods or ability groups — and each Section gets its own join code and QR code. Students use that code to add themselves to a roster, with no login required.
Quick Answer: A Teaching Space is one class you organize in EduGenius. A Section is one group of students inside that Space — a period, a grouping, or a single section if you only teach one group. Each Section auto-generates a join code and QR code; students scan or type it to add themselves to that Section's roster, no account required. Teaching Spaces is deliberately minimal: no student-information-system integration, no parent or guardian accounts, and no attendance tracking. A demo mode with sample spaces, sections, and rosters lets you try the whole workflow before you connect a real class.
Any teacher who covers more than one class period, or more than one section of the same grade, runs into the same problem: a single free-text list of names doesn't scale, and retyping a roster for every new assignment wastes time that should go toward actual teaching.
EduGenius's Teaching Spaces page is built to solve that exact problem, and it's backed by a real API rather than a static mockup. This guide covers what the feature actually contains, why the space-section-roster structure exists, how to set one up end to end, and where its limits are by design.
What a Teaching Space Actually Is
A Teaching Space is the top-level container for one class you teach. Everything else you'll interact with — Sections, join codes, QR codes, and rosters — lives inside that one Space.
The Three-Layer Model: Space, Section, Roster
EduGenius organizes a class into three nested layers rather than one flat list. Understanding the distinction between them makes the rest of the feature self-explanatory.
- Space — the class as a whole, such as "Grade 6 Mathematics," with a name, subject, and optional grade/board fields.
- Section — one group of students inside that Space, such as "6A" or "Period 3," each with its own join code, QR code, and member count.
- Roster (Members) — the students who've joined a specific Section, shown by display name plus an optional free-text ID field you control.
A teacher managing three different class periods for the same subject creates one Space and three Sections inside it, rather than three disconnected class lists that share no relationship to each other.
Built on a Real Backend, Not a Mockup
Every action on the Teaching Spaces page — creating a space, adding a section, adding or removing a roster member — calls a real, dedicated API behind the scenes, not placeholder UI state. Listing, creating, and updating spaces, sections, and members are each separate, working server routes.
The join code itself is generated to avoid ambiguous characters, skipping 0, 1, I, L, O, and U so a student reading it off a slide or a printed handout doesn't misread a letter for a number. Join links reuse the same secure sharing mechanism EduGenius already uses elsewhere for shared assignments, rather than a separate, one-off system.
The table below summarizes the vocabulary this feature uses, since the terms map directly onto what you'll actually see on screen.
| Term | What it is |
|---|---|
| Space | The class you teach as a whole (e.g., "Grade 6 Mathematics") |
| Section | One group of students inside a Space (e.g., "6A," "Period 3") |
| Join code | A short, easy-to-read code students use to add themselves to a Section |
| QR code | A scannable version of the same join link |
| Roster / Members | The students who've joined a Section, by display name plus an optional ID field |
| Demo mode | Sample spaces, sections, and rosters you can explore risk-free before connecting a real class |
Once those five terms click, the rest of the workflow is just filling in each layer in order: Space, then Section, then roster.
Why Organizing Classes Into Spaces and Sections Matters
Splitting classes into Spaces and Sections isn't organizational overhead for its own sake. It mirrors a real, well-documented workload problem: teachers who manage multiple distinct groups of students spend real time on the administrative side of that work, and every extra disconnected tool or list adds to it.
The Multi-Section Workload Is Common, Not an Edge Case
Teaching more than one distinct group of students in a day is standard, not unusual. Nationally, 24% of public school teachers teach departmentalized classes — instructing several different groups of students for some or all of the day, rather than one self-contained class (NCES).
That structure alone creates administrative load. Full-time teachers report spending an OECD average of roughly 3 hours a week on administrative tasks, and in 18 of the education systems surveyed, "too much administrative work" grew as a reported source of stress between 2018 and 2024, even though it's a comparatively small share of total working time (OECD, TALIS 2024).
Fewer, Better-Organized Tools Beats More Disconnected Ones
Tool sprawl compounds the same problem. K-12 districts accessed an average of roughly 2,982 distinct edtech tools during the 2024-25 school year, a 9% year-over-year increase, and individual teachers used around 50 different tools across that same year (LearnPlatform by Instructure, 2025).
A structured roster inside the tool a teacher already uses to generate materials removes one more disconnected spreadsheet or app from that pile, rather than adding to it.
Minimal Data Collection Matches What Families Actually Want
Privacy is now a front-line concern for the same tool-sprawl reasons. Data privacy and security jumped to the #2 priority for K-12 edtech leaders in 2024, up from #5 in 2022 (CoSN, 2025). Parents notice, too: 66% express concern about unnecessary data harvesting by school technology (Pew Research Center, 2024), and half of US students report worrying about their own data's privacy (CDT, 2024).
The figures below give a sense of scale for both sides of the problem: the workload multiple class groups create, and the tool and privacy pressure layered on top of it.
| Data point | Figure | Source |
|---|---|---|
| Public school teachers who teach departmentalized classes (multiple distinct student groups) | 24% | NCES |
| OECD-average weekly time full-time teachers spend on administrative tasks | ~3 hours/week | OECD, TALIS 2024 |
| Distinct edtech tools an average K-12 district accessed in 2024-25 | ~2,982 (up ~9% YoY) | LearnPlatform by Instructure, 2025 |
| Distinct tools an individual teacher used across the 2024-25 school year | ~50 | LearnPlatform by Instructure, 2025 |
| K-12 edtech leaders ranking data privacy/security a top-2 district priority | Rank #2, up from #5 in 2022 | CoSN, 2025 |
| Parents concerned about unnecessary data harvesting by school technology | 66% | Pew Research Center, 2024 |
| US students who worry about the privacy of their own student data | 50% | CDT, 2024 |
| US schools/universities that have adopted QR codes for administrative or academic use | 45% | EdTech Magazine, 2024 |
None of this data is about EduGenius specifically. It's the backdrop that makes a dedicated, minimal-by-design roster feature — one Space, a few Sections, a join code, nothing more — a reasonable answer rather than a nice-to-have.
How to Create a Space, Add a Section, and Get Students to Join
Setting up a working class roster takes three steps: create a Space, add one or more Sections inside it, and share each Section's join code or QR code with your students.
Step 1: Create Your Space
Open the Teaching Spaces page and fill in a name (for example, "Grade 6 Mathematics"), plus an optional subject. The same form lets you add starter section names as you go — "6A" and "6B" are pre-filled as a starting suggestion, and you can remove or add to that list before you save.
Selecting Create Space saves the Space and creates each listed section in the same step, so you land with a fully structured class rather than an empty container you have to build out separately.
Step 2: Add a Section and Get a Join Code + QR
Every Section generates its join code and matching QR code automatically the moment it's created — there's no separate setup step. Selecting a Section shows its code as large, readable text, plus a QR image you can copy as a link or save as an image file for a slide or printout.
Need another group later in the term — a new class period, or a small group pulled from an existing one? Adding a Section to an existing Space takes one field: a name. Its join code and QR generate the instant it's saved, the same way the starter sections did.
Step 3: Students Join by Code or QR — No Login Required
A student scans the QR code or visits the join link and types the code, along with a display name. That's the entire flow: no student account, no email, no password. If the student happens to already be logged into their own EduGenius account, the join can also link to it automatically — but that's optional, not a requirement to join at all.
You can also add a learner manually from the roster panel, useful for a student without a device in the moment, or for building a roster ahead of a first class meeting. Manual entries and self-joined entries appear in the same table, with a column noting which way each student joined.
A generous ceiling — up to 300 members per Section — exists purely as abuse protection, not a realistic constraint. No real class comes close to it.
What a Full Roster Unlocks
Once a roster exists for a Section, the rest of EduGenius already knows which students a piece of content is for. Generate a quiz for that class and export it straight to Google Forms without retyping a single name, or point a saved content recipe at the same Space so every future worksheet for that class starts from the same preset.
Classroom Scenarios: Three Grade 4 Sections, or One Clean Roster
Two situations cover most of how teachers actually use this feature: managing several distinct groups of the same grade, and wanting one clean, join-code-based roster for a single class.
A Teacher With Three Different Grade 4 Sections
Say you teach three separate Grade 4 groups back to back. One Space — "Grade 4," with a subject if useful — holds three Sections: "4A," "4B," and "4C." Each gets its own join code, so a code posted on one classroom's board only ever adds students to that specific group's roster.
That separation matters beyond the roster itself. Sections are also how other parts of EduGenius know which group a piece of content belongs to — an assignment published to "4B" reaches only that Section's roster, not the other two.
A Teacher With One Class Who Still Wants a Clean Roster
You don't need multiple groups to benefit from the structure. A single class still gets its own Space and one Section, which means one persistent join code and QR you can reuse at the start of every new term, instead of rebuilding a spreadsheet from scratch each time.
It also replaces the workaround a lot of teachers already use — a free-text list pasted into whatever tool needs a roster that week — with one place that stays current as students join or leave.
If you already save material into EduGenius from around the web, see how the EduGenius Chrome extension turns web content into teaching materials. Pointing that saved content at the right Space keeps everything for one class findable in one place instead of scattered across a general pool.
What Teaching Spaces Is Not (Scope and Limits)
Teaching Spaces is deliberately minimal, and the missing pieces are a design choice, not an oversight: no student-information-system integration, no parent or guardian accounts, and no attendance tracking.
What's Missing, and Why
The roster panel says as much right on screen: badges reading "no parent info," "no attendance," and "no demographics" sit under every roster you view, as a constant, honest reminder of what the feature does and doesn't do.
- No SIS integration. Teaching Spaces doesn't sync with your school or district's student information system; a roster here is separate from your official gradebook or enrollment records.
- No parent or guardian accounts. There's no login, dashboard, or notification surface for a parent — the roster is teacher-and-student only.
- No attendance tracking. Joining a Section's roster is a one-time action, not a daily check-in; nothing here logs which day a student was present.
- No demographic fields. The optional ID field is free text you define, not a formal student-ID system or a place for sensitive demographic data.
This Isn't Built for District-Wide Deployment
Teaching Spaces is scoped to what one teacher needs for their own classes, not a district enrollment system. There's no admin console for a principal to manage every teacher's Spaces at once, and nothing here claims to replace a district's official information systems.
If your school needs SIS-synced rosters, official attendance, or parent communication, those stay the job of your school's existing systems. Teaching Spaces solves the narrower problem of organizing classes and getting a lightweight roster in place quickly.
Try It in Demo Mode Before You Connect a Real Class
Flip on Demo mode and the Teaching Spaces page substitutes its live panels for realistic sample data. You're not looking at an empty state or a screenshot — you're clicking through a working version of the same UI.
What the Sample Data Actually Shows
The sample data ships as two illustrative classes: one math class split into three Sections with dozens of sample students already on the rosters, and one science class split into two Sections. You can create a new Space, add a Section, and add or remove a roster member, and every one of those actions updates the screen in front of you immediately.
Nothing You Do in Demo Mode Is Saved
None of it is real. Demo actions never touch the network or write to a database — creating a "space" in demo mode changes only what's on your screen, and a QR code generated in demo mode doesn't open a real join page for anyone.
Turn demo mode off and you're back to your actual account: real Spaces you've created, or an honest empty state if you haven't created one yet. That matters for anyone evaluating the feature before rolling it out to an actual class — you can fully experience the create-a-space, add-a-section, students-join workflow with zero risk of a stray test entry landing in a real roster.
Teaching Spaces only handles the roster side of the workflow — organizing who a piece of content is for. For the content itself, see AI Worksheet Generators: The Complete 2026 Guide, which covers the broader category Teaching Spaces feeds into.
Pro Tips
- Match section names to what your school already uses (the same period label or class-group name), so a join code posted on a board maps instantly to something students already recognize.
- Put the QR code on a slide, not just the code as text, for younger grades — scanning is faster and less error-prone than typing a code correctly.
- Save the QR image once and keep it for the whole term; you don't need to regenerate it unless you create a brand-new Section.
- Use the optional ID field for a stable label (like a homeroom number) if two students share a first name, so the roster stays easy to scan.
- Clean up the roster after a big self-join wave. A mistyped name from a rushed QR scan is easiest to fix minutes after it happens, not weeks later.
- Pair a filled Section with a quick generation task. Once a roster exists, generating a fast set of practice questions for that exact class takes minutes, not a free period.
What to Avoid
- Don't create a new Space for every assignment. A Space represents the class, not a single task — one Space per class, reused across a whole term, keeps rosters intact instead of fragmenting them.
- Don't try to store more than the two fields ask for. The optional ID field is free text you control; it isn't built to hold a parent's contact information, a formal SIS number, or any other sensitive detail.
- Don't treat a join as attendance. A student joining a Section's roster once at the start of term isn't the same as being marked present on any given day — there's no daily check-in built into this feature.
- Don't post a join code somewhere public. Share it with your class specifically (a slide, a printed handout, a class-only channel), not a public social post — anyone with the code or QR can join, which is the point for a classroom but not for the open internet.
- Don't confuse demo mode with your real account. A space or roster entry created while demo mode is on disappears the moment you toggle it off; nothing in demo mode is saved anywhere.
- Don't expect parent-facing features. If a family needs visibility into their child's classwork, that has to happen through your school's existing parent-communication channel — there's no parent account here to route it through.
Key Takeaways
- A Teaching Space is a class; a Section is a group inside it. Spaces hold one or more Sections, and each Section carries its own join code, QR code, and roster.
- Students join with no login — a display name and a join code (or a QR scan) is the entire flow, with manual roster entry available as a backup.
- It's backed by a real, working API, not a placeholder UI. Creating a space, adding a section, and adding or removing a roster member each call dedicated server logic.
- Multi-section teaching is common, not an edge case: 24% of public school teachers teach departmentalized classes covering several distinct groups of students (NCES).
- Administrative load and tool sprawl are measured, real pressures teachers already face, from roughly 3 admin hours a week on average (OECD, TALIS 2024) to about 50 distinct tools used per teacher a year (LearnPlatform by Instructure, 2025).
- The feature is deliberately minimal: no SIS integration, no parent or guardian accounts, and no attendance tracking, matching families' and district leaders' growing preference for tools that collect less, not more (CoSN, 2025; Pew Research Center, 2024).
- Demo mode lets you try the entire workflow risk-free: sample spaces, sections, and rosters you can create, edit, and delete without any of it touching a real database.
- Sections scope other EduGenius features, too — an assignment published to one Section reaches only that Section's roster, not every student across a whole Space.
Frequently Asked Questions
What is a Teaching Space in EduGenius?
A Teaching Space is a container for one class you teach in EduGenius. It holds one or more Sections, and each Section has its own join code, QR code, and student roster, so you can manage several class groups without a spreadsheet.
How is a Section different from a Space?
A Space is the class as a whole — for example, "Grade 6 Mathematics." A Section is one group of students inside that Space, such as a specific period or class group, and it's the Section, not the Space, that carries its own join code and roster.
Do students need to create an account to join a class?
No. A student scans a QR code or visits a join link, types the join code and a display name, and that's the complete flow. If they happen to already be logged into their own EduGenius account, the join can optionally link to it, but an account isn't required to join at all.
Can I use Teaching Spaces to track attendance?
No. Joining a Section's roster is a one-time action, not a daily check-in, and there's no attendance-tracking feature built into Teaching Spaces. The roster panel says so directly, with an on-screen "no attendance" note.
Does Teaching Spaces connect to my school's student information system (SIS)?
No. Teaching Spaces is deliberately separate from any SIS. A roster built here doesn't sync with your school's official enrollment or gradebook system, and it isn't designed to replace either.
Can parents see their child's roster entry?
No. There are no parent or guardian accounts in this feature, and no parent-facing view of any roster. Family communication about classwork stays with your school's existing channels.
Can I try Teaching Spaces before adding any real students?
Yes. Turning on Demo mode substitutes the page with realistic sample spaces, sections, and rosters you can fully interact with — creating, editing, and removing entries — without any of it being saved or connected to a real student.
How many students can join one Section?
Up to 300, though that ceiling exists purely as abuse protection rather than a realistic classroom limit — no ordinary class size comes close to it.