TBD if we do this for all contacts, just for Italy and Austria contacts or for all European contacts.
Alternatively, we can consider a donor portal email change to be equivalent to a double opt-in.
TBD if we do this for all contacts, just for Italy and Austria contacts or for all European contacts.
Alternatively, we can consider a donor portal email change to be equivalent to a double opt-in.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | Lars | T407017 Epic: Double opt-in | |||
| Resolved | Ejegg | T407442 Record confirmed email change in email preferences centre as double opt-in activity in CiviCRM |
Does this get complicated if/when we start to send multiple streams of emails that people would be able to opt-in to separately? Or would an email address update initiated by the user imply global double opt in consent?
Does the timing of the task depend on wider roll out of the preference centre?
Change #1240016 had a related patch set uploaded (by Ejegg; author: Ejegg):
[wikimedia/fundraising/crm@master] Add double opt-ins from email prefs form
Change #1240025 had a related patch set uploaded (by Ejegg; author: Ejegg):
[wikimedia/fundraising/crm@master] Add double opt-in activity from email change
Change #1241008 had a related patch set uploaded (by Ejegg; author: Ejegg):
[wikimedia/fundraising/crm@master] Refactor Dbl Opt-In send into API action
I've asked legal just to confirm that we can count the confirm your email change message as a double opt in (or if we might need to conditionally add text based on the country).
Change #1241008 merged by jenkins-bot:
[wikimedia/fundraising/crm@master] Refactor Double Opt-In send into API action
Change #1240016 merged by jenkins-bot:
[wikimedia/fundraising/crm@master] Send double opt-in email on email prefs opt-in
Change #1240025 merged by jenkins-bot:
[wikimedia/fundraising/crm@master] Add double opt-in activity from email change