Changes between Version 97 and Version 98 of BluePrintAuthorization

Timestamp:

07/04/10 16:32:53 (14 years ago)

Author:

Fran Boon

Comment:

--

BluePrintAuthorization

@@ -348 +348 @@
 === Location restriction ===
 e.g. Country or Region
- * Add a special role 'Geographic' which can be added to {{{writer_id}}} (& maybe {{{reader_id}}} although less use case for this)
+ * Add a special role 'Geographic' which can be added to {{{writer_id}}} or {{auth_permission}}.
   * Patch {{{shn_has_permission()}}} (& maybe {{{shn_accessible_query()}}}) to spot this special case &, if no other roles match, then do a lookup in another table (or deployment_settings dict)
  * NB If doing this through a table, then need to ensure that this table is protected appropriately
@@ -354 +354 @@
 === Organisation restriction ===
  * This could be all members of the Organisation or just the 'Focal Point'
- * Add a special role 'Organisation' which can be added to {{{writer_id}}} (& maybe {{{reader_id}}} although less use case for this)
-  * Patch {{{shn_has_permission()}}} (& maybe {{{shn_accessible_query()}}}) to spot this special case &, if no other roles match, then do a lookup in another table (or deployment_settings dict)
+ * Add special roles 'Organisation' & 'Focal Point' which can be added to {{{writer_id}}} or {{auth_permission}}.
+  * Patch {{{shn_has_permission()}}} (& maybe {{{shn_accessible_query()}}}) to spot these special cases &, if no other roles match, then do a lookup in another table (or deployment_settings dict)
  * NB If doing this through a table (such as a person's organisation), then need to ensure that this table is protected appropriately
 
@@ -363 +363 @@
 > permissions, and all others have yet other permissions, and finally we do not have
 > something like "members of organisations" at all.
+
 === Author restriction ===
 Only allow a user to update records which they created.