Changes between Version 23 and Version 24 of UserOptInConsent

Timestamp:

Sep 17, 2018, 2:38:21 PM (6 years ago)

Author:

skwang

Comment:

Add usage section and basic usage information.

UserOptInConsent

@@ -131 +131 @@
 === Anonymous Accounts ===
 
-(to be written)
+There may be cases where a user uses an Account Manager (AM) which has the feature of anonymous accounts. Effectively the user agrees to the AM terms-of-use. They do no see or agree to the projects terms-of-use. It is these cases where the `consent_not_required` flag is set in the `consent` table. However, it should be said that there is no 100% anonymity. Users' IP addresses are nearly always logged by the Web site server, and could be traced back to a user's account.
+
+To use this functionality, the create_account RPC is called with `consent_flag=0`.
+
+= Usage =
+
+From a project administrator's point-of-view. To enable the Opt-in feature:
+
+1. First in the OPS pages, go to "Manage consent types". All consent types are disabled by default. You should enable `ENROLL` and `STATSEXPORTS`, the two default consent types.
+1. You must add a `terms_of_use.txt` text file in the root of the project directory. This is the same directory `config.xml` may be found. This file must have the exact filename `terms_of_use.txt`, with underscores. It contains your projects terms-of-use text.
+1. `config.xml` must be updated: add XML `<enable_login_mustagree_termsofuse>1</enable_login_mustagree_termsofuse>` to the `<config>` section.
+  * Note: If this config option is **not** set, the behavior of the site will be as follows. New accounts, whether created from the BOINC client or the Web site, will see a terms-of-use dialog which the user must agree to. However, existing accounts, when they login, are not asked to agree to a terms-of-use.