What is the process that other people use?

Right now, parents give us their e-mail address via the Inquiry form. After we process the Inquiry, we assign usernames and passwords.

We use the "username generator," and then in the notification that is part of that process, we give everyone in that "batch" the same password, as there is no merge field for "password," only "username."

Then, right before we send off the notification and complete the "username generator" process, I open another window and go into each user's profile in the Core and assign them a temporary password- the one listed in the static notification.

Being able to assign a temporary password in the same space where we assign usernames, and then having a connecting merge field for the notification would be ideal, and would allow for a greater range of temporary passwords.

They can be two separate steps. We need the ability to automatically create a login name (as we do) and also the ability to create temporary passwords as a group, versus one by one. Too many people are having problems logging into to start their applications. I hope this makes sense.
Tina McCurry
Christchurch School
Admission Assistant
49 Seahorse Lane
Christchurch, VA 23031
804-758-2306 x122
www.christchurchschool.org

Hi Tina and Jen, 

Sending both in the same email prevents a security risk, for example what if the email address is incorrect? We are definitely open to making the process more streamlined for parents. 

Ditto!  Can we create the temporary passwords as a step in the username generator task? Then we could use that as a field in our automatic email that would send them their username and temp password!

URGENT...We have "User Name Generator", may we PLEASE have a "Temporary Password Generator."  This would cut down on so many of our applicants having login problems for the application.