Changes between Version 5 and Version 6 of BluePrint/UserManagement


Ignore:
Timestamp:
11/12/12 22:58:38 (12 years ago)
Author:
Michael Howden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • BluePrint/UserManagement

    v5 v6  
    1111== Use-Cases ==
    1212When a User registers and is approved, Sahana will automatically create them:
    13 * Staff Record (if they request it & Admin agrees)
    14 * Volunteer Record (if they request it & Admin agrees)
    15 * Member Record (if they request it & Admin agrees)
    16 * Membership of auth_groups (Roles)
    17  * minimally AUTHENTICATED
    18 * Membership of pr_groups (Teams, Mailing Lists)
    19 * Contacts
    20  * minimally EMAIL
     13* Staff Record (if they request it & Admin agrees) (IMPLEMENTED)
     14* Volunteer Record (if they request it & Admin agrees) (IMPLEMENTED)
     15* Member Record (if they request it & Admin agrees) (IMPLEMENTED)
     16* Membership of auth_groups (Roles) (IMPLEMENTED)
     17 * minimally AUTHENTICATED (IMPLEMENTED)
     18* Membership of pr_groups (Teams, Mailing Lists) (IMPLEMENTED)
     19* Contacts (IMPLEMENTED)
     20 * minimally EMAIL (IMPLEMENTED)
    2121* Extra fields (as per configuration)
    2222
    2323== Requirements ==
    24 * a deployment_setting to control what type of records (Staff, Vol, Member, etc) can be created for a new user
    25 * allow a URL var to be used to automatically determine the type of record to be created for that user, and hide the widget on the registration form
    26 * Show the administrator what types of records will be created for the user when they are approved.
    2724* Extra fields to collect (configurable - possibly included in above deployment_setting & possibly a separate one), e.g.:
    2825 * Disclaimer(s) - just a client-side JS requirement to tick box before submit
    … …  
    3734
    3835== Design ==
    39 * auth_user record would have to contain some sort of tracking of what types of records are linked to it.
    40 * s3_link_user would be extended to link the user to the different types of records
    4136
    4237== Implementation ==
    … …  
    4742* Don't force re-entry of password for Admin (or use a different screen for just changing the password?) on user update
    4843* Approve email should contain link to the specific User page
    49 * Populate sites widget from Organisation
    50 * Option to choose to create Staff or  Volunteer
     44* Populate sites widget from Organisation - issue with permissions for org_site to user FilterFiled
    5145* Email & Mobile -> Use Inline Form framework (when complete)
    5246* Multiple OrgAdmin approvers & asyn send of emails