Changes between Version 27 and Version 28 of BluePrintOrganisationRegistry

Timestamp:

03/19/11 14:53:14 (14 years ago)

Author:

Fran Boon

Comment:

--

BluePrintOrganisationRegistry

@@ -160 +160 @@
  * Only staff of an organisation have permissions (READ, CREATE, UPDATE and/or DELETE) for their organisation resource.
  * Only staff stationed at a certain site have permissions (READ, CREATE, UPDATE and/or DELETE) for their site resource.
+
 For further flexibility, there are 2 boolean fields for staff:
  * {{{no_access}}} - If this is true, this staff member has no additional privileges (labelled as 'Read-only')
  * {{{supervisor}}} - This gives the options for more permissive permissions for some staff.
 
-This is done by the {{{shn_create_record_roles}}} function in {{{models/05_org.py}}}, which can be called from a org or site onaccept by configuring the onaccept for that resource as following:
+If a user creates a resource (Site or Organisation) then they are automatically given a staff record with Supervisor access to that resource.
+
+The roles are created by the {{{shn_create_record_roles}}} function in {{{models/05_org.py}}}, which can be called from an org or site create_onaccept by configuring the model as following:
 {{{
 # Create roles for each organisation / site instance
 s3xrc.model.configure(table, 
-                      onaccept = shn_staff_join_onaccept_func(tablename))  
+                       create_onaccept = shn_staff_join_onaccept_func(tablename))  
 }}}
 (This code should be called after the resource table is defined in the model)
 
-If a user creates a resource (Site or Organisation) then they are automatically given a staff record with Supervisor access to that resource.
 === Enabling Staff Permissions ===
  1. Set: