On 17/12/2014 03:22, Ryan Feeley wrote:
The user can be sent to the "account locked" screen as the result of three
actions:
1) sign in
2) delete account (from settings)
3) change password (from settings)
Thanks for this! I updated the flow to accommodate the additional cases.
I imagine the o
On 17/12/2014 04:09, Ryan Feeley wrote:
For most of our emails in the footer we say: This is an automated email; if you
received it in error, no action is required. For more information, please visit
Mozilla Support.
I am going to assume this is not appropriate for re-verification emails, as
For most of our emails in the footer we say: This is an automated email; if you
received it in error, no action is required. For more information, please visit
Mozilla Support.
I am going to assume this is not appropriate for re-verification emails, as the
user probably should keep the account
> The user can be sent to the "account locked" screen as the result of three
> actions:
> 1) sign in
> 2) delete account (from settings)
> 3) change password (from settings)
Thanks for this! I updated the flow to accommodate the additional cases.
> I imagine the original tab, if still open and v
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ryan, I'm having a look at the lucid chart now. In particular, I'm
looking at the bottom-right quadrant of the diagram.
The user can be sent to the "account locked" screen as the result of
three actions:
1) sign in
2) delete account (from settings)
3
+ dev-fxacct, rfk, and stomlinson
Francois is no longer on FxA. rfk and stomlinson are leading the implementation
of the locked account work.
-chris
On Dec 15, 2014, at 7:07 AM, Ryan Feeley wrote:
> Hi Chris and Francois,
>
> Here’s a first attempt at describing the user experience of th
6 matches
Mail list logo