Product: diferent interfaces for diferent roles

[JoniBife]

Users should have diferent roles, and according to the role a user
is allowed to perform diferent activities on a certain course. For example, a user with a student role
may only check information about a course whereas a teacher may manage the whole course,
including the participant users which can be "kicked" if necessary.

When it comes to the client app it should present a diferent interface according to the user type,
which presents the adequate features for each of them.

On the client app a user with the role:

• Student
  may join any subject and check its info
  can alter some resources and participate in events (e.g Tests, Discussions)
  requires the teacher permission to join a subject (could be a promotion from spectator to student)
• Teacher
  is the administrator of a subject and can alter info and manage the participants (students)
• Spectator
  may join any subject and check its info

Note : The Spectator role is probably unecessary because the subject info could just be made public. This would for sure simplify the model.