Roles and dashboards
Academia is built around role-based dashboards. Users do not land in one generic workspace. After login, the app resolves the user's primary role and routes them to the matching dashboard surface.
This page is now the role hub. Use it to choose the right role guide, then open the dedicated page for that audience.
How to use this guide
- Read Role map if you only need a quick ownership summary.
- Open one of the dedicated role pages if you are onboarding a specific audience.
- Open Project lifecycle if you want to switch from roles to workflow stages.
Fastest route through this guide
- Read Role map for the ownership summary.
- Open the dedicated role page that matches your audience.
- Continue to Project lifecycle if you want to understand how roles interact over time.
Role map
| Role | Typical responsibilities |
|---|---|
| Department head | Department setup, verification, invitations, governance, approvals |
| Coordinator | Operational readiness, assignments, evaluations, defense coordination |
| Advisor | Supervision, project feedback, reviews, student progress |
| Student | Group formation, project work, document submission, milestones, defense preparation |
| Evaluator | Evaluation scoring, assigned project review, defense schedule participation |
| Committee member | Committee review, defense participation, late-stage academic decision support |
Fast role chooser
| If your main question is... | Open this role page |
|---|---|
| How does a department get activated and governed? | Department head |
| How does day-to-day academic movement stay on track? | Coordinator |
| How do supervised projects improve through feedback? | Advisor |
| How does a student experience the platform from group formation to defense? | Student |
| How does formal scoring and defense review work? | Evaluator |
| How does committee review fit into defense and final decisions? | Committee member |
Best page by reader type
| Reader | Start here |
|---|---|
| Department head setting up a new department | Department head |
| Coordinator tracing academic operations | Coordinator |
| Advisor following review work | Advisor |
| Student learning the academic journey | Student |
| Evaluator preparing for scoring and defense | Evaluator |
| Committee member preparing for review sessions | Committee member |
How dashboard routing works
The frontend resolves the primary role after authentication and redirects users into a role-specific URL such as:
/dashboard/department-head/dashboard/coordinator/dashboard/advisor/dashboard/student/dashboard/evaluator/dashboard/committee-member
From there, each role gets its own navigation and allowed sections.
How the six roles fit together
The role pages are strongest when read as one connected operating model:
- The Department head activates the department and keeps governance visible.
- The Coordinator keeps proposals, assignments, and late-stage readiness moving.
- The Advisor supervises project quality through milestone feedback and approval.
- The Student experiences the platform as the main academic journey.
- The Evaluator performs the final formal review and defense-stage scoring.
- The Committee member joins late-stage review and helps complete committee-facing decisions around defense activity.
Role pages
Use these dedicated pages from the sidebar or the links below:
Best page after this one
| If you want to move from roles into... | Open this page | Why |
|---|---|---|
| the full end-to-end workflow | Project lifecycle | It shows how the six roles interact over time. |
| first-run department activation | Onboarding and first setup | It explains the department-head-first sequence behind the role model. |
| assignment and late-stage monitoring | Staff oversight and assignment | It shows where coordinator and department-head control becomes operational. |
| submission and review loops | Milestone delivery and advisor review | It is the clearest shared student-advisor workflow. |
Recommended role onboarding sequence
If you are introducing a new department to the platform, this is the cleanest operational order:
- Department head completes setup and verification.
- Department head invites coordinators and advisors.
- Coordinators and advisors confirm readiness.
- Department head invites students.
- Evaluators and committee members are invited when review and defense activity is approaching.
Related pages
Best next reads
- Open Department head if you are documenting first-run ownership.
- Open Coordinator if you want the operational control layer after setup.
- Open Student if you want the most workflow-heavy day-to-day view.
- Open Committee member if you need the committee-facing late-stage review layer.
- Open Project lifecycle if you want to see how these roles interact over time.