@kona ,
Our online program adopted Quality Matters (QM) this year and before the first course went through review I looked at how we could bring a reviewer into Canvas without giving them access to things they didn't need, but also creating an environment where they had access to all the things a student would have access to. After looking at the different roles that we have in Canvas I concluded that there needed to be something different for these courses. This is what I came up with.
#1. I created a new sub-account where a version of these courses live that allows the reviewer to interact with the content in the same way that a student would have in a regular course. I named this sub-account "Course Reviews" and placed it under our Manually Created course sub-account. This allowed us to basically create master shells for the courses that were going through review and it allowed for the course to live "outside" of the other sub-accounts, courses, and students.
#2. I created three reviewer accounts that had a generic login and password. Each password is specific to an account and it logged in a Google Doc that my team has access to. A calendar event was created to revisit the accounts and change the password at the end of each review cycle.
#3. The reviewers use a non-authenticated URL to gain access to Canvas. This allows us to bypass the AD tree that everyone else needs to use. We could create the accounts through AD and we may in the future if we feel this is becoming a security risk. Right now those accounts only have access to what we put them in so I feel that it is a low-risk situation.
#4. Each reviewer account is added manually to the course that needs to be reviewed. I then change the role of the reviewer to a student and the professor links all of the textbook content much like they would if it was a "real" course.
#5. We work with each publisher and give them the reviewer account information and explain that this account needs access for review purposes only. The publishers then grant access on their end and we make sure the connections work before the actual reviewer logs into the course.
#6. Once the review is complete the reviewer accounts are removed from the course. This ensures that even if the reviewer tried to access our LMS they wouldn't have access to anything.
So far this is working for us. It is not the best solution, but it is a solid workaround for the time being. I could simplify things by adding the reviewer accounts to the course through a CSV, but for me, it is easier and faster to add them manually and then change their role, accept the course invitation, and make sure everything works.
Jesse
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.