This guide explains how TMS Nuggets works: pages, roles, workflow, and actions. It does not access student records. Do not enter student names or case details here.
What it is: Entry point for logging. Log positive notes, neutral notes, or behavior concerns. Assign students to pending nuggets. Optionally escalate to office.
Who uses it: Teachers, secretaries, admins, store staff (for enrollment).
Main actions: Log Concern, Log Neutral, Log Positive; Assign Student; Escalate to office.
Common confusion: You must enroll (sign in) before logging. Student name is optional for concerns.
What it is: View your own logs, assign students to pending nuggets, see escalation status (Logged → Principal notified → Student requested → In office → Resolved).
Who uses it: Teachers, secretaries, admins.
Main actions: Assign Student, Edit log, Refresh. Filter by student groups.
You see your logs only. Escalation summary does not show incident narrative (note_text).
What it is: Operational console for office staff. Active queue and recent activity. Call student, mark student arrived, notify principal. No incident narrative.
Who uses it: Secretaries, admins. Must log in on Behavior page first.
Main actions: Claim, Call Student, Student Arrived, Notify Principal, Refresh.
Secretary sees operational data only—no note_text, no incident narrative.
What it is: Full case handling, logs table, staff and student management, groups, reports. Requires admin key (one-time per device).
Who uses it: Admins only.
Main actions: Acknowledge, Called Student To Office, Student Arrived, Student Did Not Arrive, Close Case, Create PDF, Refresh.
Admin key must be set once per device. Clearing browser data requires re-entry.
What it is: Redeem nuggets for students. View leaderboard and catalog. Store role sees operational ledger only (no incident narrative).
Who uses it: Teachers, secretaries, admins, store staff.
Main actions: Redeem Nuggets, Refresh Balance.
Store role does not see note_text for FERPA safety.
Does: Log positive/neutral/concern. Assign students. View own logs and escalation status.
Does not: See incident narrative in escalation summary. Access other teachers' logs.
Pages: Behavior, Teacher Dashboard, Store.
Does: Claim cases, call student, mark arrived, notify principal. Operational case data only.
Does not: See note_text or incident narrative.
Pages: School Response Team (Secretary), Behavior, Teacher, Store.
Does: Full case detail, staff/students/groups, reports, PDF export. Requires admin key.
Does not: Share admin key. Bypass device lock.
Pages: Admin, Behavior, Teacher, Secretary, Store.
Does: Redeem nuggets. View leaderboard. Ledger without narrative.
Does not: See incident narrative (note_text withheld).
Pages: Store.
Logged — Case created, awaiting School Response Team.
Principal notified — Case claimed by School Response Team.
Student requested — Student called to office.
In office — Student arrived at office.
Resolved — Case closed.
Phrase: School Response Team. Escalation: teacher logs concern → optionally assigns student → sends to office → case created.
Log Concern — Creates CONCERN log, optional student assignment, optional escalation to office.
Log Neutral — Creates NEUTRAL log.
Log Positive — Creates POSITIVE log with +1 nugget.
Assign Student — Assigns selected student to pending log.
Assign Student — Assigns student to pending log.
Edit — Opens editor for log (kind, note, student).
Refresh — Reloads dashboard data.
Claim — Acknowledges case, claims for School Response Team.
Call Student — Records that student was called to office.
Student Arrived — Records that student arrived at office.
Notify Principal — Sends principal exception email for case attention.
Acknowledge — Claims case for response.
Called Student To Office — Records call to office.
Student Arrived — Records arrival.
Student Did Not Arrive — Records non-arrival; may trigger principal email.
Close Case — Closes case with resolution.
Create PDF — Builds report PDF.
Redeem Nuggets — Spends nuggets for selected student and item.
Refresh Balance — Reloads student balance.
This helper has no access to production data, D1, or live cases.