Thanks Eduardo, I will try that!
On Saturday, August 26, 2017 at 2:05:22 PM UTC-6, Eduardo Balbinot wrote: > > You could do like this: when the user signs in you create the user in the > database and flags is_active as False, so the user won't be able to log in. > In your extended User model you could have another flag like > has_confirmed_email which you also set to False. When the user confirms the > email you set has_confirmed_email to True so you can have a page that shows > the admin which users are not active but have confirmed their email > addresses. Finally, the admin confirms a user which means in the background > you set is_active to True and then the user is able to log in to your > system. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/b853fe36-b96a-4820-921c-28207fd9a4f6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
