🐛 Bug Report: Adding a non-existing user to a team as a member creates a password less user

[anelad]

👟 Reproduction steps

1. create a team in Appwrite admin console
2. click on add member. it will ask for email, name and roles.
3. Enter an email that is not used by any of existing users, Appwrite will create a user for that email.

👍 Expected behavior

It should ask for a password for that new user

👎 Actual Behavior

It actually doesn't ask for a password so the created user is passwordless.

I'd suggest 'Add an existing user' and 'add a new user' buttons, first is a dropdown input where you select existing users, and the second is the same with current form, except it will ask for a password too.

🎲 Appwrite version

Version 0.13.x

💻 Operating system

Linux

🧱 Your Environment

No response

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[eldadfux]

This might make sense to the console, but not sure it will work from the client SDK. Should an owner set a password for a new user?

@TorstenDittmann is there any way for us to split this endpoint and keep current REST conventions?

[lohanidamodar]

@eldadfux what makes more sense is for the invited user when accepting the invitation, to set the password right?

[stnguyen90]

related: appwrite/console#1472

[stnguyen90]

Closing as this is the expected behavior and we don't have any plans to change it