Changes between Version 4 and Version 5 of TracDev/Proposals/EmailValidation

Timestamp:

Dec 6, 2010, 10:37:58 PM (13 years ago)

Author:

Carsten Klein <carsten.klein@…>

Comment:

—

TracDev/Proposals/EmailValidation

@@ -6 +6 @@
 
 == The Context ==
-User enters a new or changes an existing email address in the general preferences tab. Under both circumstances, a verification email must be sent to the
-user containing a link that will validate the email address to the system, so that the change will come into effect.
+
+User enters a new or changes an existing email address in the general preferences tab or a different tab from a different contributor.
+Under all circumstances, a verification email must be sent to the user containing a link that will validate the email address to the system, so that the 
+change will come into effect and the email address will be considered safe for sending notification emails to.
 
 But the general preferences tab is not the only place where user's might enter an email address. Similar input fields exist in the ticket system where
@@ -17 +19 @@
 mails and in turn receiving notification from the user upon clicking on the verification link. In the general preferences tab a notification must be
 shown that the email address still needs validation and also a resend email verification mail button must be present.
+
+- users need to register their email address with the system in order to receive notifications
+  and also having them validate their email addresses via the notification subsystem
+- email addresses must be entered in the general preferences tab and will be stored in the session
+- only one default email address can be associated with a given user
+- other preference contributors may opt the user for entering alternate email addresses for different
+  purposes, and, if none was specified, they must fall back to default email address, if available
+- alternate email address entry forms, for example in the ticket system, must register the specified
+  email address with the session on behalf of the user, and, for as long as that email address was
+  not validated, the user must not be able to opt in for notification
 
 === i18n requirements ===