Changes between Version 21 and Version 22 of BluePrintAuthorization

Timestamp:

06/19/10 15:04:58 (15 years ago)

Author:

Fran Boon

Comment:

More use cases

BluePrintAuthorization

@@ -201 +201 @@
    * Simply add the Authenticated group (2) to the table (or records in the table if using Option 3)
    * ~~This requires all authenticated users to be added to the 'Authenticated' group~~
+  * What if just some fields should be protected?
 
  * A Person's Subscriptions shouldn't be visible by default.
@@ -219 +220 @@
    * 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)
+  * 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)
+
  * If access to a record is restricted then access to messages relating to that record should also be restricted
   * unless routed somewhere visible as well!
@@ -226 +231 @@
   * Need special handling for this in shn_create/shn_update?
    * Might need to differentiate the 2 (can deposit new but not edit existing)
+  * Might want to be have new records by unauthenticated users not be visible in lists until an admin has approved them
 ----
 BluePrintAuthenticationAccess