Hi Kelly, unfortunately, as I explained, what was suggested doesn't work. Restricting access after the end date restricts access *at* the end date. We don't want that. We want the default read-only behavior. But only for a certain number of days (90), not until the end of the term, whenever that may be.
Obviously courses have graded content by the end of the semester (again, as I said), so no, they definitely, absolutely, can't "be unpublished!".
And since "un-conclude" doesn't appear to available via the API--and you can't change the effective dates of a concluded course via the API, either--it doesn't seem possible to retroactively restrict viewing in an automated way.
And, again, creating special term defs and sub-accounts is not sustainable at volume. We already have 24 Canvas terms per academic year and a proliferation of subaccounts to accommodate "normal" start and end dates; I'm not adding more to accommodate one-offs.
*IF* courses are created with the correct settings *and* nobody messes with them in the interim, we can go through and use restrict_student_past_view (https://canvas.instructure.com/doc/api/courses.html#method.courses.update_settings) to lock them after the fact, but if restrict_enrollments_to_course_dates gets unchecked manually that doesn't work.
There's no good way (apparently), to reliably remove access to a number of courses in bulk, at a particular point in time.
That's why I'm interested in hearing whether there was ever a good solution to OP's *original* question.
This discussion post is outdated and has been archived. Please use the Community question forums and official documentation for the most current and accurate information.