FHi
I think there are two solutions to this:
1) you can disable «User Loginname must contain orgdomain» to allow each user to reuse his mail as login
2) you could hide the suffix with the branding suffix https://docs.zitadel.com/docs/guides/manage/console/instance-settings#branding
I think there are two solutions to this:
1) you can disable «User Loginname must contain orgdomain» to allow each user to reuse his mail as login
2) you could hide the suffix with the branding suffix https://docs.zitadel.com/docs/guides/manage/console/instance-settings#branding
Instance settings work as default or fallback settings for your organizational settings. Most of the time you only have to set instance settings for the cases where you don't need specific behaviour in the organizations themselves or you only have one organization.
Fif you disable user loginname must contain orgdomain the suffix should not be shown actually.
Fat the moment we do have a bug when you switch this setting, because on one view in the queries the usernames are not correctly updated. we just merged the fix this morning. and will publish it to the cloud sometimes this week.
Fafter the fix the users will have the same loginnames as they had if you change the setting. And you have to manully change it if you like
FNot exactly. I make some examples to make the settings clear.
F"username must contina orgdomain" enabled: ordomain: acme.com username: fabienne, loginname: fabienne@acme.com
F"username must contina orgdomain" disabled: ordomain: acme.com username: fabienne, loginname: fabienne
F"username must contina orgdomain" disabled: ordomain: acme.com username: fabienne@acme.com, loginname: fabienne@acme.com
Fso if you have enabled it and send an org id scope on the authorize request. we will show the user automatically @acme.com so he only has to fill fabienne
Fif you hide it, acme.com is not shown and the user only has to fill fabienne