E-Mail as username already taken, user cannot join organization
Scenario
We as a company have the following scenario:
We offer various online services; most of them are for b2b customers and are paid. Here we simply create one organization per customer, which works wonderfully with zitadel.
But we also have a blog (wordpress) where users can register and comment. The blog is intended for everyone, including private individuals or employees of a company that is not a “customer” of ours.
Here it is neither possible nor sensible to assign users to a specific organization. Instead, we would create a general “public” organization and assign the users of the blog to it.
Problem
But now the following problem arises:
- the user peter@company.com registers for the blog and ends up in the “public” organization
- shortly afterwards company.com becomes a customer with us and gets its own organization “company”, to which the domain company.com is assigned
- peter@company.com cannot register / log in to “company” because he is already in “public”
- when trying to create / invite peter@company.com as manager of “company” directly via the console, the error “User already exists (V3-DKcYh)” appears (questionable from a security perspective, by the way, because of user enumeration, but this is a common trade-off and I understand the need)
We have emails as usernames, so according to zitadel they have to be globally unique, we are aware of that.
The problem with other usernames or domain suffixes is that it is a major UX killer for the 0815 default user, who is so used to emails and doesn't want to worry about domains, tenants etc.
Post is too long, see the comment below.
We as a company have the following scenario:
We offer various online services; most of them are for b2b customers and are paid. Here we simply create one organization per customer, which works wonderfully with zitadel.
But we also have a blog (wordpress) where users can register and comment. The blog is intended for everyone, including private individuals or employees of a company that is not a “customer” of ours.
Here it is neither possible nor sensible to assign users to a specific organization. Instead, we would create a general “public” organization and assign the users of the blog to it.
Problem
But now the following problem arises:
- the user peter@company.com registers for the blog and ends up in the “public” organization
- shortly afterwards company.com becomes a customer with us and gets its own organization “company”, to which the domain company.com is assigned
- peter@company.com cannot register / log in to “company” because he is already in “public”
- when trying to create / invite peter@company.com as manager of “company” directly via the console, the error “User already exists (V3-DKcYh)” appears (questionable from a security perspective, by the way, because of user enumeration, but this is a common trade-off and I understand the need)
We have emails as usernames, so according to zitadel they have to be globally unique, we are aware of that.
The problem with other usernames or domain suffixes is that it is a major UX killer for the 0815 default user, who is so used to emails and doesn't want to worry about domains, tenants etc.
Post is too long, see the comment below.
