Setting up a school account
Red Stet runs at the individual user grain — every teacher, student, and admin is a users row — with a district + school org layer above. Teacher verification, account tiers, the platform admin role, and the district/school org model.
The teacher-verification gate Ships today
Every teacher passes a verification check before they can create classrooms, post assignments, or see Provenance recordings. Same gate for individuals and school teachers.
Four states on users.teacherStatus:
- None — writer / editor / student. Not in the teacher flow.
- Pending — applied via the teacher flow with evidence (school email, role description, ID). In the admin queue.
- Verified — approved. Full classroom, grading, and recording access.
- Rejected — declined. Can re-apply; a new row lands in
teacherApplicationsand the audit trail accumulates.
How applications are reviewed
Every teacher self-applies. Sign up, hit "Apply to teach", wait. A superuser reviews name, email domain, and role from the queue and approves or rejects. The applicant gets a notification.
Account tiers Wired, not surfaced
users.subscriptionTier has three values: free, pro, institutional.
- Free — default. Writing, marks, notes, Provenance recording, viewing recordings on your own work.
- Pro — individual teacher tier.
- Institutional — billed to the org against a seat count, admin controls, single invoice.
Institutional is granted manually today — a superuser flips the field for early-access schools. Email us.
{
email: "[email protected]",
teacherStatus: "verified",
subscriptionTier: "free",
stripeCustomerId: null
}
Platform administrators Ships today
The superusers table is a flat allowlist of platform-wide admins. Email matches on sign-in, isDev flips on. Superusers can:
- Review teacher applications across the platform
- See all classrooms and submissions (god-mode)
- Bootstrap new superusers
- Operate the admin queue
School IT coordinators email support for admin actions — approving a teacher, suspending an account, pulling a roster. [email protected].
superusers: [
{ email: "[email protected]",
note: "Founder", createdAt: ... },
{ email: "[email protected]",
note: "Support eng", createdAt: ... }
]
Onboarding teachers at a school today Ships today
Until the self-serve seats panel ships, schools onboard through the individual flow:
- Each teacher signs up at app.redstet.com and uses "Apply to teach" with their school email.
- Applications land in the superuser queue.
- For institutional pricing, the IT coordinator emails support with teacher emails and school. Support flips verified teachers to
institutional.
Already available at the classroom level
- Co-teacher / TA roles handle much of what schools assume needs an org account — multiple staff on one classroom, per-class capability overrides.
- LTI 1.3 with Canvas / Schoology / Brightspace — see Connecting Red Stet to your LMS.
District + school org model Ships today
The org layer sits above classrooms. A district contains schools; a school contains teachers, co-teachers, TAs, and students. Classrooms are owned by an individual teacher and can be attached to a school — attaching gives the school's admins roster + reporting visibility without taking ownership.
Roles
- Owner — transfers org ownership or archives the org. At least one per district and per school.
- Admin — manages members, classes, billing view, and the domain allowlist. Day-to-day operator.
- Billing-only — sees payment and invoice surfaces. Can't manage rosters or pull reports. For finance contacts.
Org-admin invites
Owners and admins invite from the Organizations panel by email. The invitee gets an email plus an in-app notification if they have an account. Invites expire after 14 days; resending refreshes the expiry.
Pre-approved domain allowlist
Each school keeps an allowlist of email domains (e.g. @centralhs.edu). When someone signs up with a matching address:
- Auto-attached to the school via a school membership row.
- If the domain is marked auto-verify teacher, the review queue is skipped and the account flips to verified.
Soft-removing a domain stops new auto-attachments; past ones stay, audit trail intact.
What admins see — and what they don't
The boundary that matters for FERPA and student trust:
- Org admins can see roster counts, classroom names, teacher rosters, integrity-rate aggregates, and the domain allowlist.
- Org admins cannot see document body content, mark text, margin-note content, or private student work. Those stay gated to the classroom owner or staff with grading rights.
- The only path to body content is a compliance export — a records-request flow that requires a written reason, fans email confirmations to every named student, and logs permanently.
Attaching classrooms to a school
In the classroom's Settings tab, the owner picks the target school. The classroom keeps its owner; school admins gain a read-mostly seat. Detaching clears the link.
Removing a member
A school admin can soft-remove any member. For departing teachers, an optional "return classrooms to the org pool" toggle notifies the school's primary contact and first three admins with the orphaned classrooms. Reassignment runs from the org admin dashboard.
The integrity rollup and writing patterns
Once a school is wired up, two daily aggregates populate: the integrity rollup (confirmed-issue, non-issue, pending, and review-rate counts across every submission in a rolling 30-day window) and the typing-rhythm aggregate (school-wide WPM bucket distribution). The Overview and Writing patterns tabs read from these.
The integrity rollup breaks down per subject. The cron reads classrooms.subject and writes a per-subject rollup alongside the all-subjects one. Low-volume subjects still appear — the rate is a denominator slice.
The typing-rhythm aggregate respects a k-anonymity floor of 10 samples. Below the floor, no chart — the dashboard says "Insufficient sample". The chart only exists when the data is genuinely aggregate.
Individual student writing content. Individual keystroke streams. Individual paste positions. Individual flag decisions. The aggregates are bucket counts and category totals only.
Related
→ Co-teachers & TAs — the classroom-level role model.
→ Connecting Red Stet to your LMS — Canvas / Schoology / Brightspace setup, often the right move before an institutional plan.
→ Setting up your first class — what each verified teacher does on day one.
Setting up an institutional account? Email us — early-access institutional onboarding is high-touch on purpose.