Changes between Version 1 and Version 2 of UserRoles
- Timestamp:
- 2010-05-31T15:56:32Z (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
UserRoles
v1 v2 1 == User Types Table ( aka User Roles)==2 The new User Types table will separate the specific types of users on site out of the PHP code. Thus, any institution would be able to modify existing user types, and create new ones. Each user types will have customizable permissions to access different components of the site. The permissions will tell what each type can do with each component.1 == User Roles == 2 The new User Roles table will separate the specific roles of users on site out of the PHP code. Thus, any institution would be able to modify existing user roles, and create new ones. Each user role will have customizable permissions to access different components of the site. The permissions will tell what each role can do with each component. 3 3 4 4 == iPeer Components == 5 5 Following is a list of components that each user can potentially access. Each one maps to a database table, or a set of tables (ex. evaluation tools). 6 6 * System Parameters 7 * User Types7 * User Roles 8 8 * Users 9 9 * Groups … … 21 21 ||1,2,3,5,6,7,9,10,11,13,14,15|| ...are all Reserved for future use. Should map to the next lower valid value. 22 22 The higher bits are reserved for flags.[[BR]] 23 +16) Can perform evaluations. This is how the system knows this person user type is a '''student'''. Flag(s) bellow relate to student permissions: [[BR]]23 +16) Can perform evaluations. This is how the system knows this person user role is a '''student'''. Flag(s) bellow relate to student permissions: [[BR]] 24 24 +32) Can list own group members & see some of their details (ex. names & email) [[BR]] 25 25 +64) Can see some details (ex names & email) of all students in the class. Must have at least Permission Level "Read" (>=4) for the Course. [[BR]] … … 27 27 == Suggested Default Table Contents == 28 28 29 || ||Short Char||Privilige Level||Sys.Params||User Types||Users ||Groups ||Courses ||Evaluation Tools||Events ||Messages ||29 || ||Short Char||Privilige Level||Sys.Params||User Role||Users ||Groups ||Courses ||Evaluation Tools||Events ||Messages || 30 30 ||'''Super Admin''' || S ||1200 ||R-W + C-D||R-W + C-D || R-W & C-D ||R-W & C-D||R-W & C-D||R-W & C-D ||R-W & C-D ||R-W & C-D|| 31 31 ||'''Faculty Admin''' || F ||1000 ||R ||R-W + C-D|| R-W & C-D ||R-W & C-D||R-W & C-D||R-W & C-D ||R-W & C-D ||R-W & C-D|| … … 45 45 * Ex: All users can always list the courses they are assigned to. They can also view the courses' details, but not the whole class list. 46 46 * One can not write any course, unless they are enrolled in it & have write permissions (R-W); or if they can create courses (R-W & C-D), regardless of enrollment. 47 * Only users of ''lower'' privilege levels can be created. No equal's creation is allowed. Same goes for user types.47 * Only users of ''lower'' privilege levels can be created. No equal's creation is allowed. Same goes for user roles. 48 48 * A user can view/modify another user, given that the target user is ''bellow'' this user's privilege level. 49 49