Gamemasters · Houses
Houses — Your Course Hub
A House is a course. Learn how it holds your campaigns, Lore, parties, Dungeons, sources and collaborators, where to find your courses, and what your students see of it.
Verified against app build 2f427ecbd · 2026-10-07
A House is a course: the thing a class enrols in and works through for a term or a year. Everything else hangs off it:
House (COURSE)
├─ Campaign (UNIT) → Path (chapter) → Node (lesson)
├─ Party (cohort) — the join code lives here
├─ Dungeon (shareable review challenge)
└─ Collaborators (other teachers you invite)
A Campaign is a unit, not a course
Campaign means a unit (or module) inside a course. It is not the course itself, and since the units are ordered inside one named course, a Campaign does not carry a title of its own. The House is what gets named.
How a course gets created
A course is born with its first unit, in one step.
Tap Create House (Course)
From Gamemaster Quarters on Base Camp or from My Houses, tap Create House (Course). Answer the steps, and in one transaction the server mints the House (the course), its first Campaign (the opening unit), and your first Party.
Add further units to the same course
Each later unit is created inside the course you already have, so the course grows a unit at a time. Every Campaign belongs to exactly one House; there is no standalone-unit mode.
A course can be empty, but nobody can play it
If you delete a course’s last unit, the course stays. Its parties read Needs a campaign, and students cannot join or play it until it has one again. Deleting a unit is not final: see Deleted campaigns below.
Find your courses: My Houses
My Houses lists every course you own, archived ones included. Open it from
the House Management button in Gamemaster Quarters, or from the navigation
drawer’s Houses header. On the web it lives at /houses.
Each course is a row that expands to its campaigns and its parties. A course’s menu offers:
- Edit House: the course’s name, subject and audience.
- Add Campaign and Add Section: a new unit, or a new Party.
- Collaborators: who else works in this course. See Invite collaborators.
- Deleted campaigns: the 30-day Trash (below). Owner only.
- Delete House: removes the whole course. Owner only.
Deleting a House cannot be undone
Before it deletes anything, the app counts what the course holds and shows it to you: its campaigns, parties and enrolled students, along with all campaign content and student progress. Any Dungeon filed under the course goes too, and its share code stops working for anyone who has it. Only the owner can delete a House.
Deleted campaigns
A campaign you delete is not gone at once. It waits in the course’s Trash for 30 days, and restoring it puts it back with its content, its library and its students’ progress.
Open it from the course’s menu in My Houses by choosing Deleted campaigns (the sheet is headed “Deleted from this House”). The owner is the one who can delete a unit, so it is the owner who sees this Trash. A campaign’s own builder has a separate Trash for what you delete inside it; see Create a Campaign, Path & Node.
One page, two audiences
The course opens at a single screen that both you and your students reach. On the
web its address is /house/ followed by the course’s id. It is a main destination, not something you drill down
into. There is no separate “course builder”: the list of units is the course.
What everyone who can open the course sees:
- Identity: the course’s name, subject, and audience.
- Lore: a short paragraph about the realm, in the Sovereign’s own card, and a button, Explore “<Kingdom>”’s Lore & Characters, that opens the rest. See Set up & Use Lore.
- Campaigns: the ordered units, each the way into its Paths and Nodes.
What the people who run the course also see:
- Collaborators: the owner and every collaborator, with their roles. The owner manages them; a collaborator can see who else works here and can leave. A student never sees this section.
What only the owner and Editor collaborators see:
- Dungeons: assemble and share review challenges. See Dungeons.
- Source Library: the sources the AI Wizard reads when you generate content.
At the top of the page, the title carries a few doors of its own:
- GM Actions (the construction icon): Edit House and Edit Lore (or Author Lore, until the course has Lore of its own). Owners and Editors only.
- Copy this House (Course): a Teacher collaborator can’t edit the course but can take a copy of their own. Owners and Editors copy from the Edit House sheet.
- Leaderboard: the House leaderboard, for every viewer. What each person sees is the server’s call.
- Party Records: for anyone who teaches or belongs to a Party here, owns the course, or administers it.
Where the Parties went
The course page has no Parties list of its own. A teacher manages sections from the app bar’s Switch Section button, from My Houses, or from Party Management. See Parties & inviting players.
Lore deliberately crosses that line
Lore is the one editor-adjacent thing students do see. It discloses nothing (it is the setting, not a credential), and a student who cannot name the realm their class is set in is missing the point of the course. Only the edit affordance is withheld.
One join code for the whole course
A Party enrols in the course, not in a unit. So one 6-character code covers every Campaign in the House, and a student who joins lands on the course page with access to every unit in it. You do not re-issue a code per unit.
A join code is a credential, so the server holds a course’s Parties back from anyone who isn’t running them: a student never receives another cohort’s code, and a collaborator sees only the sections they run themselves.
See Parties & inviting players for running a cohort, and Join a Party for the student side.
You never need collaborators to teach
A House works on its own: you create it, you own it, and you run your own Parties. Collaborators are for sharing a course with other teachers. Inviting them is part of Lord; see Invite collaborators.
