Changes between Version 6 and Version 7 of S3/S3AAA/RecordApproval

Timestamp:

09/21/12 10:20:54 (12 years ago)

Author:

Dominic König

Comment:

--

S3/S3AAA/RecordApproval

@@ -66 +66 @@
 }}}
 
-''Note:'' that users can have review permission (=permission to ''see'' unapproved records) without need to also have approve/reject permission.
+  '''Note:''' that users can have review permission (=permission to ''see'' unapproved records) without need to also have approve/reject permission.
 
-''Note:'' REVIEW permission alone doesn't give any access to unapproved records: it merely extends the READ/UPDATE permissions so they also apply for unapproved records. That means, if the user besides REVIEW has only READ permission in this table, then they can ''read'' unapproved records but not update them. To do that, they would need REVIEW+UPDATE permission.
+  '''Note:''' REVIEW permission alone doesn't give any access to unapproved records: it merely extends the READ/UPDATE permissions so they also apply for unapproved records. That means, if the user besides REVIEW has only READ permission in this table, then they can ''read'' unapproved records but not update them. To do that, they would need REVIEW+UPDATE permission.
 
 The permission to review/approve/reject records of this role is realm-limited (see [wiki:S3AAA/OrgAuth] for more details).
 
-''Note:'' users can always only see approved records, unless they have review permissions and use the "review" method. For custom layouts, it is possible to implement custom views which include both groups of records by using the S3Resource API directly.
+  '''Note:''' users can always only see approved records, unless they have review permissions and use the "review" method. For custom layouts, it is possible to implement custom views which include both groups of records by using the S3Resource API directly.
 == Methods to Approve or Reject Records ==