#6 Option to send email to new user

[qirex]

When creating new users can we have a tick-box to determine whether an email is sent out to them?

Admin work often involves adding / removing users and having no choice over whether an email is sent out can result in confused users.

[Benjamin Schmitt]

User creation is a sensible task as it also creates the user's password.
The automated mail is the only way the password is sent to the new user.
We cannot send it at a later point (for example by button), because password is encrypted in database.

Furthermore, I think a new user has a right to be informed that an account in his name was created.

If you are only testing, why not simply set up a testing environment with mail addresses owned by yourself.

But for productive purposes, I think the way it is is just right.

[qirex]

It is great that the user's password is stored encrypted and emailed out but that doesn't mean it couldn't be done again with a button that regenerates and resends.

I don't really think it's a 'rights' issue. Software doesn't protect people's rights, that's down to the responsibility of the operators. Like you say there are plenty of other ways to stop the email being sent. It would just make life easier for the Admin if there was a tick box which could be used appropriately.

I have to disagree, I think for production purposes it's important that emails are not sent out unless the Sysadmin intends them to be.

[Benjamin Schmitt]

no contact since 2,5 years -> obviously no more interest
=> closing issue in a week (2017-01-11), if no more message from qirex