Good suggestions here. Sometimes multiple people in the same org are creating accounts. It will be important for us to have approval from the primary contact at that org to validate the new signup person is really working there.

Any progress on this?

They key piece is that when a new USER creates an account, there is no control on the ORGANIZATION. If I am a new development officer at an existing organization, I will type my my organization's name in the account creation screen and unknowingly create a duplicate. Instead, as the OP suggested, there should be a drop-down menu for organizations already in the system. The system could make suggestions as the user types. It should then pull the relevant information (address, EIN, etc.) from the organization on file and add the user to the existing organization.

It would be nice to be able to see the organizations that you want to merge side by side so it is easier to determine which org to keep. Right now you have to go way back to the beginning and search for the organization again and hope you aren't clicking into the one you just looked at. The merge process is very tedious and time consuming when you are trying to figure out which organization to merge into and what information would be lost in the merge.

I see two huge time-relievers here, especially with the way we're using our system.

1) It would be super-useful when you have organizations with high turnover (so... all of them?) so that every time Agency A has a new grants manager, you don't have to manually spin up a login for them, and they don't start spinning up duplicate organizations to clutter your system with junk.

2) We're rolling out a workaround for getting staff evaluators (community volunteers) in our system (mostly because I manually added over 100 of them by hand in the past six months and would like to not need to do that again in the next six months). One of the steps in our fix was putting all the evaluators in a "Volunteers" organization with a null EIN, so that when we ask new volunteers to sign themselves up, we can say "put in EIN 00-0000000" (because they're unlikely to know their employer's tax ID off the tops of their heads, and we'll be able to easily de-dupe the junk orgs these people will be generating).

That being said, the quickest fix I can see on addressing these issues and the original idea is a group above "Organization Information" on the Create New Account screen that has the same drop-down as the Create New / Edit User pages do (with all available organizations populating). Throw the rest of those sections on a branch based on their answer in there.

They either select one of the pre-existing orgs or say their org isn't in the list.
- If it's not, they fill out all information on that page as usual.
- If it is, they skip straight to User Information / Password.

I will say there's probably one extra step you'd want there, which would be to ask the administrator / primary contact at that org to validate the new signup person is really working there? But maybe that's just me.