Add a NULLable foreign key from student to users. When this key is set the schedule is considered protected.
Only user who can authenticate as the correct user for the locked schedule can edit it. If view access should be equally restricted needs to be decided.
Users should '''only''' be allowed to lock schedules where {{{ username == slug }}}, this should save us the trouble of having to solve disputes over schedule names.
Add a NULLable foreign key from student to users. When this key is set the schedule is considered protected.
Only user who can authenticate as the correct user for the locked schedule can edit it. If view access should be equally restricted needs to be decided.
Users should '''only''' be allowed to lock schedules where {{{ username == slug }}}, this should save us the trouble of having to solve disputes over schedule names.