Skip to content

Define and enforce open vs. protected student pages #70

Description

@coderabbitai

Overview

The student layout currently imports AuthGuard but does not apply it, meaning all student routes are unprotected regardless of intent.

This issue tracks the work to:

  1. Identify open (public) student pages – pages that should be accessible without authentication (e.g., public course listings, landing/info pages).
  2. Identify protected student pages – pages that require an authenticated student session (e.g., application status, profile, enrolled courses).
  3. Apply AuthGuard correctly – either wrap the entire student layout with AuthGuard if all routes are protected, or introduce nested route groups (e.g., (protected) / (open)) with AuthGuard applied only to the protected group layout.

Context

Acceptance Criteria

  • Open student routes are accessible without a token.
  • Protected student routes redirect unauthenticated users appropriately.
  • AuthGuard (or equivalent) is applied to all pages that require authentication.
  • No dead imports remain in layout files.

Requested by

@blebelo

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions