Discussions missing for concluded students in a concluded course?

[canvas_admin]

I was just contacted by a student who has finished a course and his enrollment has been *concluded.* My understanding is that discussions should still be viewable to the student as read-only. 

Here is the student view when I masquerade as the student:

Here is my view:

The discussions are there for me as admin, but not for the concluded student. I need to determine if this is a broken feature in which case I need to submit a support ticket OR if Canvas changed functionality intentionally OR if this is related to the issue of grades not showing for concluded students: https://community.canvaslms.com/t5/Known-Issues/OPEN-Concluded-students-see-N-A-for-some-all-grades-...

The checkbox to prevent students from accessing the course after being concluded is NOT checked so that's not the issue. 

[mzimmerman]

Hi @canvas_admin 

According to the documentation at https://community.canvaslms.com/t5/Canvas-Resource-Documents/Canvas-Enrollment-Status-Comparison/ta-...

• Unless an instructor or admin restricts students from viewing concluded courses after a specific term, course, or section date, students can access the course but cannot submit assignments or participate in discussions. 

It's not clear from that if students can still view the discussion board if they are not allowed to participate.

The admin view of the discussions also shows that the discussions all had last postings several months ago.  If it possible that the discussions themselves are set to no longer be available to students? 

[canvas_admin]

@mzimmerman we are on rolling enrollment so the discussions do not have end dates; those are just the dates of the last post. The course in the screenshot has been archived because we refreshed it with updated lectures, etc.  So the course is concluded and student enrollments are concluded as well.  I haven't had this issue come up before so I assume students have been able to access past course discussions as "read only." But obviously, that is not working and I'm trying to discern if that is intentional or an accidental byproduct of some update.