BETA Best Practices - Institutional Visible Courses and LTIs

Community Participant

I noticed some odd behaviour today in our beta instance in regards to a course with visibility is set to institution. Multiple accounts who can view the course in PROD could not in BETA and were given the error "Students are not allowed to access test installations."

I can rationalise this as any user viewing the institution visible course who doesn't have account or course level access is basically considered a student with view only access. Students are not allowed in beta, therefore you cannot view anything about this institution visible course in BETA without specific account/course level access.

While I think this is likely the reason, this is also frustrating as this is another component of our setup that we cannot fully test/try things out on in beta. We have the same complication with LTIs, particularly SCORM packages, as we cannot test those in beta.

How is your institution using the BETA and TEST environments?

We have a hard time understanding when we can rely on testing something in BETA or TEST as we often come across scenarios where we cannot use it fully. We are considering perhaps getting a second environment as a true test environment, but that presents it's own challenges as well.

I am a Canvas administrator for our institution and we have been using Canvas for a little over a year.