I can’t imagine that process being that troublesome or difficult.
Maybe, you could set a few up ahead of time so you’ll know the username and password works… then it would be just a matter of sending the new developer a username/password pair that you know works and then permission ‘up’ the role to whatever they needed.
Or you could even have them register as a user with the username/password they chose and promote that role as needed.
Any dev that has too much trouble logging in might be a good candidate to avoid if you know the username/password pair works in the first place. Though I’ve experienced issues receiving username/passwords myself.
If your username/password pairs are faulty (after ruling out fat fingers and extraneous or wrong characters) you’ll probably want to fix that first. A separate plugin would just make that process worse.
You might create the username/password pair using a less stringent password as a low permission role and only promoting that user after the dev changes the password himself. Again, if he can’t create a stronger password and make it work then maybe you don’t want him in there anyway.
And the minute they are done… zap them or demote.
