Kalpesh
0%
Admin Dashboard
Dashboard
Web app
UX UI design
Client:
What is Fyule Admin Dashboard
Every app students use in the Fyule ecosystem is managed from the admin dashboard. It is used by administrators from Fyuele team and school representatives to manage users, assign content, track progress, and manage what students can access.
I designed the admin dashboard as part of the broader Fyule ecosystem, alongside the three student-facing apps.
Note
This dashboard is an internal product, hence specific details of the project are not disclosed here. This case study focuses on approach to design with representative visuals to maintain confidentiality.
TL;DR
Challenge
Designing a control layer for non-technical users i.e. administrators and teachers; who needed meaningful oversight of a multi-product platform without any training or technical background. Complex data and multiple user roles to be catered with one interface.
• Manage users, roles and content.
• Create, Manage & Publish events/contests etc
• Manage tutorials and training content in LMS
• Schedule online masterclasses/cohorts etc.
• Push notifications, announcements and other important updates
Solution
A role-based dashboard prioritising scanability and task speed over feature richness. Clear information hierarchy, a consistent component system shared across the ecosystem, and an interface structured around what administrators actually need to do within their defined scope.
Here's what the 3 apps looked like
Now let's dive deeper…
Discovery
Research focused on understanding what administrators actually needed to do and what different levels of access, control and management is needed. Three primary tasks emerged from this:
Managing users: adding students, assigning them to classes, resetting access. This needed to be fast, repetitive-task friendly, and forgiving of errors.
Managing content: assigning curriculum content to specific classes and standards. This required clear filtering and a structure that mapped to how schools actually organise teaching, not how the database organises data.
Monitoring activity: understanding whether students were engaging with the platform, which content was being used, and where drop-off occurred. This needed to be scannable at a glance, not a detailed analytics report.
Information architecture
The IA was structured around these three tasks putting priority needs to the front making it effective for different user groups.
Primary navigation covered three areas: Users, Content, and Activity. Everything else including settings, account management, support was secondary navigation.
Designing for role based access
The dashboard served multiple user types with different levels of access:
Master admin with full access
Co-admins with specialized access
School admins with school facing access
Role-based design meant the same interface needed to surface different information depending on who was logged in, without creating confusion when a user's scope changed or when they needed to understand what they couldn't access and why.
Reception and impact
The Fyule admin dashboard streamlines administrative processes, enhancing efficiency in user & content management. Master admins gain comprehensive control, while school admins effectively manage their schools profile & students' content.
Reflection
Designing a dashboard is a specific discipline in itself with the goal to make it effective without overwhelming.
The most useful constraint on this project was designing within an existing system. Having worked with the cross-functional stakeholders allowed me to design for an array of users.
If I were doing it again, I'd involve at least one teacher in the discovery phase as a research participan, because the people who understand the workflow best are the ones using it daily.