Replies: 2 comments
-
The boolean defaults to False and CharField as empty until the step 3 when a user can start the process that first set the secret field and once the click the link the view in step 2 will make the boolean to True(as email verified) |
Beta Was this translation helpful? Give feedback.
0 replies
-
support using different state for the verification status field such UNVERIFIED, VERIFIED, FAILING |
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
-
We can support email verification for our users form the platform in the following steps
rapidpro/temba/orgs/models.py
Line 331 in fc777a1
Additionally we could also go further as below later
5) Start requiring verification for views such as exports
6) New signups get redirected to the the verification first
7) Require verification to use any feature once most users have been verified
Beta Was this translation helpful? Give feedback.
All reactions