Subscription-Based Tutoring Platform

Maintaining correct authorization and billing boundaries across users who pay, attend, teach, and administer.

Educational platforms rarely have symmetric users. In this system, parents purchase subscriptions, students attend sessions, teachers deliver instruction, and administrators manage operations.

These roles overlap in access but not in responsibility. Payment ownership, scheduling rights, visibility into progress, and administrative controls all differ depending on role. A mistake in permissions risks financial errors, privacy leaks, or operational failure.

The system had to reflect real-world authority structures rather than simplifying them for convenience.

The system focused on role-driven authorization and lifecycle correctness.

This centered on:

• Clear separation between payment ownership and service consumption
• Role-based access control enforced at the API level
• Subscription lifecycles tied to parents, not students
• Administrative permissions scoped by responsibility rather than status

Authorization was treated as business logic, not a UI concern.

Demonstrates the ability to model real-world organizational relationships in software without collapsing them into simplified user types.

Shows disciplined thinking around permissions, financial responsibility, and long-lived system correctness in user-facing platforms.