Repository navigation
Phase 4: Implement the First Instructor Dashboard Slice #376
Description
Once the expansion model is defined, the roadmap should include a first implementation slice for Instructor Dashboard.
This should be the minimum implementation needed to make the new course roles coherent across the most relevant LMS-based course administration flows.
It should not be framed as a full Instructor Dashboard refactor.
A key requirement for this work is modularity. Instructor Dashboard sections should be updated in a way that keeps each section independently permission-aware, so future changes can be made without reworking the full dashboard.
Instructor Dashboard areas to evaluate
The first implementation slice should focus on the current Instructor Dashboard structure and define permission-aware behavior for each section:
| Section | Current actions or information |
|---|---|
| Course Info | View course information and pending tasks. No management actions expected. |
| Enrollments | Enroll learners, add beta testers, and view enrolled learners. |
| Course Team | Add team members and view existing Studio role assignments. |
| Grading | Manage grading-related actions. |
| Date Extensions | Manage learner date extensions. |
| Data Downloads | Manage access to available data download actions. |
| Open Responses | Manage open response workflows. |
| Cohorts | Manage cohort-related actions. |
| Reports | Manage access to available reporting actions. |
Data Downloads and Reports may require additional alignment because they can overlap with broader reporting and analytics work. For this roadmap, they should be included in the mapping, but only implemented if the required ownership and permission boundaries are clear.
Expected outcomes
- The affected Instructor Dashboard sections become permission-aware.
- Each section has clear access rules based on the agreed course roles.
- Course Team Management has a clear relationship with the Administrative Console.
- Users with restricted roles are not exposed to actions they should not perform.
- Legacy role behavior is preserved unless explicitly changed.
- The implementation is modular enough to support future section-level changes.
- The implementation is small enough to be estimated and delivered without pulling in the full LMS permission surface.
Activity