Sending a link to set a password isn't much better. Perhaps a way to force a password change on login would be better, which has more use elsewhere, such as being able to periodically force password changes
On 16 Nov 2016 8:13 p.m., "Aymeric Augustin" < aymeric.augus...@polytechnique.org> wrote: > Hello, > > I wouldn’t dismiss the idea so quickly. Adding staff users from your > company is a fairly common use case. > > Currently you have to email them a password and ask them to change it. > This doesn’t set a good example. > > The better solution is SSO with the corporate directory (often > ActiveDirectory or Google Apps), but not every project has taken the time > to configure that. > > Best regards, > > -- > Aymeric. > > On 16 Nov 2016, at 20:59, Tim Graham <timogra...@gmail.com> wrote: > > I don't think this registration model is common on most websites. > > On Wednesday, November 16, 2016 at 2:24:43 PM UTC-5, Bruno Ribeiro da > Silva wrote: >> >> Hello everyone, >> >> I have this simple idea that I think django could benefit from, which >> would be the option to create a user by an invitation from the django admin >> page. So the person who is creating a new user doesn't have to type a >> password neither a username for this new user. He would only fill a form >> with an email that the invitation would be sent to. Something like a reset >> password link but to add a new user. >> >> Do you think it would be useful? That would be accepted as a PR for some >> version in the future? What are your thoughts? >> >> I would like to implement it and contribute to django, but I need >> feedback from you guys. >> >> >> Thanks! >> >> -- >> Bruno Ribeiro da Silva >> Python Dev and Homebrewer! >> > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit https://groups.google. > com/d/msgid/django-developers/2c949269-59f5-4332-8803- > c2958f789336%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/2c949269-59f5-4332-8803-c2958f789336%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/django-developers/A7A9A23F-24C3-495D-93C4- > 12A9B859E9FC%40polytechnique.org > <https://groups.google.com/d/msgid/django-developers/A7A9A23F-24C3-495D-93C4-12A9B859E9FC%40polytechnique.org?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CALs0z1bNRW072KZNJkkxiU3wjOfELZZ0fP51DJUWiBSX64A%2Bow%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
