EDLAN Product Roadmap
Role clarity · Tenant clarity · Workflow clarity — turning EDLAN into a role-specific education OS
The Main Product Gap
Not "lack of features" — it is role clarity, tenant clarity, and workflow clarity. Each screen should answer three things: who is using it, which school they are in, and what action to take next.
7
Areas Audited
50+
Exact Improvements
25
2050 AI Pillars
30
Day Action Plan
Login Screen
Turn a generic sign-in into a school portal selector
Ideal 4-Step Login Flow
Identify School
User enters school code, domain, or email prefix
School-Branded Login
Show school logo, name, SSO options, and academic year
Role Hints
Display role cards so users know which pathway to take
Correct Workspace
Route to role-specific dashboard immediately after sign-in
What's Already Good
The app already supports SSO-related login states, forgot-password, password reset, email verification, OTP/MFA, and "request access" / "access restricted" flows. This is a UX surfacing problem, not a platform limitation.
Exact Improvements
School Tenant Entry
Add a "School code / School name / Work email" field BEFORE password. If a user types teacher@greenhill.edu, auto-route them into the correct school workspace.
Role Entry Cards
Show four clear entry cards below the form: Admin, Teacher, Student, Parent. Don't make all users guess they share the same login flow.
SSO Visibility
If Google or Microsoft SSO is enabled for the school, show it BEFORE the password field — not as hidden secondary logic.
Visible Request Access Button
Add a prominent "Request Access" button since the frontend already supports restricted-access and approval flows.
Role-Based MFA Enrollment
After first successful login, prompt users to enroll in MFA based on role. Require it for admins and bursars.
Role-Aware Error Messages
Replace generic "invalid credentials" with messages like "No account found in this school workspace" or "Your access request is pending approval."
School Branding on Login
Once school is identified, show the school logo, name, and current academic year on the login screen.
Trust Signals Footer
Add a small footer: secure login, data privacy, help/contact, and system status link.