Homeroom Directory · the school directory and ID cards
A living school directory that builds itself from your roster.
A printed directory is out of date the day it ships, and a public one is a privacy risk a school should never take. Homeroom Directory keeps a school’s own directory of students, staff, and families current automatically — built from the same roster the rest of the platform uses. It is not a public page: the directory lives inside the school’s own private account, and an ID-card pipeline draws from the same list.
The living directory and the ID-card pipeline are live today. A parent-facing class directory, where a family could be listed for other families in the same class, is in early access, and it is being built with per-family privacy controls that default to off.
Always current
The directory builds from the roster a school signs in with or imports once, so when a student enrolls or a teacher changes rooms, the directory is already right — no annual reprint that is stale by October.
Private, not public
The directory is not a public website. It lives inside a school’s own account on the platform, and only the staff a school allows can look someone up.
ID cards, from one list
Badges and ID cards draw a name and a photo from the same roster and directory, so issuing a card is a print job for the school’s own use, not a separate data-entry project.
Built from the roster you already keep
A school signs in with the standard ways it already logs in, or imports its roster once, and the directory builds itself from that same list — the same roster the rest of the platform shares. There is no second spreadsheet to keep in sync and no annual re-typing project: when a student enrolls, a family updates a phone number, or a teacher changes rooms in the roster system of record, the directory is already right.
A school owns the directory it builds this way. Homeroom Directory keeps it current; it does not take that ownership away.
Who can actually see the directory
Homeroom Directory is not a public listing, and it is not searchable from the open internet. It is a private, permission-checked directory that lives inside a school’s own account on the platform — built from the roster a school already keeps, and reachable only by a signed-in user the school has given access to. There is no public URL that lists a school’s students, staff, or families, and the directory is never indexed by a search engine.
Today, looking someone up is a staff-facing action: a signed-in staff member with the right role finds a student, a colleague, or a family contact the way they would flip through a paper directory, except it is always current. A school controls who holds that access, the same way it controls who holds a key to the front office — access is a role a school grants, not a default every account gets.
Directory and family contact details are never sold and never handed to an outside company. A school owns the directory it builds; hosting it here does not change that, and a school can get its data out or have it removed.
Being honest about the edges: a directory holds real data — a name, a room, a contact email — the same kind of thing a school already keeps on file. The promise here is narrower than a blanket claim that nothing exists: it is that the directory does not become a public page, it is not sold, and it is not handed to an outside company to mine.
Who sees what: the audiences and the permissions
Nothing in the directory is visible to anyone by default. Every row below starts denied, and only a specific grant makes a cell visible: a staff role a school grants, or a family’s own opt-in. An account or a family that does nothing stays out — the absent record is denied, not shown.
There are two kinds of grant, and only two: (1) staff access is a role a school grants to a signed-in staff member, scoped to that school; (2) family visibility in the parent-facing class directory is a per-family opt-in that defaults to off, one family at a time. Students are not a directory-viewer audience on this surface. The public internet, a search engine, and an outside company are denied every cell, with no exception.
| Audience | Look up a staff or student record | See a family’s contact info | See the parent-facing class directory | Appear in the class directory | Print/ID-card lookup |
|---|---|---|---|---|---|
| Staff with a school-granted role | Yes, within the school | Yes, within the school | N/A | N/A | Yes, within the school |
| Staff without that role | No | No | No | No | No |
| A signed-in family, its own record | N/A | Own record only | Only if that family opts in (default off, early access) | Only if that family opts in (default off, early access) | No |
| Another family in the same class | No | Only if that family opted in | Only the families that opted in | N/A | No |
| The public, or a search engine | No | No | No | No | No |
| An outside company or data buyer | No, never sold or handed to an outside company | No, never sold or handed to an outside company | No, never sold or handed to an outside company | No, never sold or handed to an outside company | No, never sold or handed to an outside company |
Reading the table plainly: a school-granted staff role is the only way in for staff, scoped to that school’s own roster. A family only ever sees its own record until it opts in, and even then only opted-in families see each other in the early-access class directory. The public, a search engine, and an outside company never see a row, never a cell, no exception.
The parent-facing class directory: early access, opt-in by design
A separate, not-yet-live feature would let a family choose to appear in a class directory that other families in the same class could see — a modern version of the paper class list a room parent used to photocopy. It is in early access: built, being tested, not open to every school yet.
The design principle for that feature is per-family privacy controls with a default of off: a family’s information becomes visible to other families only if that family opts in, one family at a time, and a family that does nothing stays out of the class directory. Until this feature is generally available, no family sees another family’s directory information through this product.
This is separate from the staff-facing directory above, which is live today and used by a school’s own staff. The parent-facing, family-to-family view is the piece still in early access, and this page says so plainly rather than presenting it as available now.
ID cards, drawn from the same list
A school’s badges and ID cards pull a name and a photo from the same roster the directory uses, so issuing a card is a print job, not a separate data-entry project or a second system to keep in sync.
Printing a badge is a roster lookup and a print job for the school’s own internal use — it is not a face-recognition feature, and it is not a public posting of a student’s photo. Facial recognition, where the platform offers it at all, is off by default.
How the money works, honestly
The directory and the ID-card pipeline are part of the free core of the platform — no per-student fee to keep a directory current or to print a badge.
This page runs no checkout and takes no payment. Money on the platform is honest-off: it is described in its own terms elsewhere, not as a live transaction here.
What is live, and what is early access
The staff-facing directory and the ID-card pipeline are running today. The parent-facing, family-to-family piece is still opening up, and this page keeps the line between them honest.
Live today
The living directory — students, staff, and families kept current from the school’s roster — and the ID-card pipeline both run today.
Early access: parent-facing class directory
A family-to-family class directory, gated by per-family privacy controls that default to off. Built, opening gradually, not open to every school yet.
How we label it
If a capability is early access, this page says early access — not “coming soon” theater. A school should never adopt a promise it cannot see.
Common questions
Is our school’s directory public?
No. There is no public page or public URL that lists a school’s students, staff, or families, and the directory is never indexed by a search engine. It lives inside the school’s own account and is reachable only by a signed-in user the school has given access to.
Who can see my child’s information in the directory?
Today, the directory is staff-facing: a signed-in staff member with a role the school has granted can look up a student, a colleague, or a family contact. A parent-facing view where other families could see it is a separate, early-access feature, described above, and it defaults to off per family.
Can other families see our family’s contact information?
Not through the live product today. The parent-facing class directory that would allow that is in early access and is being built with per-family privacy controls: a family’s information appears to other families only if that family opts in, and the default is off.
Do you sell directory or family contact information?
No. Directory and family contact details are never sold and never handed to an outside company. A school owns the directory it builds; hosting it here does not change that.
Are the ID cards a face-recognition system?
No. Printing a badge is a roster lookup and a print job for the school’s own use, not a face-recognition feature. Facial recognition, where the platform offers it at all, is off by default.
Is it free?
Yes. The directory and the ID-card pipeline are part of the free core of the platform — no per-student fee. This page runs no checkout and takes no payment.
How is this different from homeroom.software?
Same platform, narrower question. homeroom.software leads with what the whole platform does across publications, records, the directory, and picture day. Homeroom Directory leads with one piece of that — the living directory and ID cards — and with exactly who can see it.
What this page is and is not claiming
Homeroom Directory is a school’s own living directory of students, staff, and families, built from its roster, plus an ID-card pipeline drawn from the same list. It is not a public listing: there is no public URL that lists a school’s people, and the directory is never indexed by a search engine. Directory and family contact details are never sold and never handed to an outside company. The staff-facing directory and the ID-card pipeline are live today; a parent-facing class directory is a separate, early-access feature being built with per-family privacy controls that default to off — until it ships, no family sees another family’s directory information through this product. Printing a badge is a roster lookup, not a face-recognition feature; facial recognition, where the platform offers it at all, is off by default. Money is honest-off: the directory and ID cards are part of the free core, and this page runs no checkout. This is a for-profit vendor, not a charity, and nothing here is dressed up as a charitable gift. There is no sample directory entry, no mock name, and no fabricated count anywhere above, and no competitor is named.