One user as ORG_OWNER across multiple organizations ā recommended pattern?
āQuestionā
Solved
Hi all 
I'm setting up Zitadel as our CIAM and want to validate the right pattern for a multi-org scenario before I build it the wrong way.
What I want to achieve
- Customers self-register normally ā they land in our default CIAM org
- A customer can then create their own organization (think: workspace / tenant)
- The same customer can create or be invited to multiple organizations over time
- All of this should be tied to one user identity ā one login, one MFA, one profile
What I've understood so far
- A user belongs to exactly one organization (their home org) and can't be moved
- The built-in
- Manager roles / external user role assignments seem to be the mechanism to give an existing user permissions in another org via the global user search
My question
What's the recommended way to make one CIAM user act as ORG_OWNER of multiple newly-created organizations without producing duplicate user records?
My current plan:
1. From my app backend, call the admin API to create the new org
2. Assign the existing CIAM user as a manager with ORG_OWNER role on the new org
3. In the app UI, show an org switcher based on the user's grants/manager memberships, and pass
I'm setting up Zitadel as our CIAM and want to validate the right pattern for a multi-org scenario before I build it the wrong way.
What I want to achieve
- Customers self-register normally ā they land in our default CIAM org
- A customer can then create their own organization (think: workspace / tenant)
- The same customer can create or be invited to multiple organizations over time
- All of this should be tied to one user identity ā one login, one MFA, one profile
What I've understood so far
- A user belongs to exactly one organization (their home org) and can't be moved
- The built-in
/ui/login/register/org/ui/login/register/org form creates a brand-new user each time, so a single person creating three orgs would end up with three separate accounts ā not what I want- Manager roles / external user role assignments seem to be the mechanism to give an existing user permissions in another org via the global user search
My question
What's the recommended way to make one CIAM user act as ORG_OWNER of multiple newly-created organizations without producing duplicate user records?
My current plan:
1. From my app backend, call the admin API to create the new org
2. Assign the existing CIAM user as a manager with ORG_OWNER role on the new org
3. In the app UI, show an org switcher based on the user's grants/manager memberships, and pass
x-zitadel-orgidx-zitadel-orgid (or the org scope) when acting in a specific org context
