Ms. Okafor · Riverbend Elementary · Grade 3
Product architecture
Information architecture
One URL space, five zones, role-adaptive content. Roles do not get separate apps — they get different content, defaults and permissions inside the same pages, so an MTSS team can link each other to the same student and see the same truth. Switch the role in the header to see the tables below highlight that role.
EduNexus shared platform
What identity owns vs. what MTSS.ai owns
Shared — owned by EduNexus
- · Organizations
- · Schools
- · Users & profiles
- · Memberships
- · Roles & permissions
- · Product entitlements
- · Students (canonical student_id)
Owned by MTSS.ai
- · Cases & tiers
- · Interventions & intervention plans
- · Progress monitoring
- · Meetings & team notes
- · Screening information
- · MTSS documents & decision history
- · MTSS workflows
Every MTSS record references the canonical EduNexus student_id. Opening a student offers entitlement-aware links into other EduNexus applications — the student record itself is never duplicated.
Sitemap
Grouped by zone
Work
- Dashboard
/
- Students
/students
- Student Intelligence Profile
/students/:id
- Universal Screening
/screening
- Referral Wizard
/referral
- Task Engine
/tasks
Intervention
- Intervention Library
/interventions
- Intervention Planner
/plans
- Intervention groups
/groups
- Progress Monitoring
/monitoring
- AI Meeting Assistant
/meetings
Oversight
- Tier pipeline
/tiers
- Fidelity monitoringrole-specific
/fidelity
- Referral readinessrole-specific
/readiness
- Compliance dashboardrole-specific
/compliance
- District analyticsrole-specific
/analytics
Admin
- Users & rolesrole-specific
/settings/users
- Schools & windowsrole-specific
/settings/schools
- Approved interventionsrole-specific
/settings/library
- Integrationsrole-specific
/settings/integrations
- Audit logrole-specific
/settings/audit
Family
- Family homerole-specific
/family
- Messagesrole-specific
/family/messages
- Consent & noticesrole-specific
/family/consent
Navigation
Sidebar groups render only when the role has an item in them
| Group | Items | Visible to |
|---|---|---|
| Work | Dashboard · Students · Student Intelligence Profile · Universal Screening · Referral Wizard · Task Engine | All staff |
| Intervention | Intervention Library · Intervention Planner · Intervention groups · Progress Monitoring · AI Meeting Assistant | Teacher, Reading Specialist, Behavior Specialist, Speech Therapist, Counselor, MTSS Coordinator, School Psychologist, Administrator |
| Oversight | Tier pipeline · Fidelity monitoring · Referral readiness · Compliance dashboard · District analytics | Reading Specialist, Behavior Specialist, Speech Therapist, Counselor, MTSS Coordinator, School Psychologist, Administrator, District Administrator |
| Admin | Users & roles · Schools & windows · Approved interventions · Integrations · Audit log | Administrator, District Administrator |
| Family | Family home · Messages · Consent & notices | Parent / Guardian |
User roles
Ten roles, six archetypes
Teacher
Focus · Core instruction
Data scope · Own roster
Reading Specialist
Focus · Reading
Data scope · Assigned caseload
Behavior Specialist
Focus · Behavior
Data scope · Assigned caseload
Speech Therapist
Focus · Speech / language
Data scope · Assigned caseload
Counselor
Focus · SEL & attendance
Data scope · Assigned caseload + school SEL
MTSS Coordinator
Focus · All tiers
Data scope · Assigned schools
School Psychologist
Focus · Referral readiness
Data scope · Assigned schools
Administrator
Focus · School health
Data scope · Own school
District Administrator
Focus · System & equity
Data scope · All schools
Parent / Guardian
Focus · My child
Data scope · Own child only
Reading, Behavior, Speech and Counselor are one Specialist archetype with a domain attribute. They perform identical actions on identical screens; only the domain filter, default intervention category and measure set differ. Four separate role definitions would mean maintaining four near-identical permission sets forever.
Permissions
Capability × role — scope is enforced separately, server-side
| Capability | Teacher | Reading Specialist | Behavior Specialist | Speech Therapist | Counselor | MTSS Coordinator | School Psychologist | Administrator | District Administrator | Parent / Guardian |
|---|---|---|---|---|---|---|---|---|---|---|
| View student profile | ||||||||||
| Log progress data | ||||||||||
| Create referral | ||||||||||
| Create / edit intervention plan | ||||||||||
| Approve Tier III plan | ||||||||||
| Approve tier movement | ||||||||||
| Record fidelity observation | ||||||||||
| Schedule / run MTSS meeting | ||||||||||
| Mark referral-ready → IEPCaseManager.ai | ||||||||||
| View compliance dashboard | ||||||||||
| View district analytics | ||||||||||
| Manage approved intervention library | ||||||||||
| Manage users & roles | ||||||||||
| Send parent communication | ||||||||||
| View audit log | ||||||||||
| Family portal access |
Shared vs role-specific
Why each page sits where it does
Shared shell, role-adaptive content
Dashboard
Same layout; "what to do next", queues and snapshot derived from role.
Students
Same table; scope ranges from 24 students to a whole district.
Student Intelligence Profile
Same tabs; landing tab differs (teacher → Data, psych → Readiness).
Universal Screening
Teachers see their class; coordinators triage the whole window.
Referral Wizard
Same 4 steps; teachers get more AI scaffolding, psych more raw data.
Task Engine
One queue, auto-assigned by role and workflow state.
Intervention Library
Same catalog; default filter = the user's domain.
Intervention Planner
Tier III plans need coordinator/admin approval.
Intervention groups
Grouping and scheduling for whoever delivers minutes.
Progress Monitoring
Measures pre-filtered by domain; identical entry surface.
AI Meeting Assistant
AI drafts different sections depending on attendee role.
Tier pipeline
Scoped to school or district; movement approvals gated.
Genuinely role-specific
Fidelity monitoring
Observation of adults, not students — different consent context.
Referral readiness
The legal seam to IEPCaseManager.ai; early access invites over-referral.
Compliance dashboard
Aggregate staff-performance data; not a practitioner surface.
District analytics
Cross-school equity and disaggregation — a governance surface.
Users & roles
School scope for principals, full scope for district.
Schools & windows
Calendars and screening windows define everyone's deadlines.
Approved interventions
Coordinators may propose; district approves.
Integrations
SIS, assessment vendors, IEPCaseManager.ai handoff.
Audit log
Immutable record of who saw and changed student data.
Family home
Plain language, translated, no staff-performance data.
Messages
Two-way, auto-translated communication.
Consent & notices
Signed notices and meeting invitations.
Page hierarchy
Six levels, no deeper
- L0Workspace shellIdentity, scope, AI command bar, notifications
- L1ZoneWork · Intervention · Oversight · Admin · Family
- L2PageDashboard, Students, Interventions, Tiers, Compliance…
- L3Record/students/:id · /interventions/:id · /meetings/:id
- L4TabOverview · Data · Interventions · Meetings · Documents · Readiness
- L5DrawerLog a score, add a plan, draft a parent note — never navigates away
L5 never navigates away. Every action an educator repeats many times a day happens in a drawer over the current context, so they never lose their place — that single rule is the mechanism behind the 50% documentation-time target.