Silvan

thanks for clarification. i will add it as soon as i have a proper proposal for it

@Lan-Phan I have added a slightly different approach to the proposal: IMO ZITADEL is not interested in multiple contact emails and phones because it only must be able to contact...

as proposed by @yordis the `bind_*`-fields of the `UserIdentificator`-message were removed and the field renamed to login_name. Additionally the login_names were moved to the `Authenticator`-method to align the `User`- with...

Hi @HungryHowies There is another discussion about actions which discusses customisation of zitadel: https://github.com/zitadel/zitadel/discussions/6926 You can store information on the user but you will need actions to make use of...

one possibility of the flow would be as follows: 1. user hits /authorize using wrong configuration 2. misconfiguration is stored in backend 3. error page including button which redirects to...

~~I added state `Initial` after our discussion because I think it could make sense to initiate a user if the client of ZITADEL wants to do additional checks like address...

Hi We fixed zitadel setup cleanup so that it can cleanup all steps. You might have to run it multiple times until all steps are cleaned up because it manipulates...

I just saw that you wrote cleaRup instead of cleaNup. So which of those did you use?

After cleanup worked how did you setup or start-from-* zitadel? Including the flag or not?

Hm ok that looks correct on the first view. the setup completed successfully?