docs/features/student-administration.md ships the studio-admin Students view deliberately read-only:
Read-only in this iteration; cancel/edit actions are a possible follow-up.
Add admin actions to the student list/detail view (manage_students):
Cancel an upcoming lesson on the student's behalf (reuse the existing cancellation path — slot release + pending-payment voiding, see docs/features/lesson-booking.md "Cancellation").
Cancel/withdraw a group-class enrolment.
Edit basic account details (display name, email) where appropriate.
Where
Spec: docs/features/student-administration.md
Controllers under src/Auth/; booking/enrolment mutations go through the existing Booking\BookingRepository / GroupClass\EnrollmentRepository paths so payment-seam behaviour stays consistent.
Tests under tests/Unit/Auth/
## What
`docs/features/student-administration.md` ships the studio-admin Students view deliberately read-only:
> Read-only in this iteration; cancel/edit actions are a possible follow-up.
Add admin actions to the student list/detail view (`manage_students`):
- Cancel an upcoming lesson on the student's behalf (reuse the existing cancellation path — slot release + pending-payment voiding, see `docs/features/lesson-booking.md` "Cancellation").
- Cancel/withdraw a group-class enrolment.
- Edit basic account details (display name, email) where appropriate.
## Where
- Spec: `docs/features/student-administration.md`
- Controllers under `src/Auth/`; booking/enrolment mutations go through the existing `Booking\BookingRepository` / `GroupClass\EnrollmentRepository` paths so payment-seam behaviour stays consistent.
- Tests under `tests/Unit/Auth/`
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What
docs/features/student-administration.mdships the studio-admin Students view deliberately read-only:Add admin actions to the student list/detail view (
manage_students):docs/features/lesson-booking.md"Cancellation").Where
docs/features/student-administration.mdsrc/Auth/; booking/enrolment mutations go through the existingBooking\BookingRepository/GroupClass\EnrollmentRepositorypaths so payment-seam behaviour stays consistent.tests/Unit/Auth/