Email confirmation loop - simple design #46
thomasiles
started this conversation in
General
Replies: 1 comment
-
|
Does a code really need to expire after 7 days if it hasn't been used? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Submission email confirmation
Introduction
Trello card for this feature
As a form creator I want to be confident that the email address I set for email submissions is correct.
This feature adds a confirmation step to setting submission eamil when creating
forms. This should help ensure that the email is working and accessible for the
form creator.
Instead of directly editing the submission email address, a user must request
that a six digit code is sent to the email address. The user can then re-enter
this code to confirm that they have access to the email address.
Only one code per email is valid at any time per form.
Ability to clear the email address without setting a new one - maybe only in draft for the moment?
The admin will store the code, date sent, user who requested the code.
Workflow
The roles of Admin and API.
sequenceDiagram Actor User participant Admin participant Notify participant API User->>Admin: Request code to email address Admin->>Notify: Send confirmation code Notify->>User: Email code to address User->>Admin: Enter confirmation code Admin->>API: Set Email AddressFlow
A flow diagram showing the flow.
flowchart TD Start[Email blank] --> |User enters email address|Sent Sent[Email with code sent] --> |User enters code|Code Code --> |Code valid| Confirmed[Email set] Confirmed[Email set] --> |change email|Sent Confirmed[Email set] --> |clear email|Start Code{Code checked} --> |Code invalid| StartBeta Was this translation helpful? Give feedback.
All reactions