I have a question for all Bubblers, who are building enterprise / corporate applications which has many users and maybe a few administrators.
I am interested to know what others have implemented in the authentication of users when setting passwords for someone else?
Typically when registering for an app you can use double opt in, so they are sent a link to verify and then create a password etc.
But, if you are authentication on behalf of some one else - creating a password for them - do you invite them and including the temp password and have them change it when they first log in, or do you send them a link and get them to create a password, or do you just send them a user-name and password.
I would be interested to know what others have used in response to the clients requirements?
And I am sure it would be relevant to many Bubble enterprise app builders.