andwati/zitadel
1
0
Fork 0
mirror of https://github.com/andwati/zitadel.git synced 2026-11-12 17:15:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore: consistent naming for organization domain (#11356)

Browse Source 
# Which Problems Are Solved

As part of the consistent naming effort, this PR focuses on
"Organization domain".

# How the Problems Are Solved

- All terms referring referring to Organization Domains where changed to
be Organization Domain

# Additional Changes

None

# Additional Context

- closes [#11283](https://github.com/zitadel/zitadel/issues/11283)

---------

Co-authored-by: Copilot <[email protected]>
This commit is contained in:
Ramon
2026-02-18 14:46:21 +00:00
committed by GitHub
co-authored by Copilot
parent 699ed17918
commit b23346f6ca
78 changed files with 258 additions and 257 deletions
Download Patch File Download Diff File Expand all files Collapse all files
apps/docs/content/self-hosting/manage/cache.mdx
+2 -2
View File
@@ -179,12 +179,12 @@ For single instance setups which fulfilled all milestone (*your next steps* in t
### Organization
Most resources like users, project and applications are part of an [organization](/guides/manage/console/organizations-overview). Therefore many parts of the ZITADEL logic search for an organization by ID or by their primary domain.
Most resources like users, project and applications are part of an [organization](/guides/manage/console/organizations-overview). Therefore many parts of the ZITADEL logic search for an organization by ID or by their Organization Domain.
Organization objects are quite small and receive infrequent updates after they are created:
- Change of organization name
- Deactivation / Reactivation
- Change of primary domain
- Change of Organization Domain
- Removal
## Examples
apps/docs/content/self-hosting/manage/custom-domain.mdx
+1 -1
View File
@@ -50,7 +50,7 @@ Check out the [reverse proxy configuration examples](/self-hosting/manage/revers
Note that by default, you cannot access ZITADEL at an organization's domain.
Organization level domains [are intended for routing users by their login methods to their correct organization](/guides/solution-scenarios/domain-discovery).
However, if you want to access ZITADEL at an organization domain, [you can add additional domains using the System API](/reference/api/system/zitadel.system.v1.SystemService.AddDomain).
However, if you want to access ZITADEL at an Organization Domain, [you can add additional domains using the System API](/reference/api/system/zitadel.system.v1.SystemService.AddDomain).
Be aware that you won't automatically have the organizations context when you access ZITADEL like this.
## Generated Subdomains