FI think you r case would work easier through the v2 api https://zitadel.com/docs/apis/resources/user_service_v2/user-service-add-human-user
Create/import a new user with the type human. The newly created user will get a verification email if either the email address is not marked as verified and you did not request the verification to be returned.
FHm, I see, so running each user separately against the API is not feasible?
How many users are we talking here?
How many users are we talking here?
Fcan you show us how you import the users? if you have set verified to true, the email should be set as verified
FThanks, I found the problem. It looks like we do have a bug,
FIn general a user is in initial state when the email is not verified or the password is not set
Fit looks like we somehow do ignore the verified true, when the user is in an initial state
Fthis means if you send a password, the email is set as verified as well