We are looking to see if there is current functionality, or an alternative capability, to allow our admins to lock a course in the cms studio? Or, if this is planned functionality in a future release?
Desired functional behavior:
Admin can lock/unlock a course
When a course is “locked” course teams can view the course, subsections, and units but, would not be able to add/update/delete/publish changes.
Desired UI behavior:
When a course is locked it has a visual indicator it is locked (lock icon, or color border etc)
** this applies to the course list page and course detail pages
If there are ways to manage this without the actual locking capability we would also welcome those thoughts. (roles?, groups?, users?, course teams? etc.)
Thanks in advance for any replies or thoughts around this topic!
It’s not exactly what you are describing, but here is current pull request that will allow Course Admins to stop Course Staff from deleting course sections, by hiding the trash icon.
Alternatively you can remove the Course Staff from the course, but then they cannot view it which is not ideal for you either.
Thanks @Dean! Yeah, we have looked into the removing of the staff from the course. It is a lot of manual work for our course team. Also, there are some requirements that we have been asked for that our course team wants to still be on the course so that they can continue to view everything.
Edit to the above Request:
Instead of it being the “admin” locking the course we are looking for the “superuser” locking and unlocking the course. I don’t see how to edit my post, or I would.
Good Evening Team,
We are trying to gauge if the “Course Locking” feature is something that others are interested in or if this is something unique to our team.
Reason for the question:
We are trying to determine if this makes sense to look at trying to get this into the open edX core functionality or if it is something that we should just handle as a one-off because it is a unique request to just our team.
Thanks in advance for your comments/replies/likes!
Disclaimer:
We are not committing to developing this feature. Just looking at getting information to help our team make an informed decision on a path forward.