Changes between Version 24 and Version 25 of BluePrintAuthorization

Timestamp:

06/19/10 15:17:22 (14 years ago)

Author:

Fran Boon

Comment:

--

BluePrintAuthorization

@@ -225 +225 @@
      * Currently this requires modifying {{{shn_register()}}} in {{{modules/sahana.py}}}
 
- * An Admin should be able to restrict access to records to just those within a certain GIS location (e.g. Country or Region)
+ * A Developer should be able to restrict access to records to just those within a certain GIS location (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)
-   * Patch {{{shn_has_permission()}}} & {{{shn_accessible_query()}}} to spot this special case &, if no other roles match, then do a lookup in another table (or deployment_settings dict)
-
- * An Admin should be able to restrict access to records to just those within a certain organisation (or the Focal Point for the organisation)
+   * 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)
+
+ * A Developer should be able to restrict access to records to just those within a certain organisation (or the Focal Point for the organisation)
   * 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()}}} & {{{shn_accessible_query()}}} to spot this special case &, if no other roles match, then do a lookup in another table (or deployment_settings dict)
+   * 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)
+
+ * A Developer should be able to restrict access to records to just those which the person created
+  * Add a special role 'Creator' 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 check between {{{auth.user.id}}} & {{{table.created_by}}}
 
  * If access to a record is restricted then access to messages relating to that record should also be restricted