Currently users are differentiated using a struct of three booleans which says whether the user isStudent, isInstructor, and isAdmin. With this approach however, we cannot tell what the user is currently logged in as.
The most common example is when instructors also have a student account and logs in as a student to see what the students can see. In this case the instructor should be treated as a student and not allowed to see instructor only stuff.
However, as we don't track what the user is currently logged in as, sometimes instructor logged in as a student end up seeing things which are instructor-only as in the boolean struct isInstructor is true.
Therefore, what user logged in as should be tracked during log in.
From arnold.k...@gmail.com on January 10, 2014 10:36:12
Currently users are differentiated using a struct of three booleans which says whether the user isStudent, isInstructor, and isAdmin. With this approach however, we cannot tell what the user is currently logged in as.
The most common example is when instructors also have a student account and logs in as a student to see what the students can see. In this case the instructor should be treated as a student and not allowed to see instructor only stuff.
However, as we don't track what the user is currently logged in as, sometimes instructor logged in as a student end up seeing things which are instructor-only as in the boolean struct isInstructor is true.
Therefore, what user logged in as should be tracked during log in.
Original issue: http://code.google.com/p/teammatespes/issues/detail?id=1475