Changes between Version 6 and Version 7 of access_control

Timestamp:

2012-05-03T01:48:02Z (13 years ago)

Author:

Pan Luo

Comment:

--

access_control

@@ -41 +41 @@
 This type of permission controls if a role has access to a specific iPeer function. E.g. Admin can add instructors or instructor is not allow to add admin. Here is an example of the permission: function/user/admin/add
 
+==== List of Permission ====
+===== Function permissions =====
+||Key||Name||Description||
+||functions/user||USER||Operations on all users||
+||functions/user/superadmin||USER_SUPERADMIN||Operations on superadmin, e.g. add/delete||
+||functions/user/admin||USER_ADMIN||Operations on admin||
+||functions/user/instructor||USER_INSTRUCTOR||Operations on instructor||
+
 === !Organization/Faculty ===
 There is another level of access control in iPeer. Consider an admin at the faculty level should have access to all resources to his/her faculty, but not for other faculties. 
@@ -55 +63 @@
 <img src="https://docs.google.com/drawings/pub?id=1xS3SQWMAhuBCac50rwLc4QrmN63_Jv4SxH7CA6cCK28&amp;w=1395&amp;h=720">
 }}}
+
+