Guardian Dashboard

Giving guardians a role of their own, instead of a copy of the student experience

Role: Product Owner & Designer

Context

Beacon’s educator and student tools were built first. Guardians with a student on the platform had no equivalent. They logged in and saw exactly their child’s own experience, the same screens, the same view, just under a different login. There was no guardian role, only a duplicated student one.

The problem

Guardians only have a look into what their kids are doing, not how they’re doing. Guardians needed their own view built around a the question: what’s happening across all of my kids that I should know about, missed assignments, guardrail violations, the things that actually need a parent’s attention, not a student’s practice screen.

From concept to working experience

I translated the guardian experience into a working HTML prototype that simulates the full journey from SSO login through the guardian dashboard. Rather than presenting the dashboard as a set of static mockups, the prototype lets users move through the experience as a guardian would—entering through SSO, selecting their role, and navigating between the information that matters most with filterable graphics and actionable buttons on a configurable page

What I prototyped

• SSO authentication and role-based entry

• Guardian-specific dashboard and navigation

• Multi-student visibility and switching

• Assignment and activity monitoring

• Alerts for missed work and guardrail violations

• Student-level drill-downs for additional context

• Page configuration for a customized experience