For an organization that has a private membership use of the website, who would need to approve all member registrations, it would be another step of security to have the option (ie a checkbox or toggle) to have a new password generated and sent upon approval.  

Reason is, Joe Cool could register using a name and email address of someone (Ann Member) who they know would be approved by the website admin, and then just wait a few days and login.  Joe wouldn't need to receive the confirmation email to that email address to have access to the site, and Joe would know what the username and password was.  The admin would assume that it was Ann Member who registered and they were approving.  

If a new password were generated and sent to the email address, then only Ann Member would have access to the approved password.  Currently the admin can go in and change the password manually, but doing this over and over for each approval is a lot of work - and so my thought of having this done automatically - as an option when approving someone or a group of people via a checkbox or toggle of some sort.

That's a solid point there on privacy and eliminating crafty avenues of abuse — I have tagged this as an accepted feature request. Thanks for taking the time to key in the valuable feedback.

Just a thought for your future knowledgebase and usage guide (not for my use but for potential buyers of your system) - there are so many ways to approach presenting information on how to use your system, but one might be to include a section on Registration Options.  Write up a number of optional scenarios and processes.  Having information like that is useful for some people who can't easily reason together a registration process, thus making the buying decision easier knowing that such a crucial step in having a successful website is already thought through and working.

Good point, agreed. Presenting information on a market like is a tricky venture, as the skill levels of potential users are so diverse — some will turn the system upside down after skimming through tense specification notes, while others will have never heard of most of it.

We definitely need a series of WWB 101 tutorials to cater to people who don't understand technicalese — the objective is to make it simple enough to let your grandmother's neighbour's old dog create a website.

the objective is to make it simple enough to let your grandmother's neighbour's old dog create a website.

That would be an interesting website!