From 6f3f67cde75def38972790bbd540435bd0be0812 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dominik=20M=C3=BCller?= Date: Wed, 31 Jan 2024 13:34:34 +0100 Subject: [PATCH] docs: self-hosting doc link (#7249) * fix: self-hosting doc link exchanged localhost link for relative link to docs * fix: updated base path for relative doc link --- docs/docs/self-hosting/manage/custom-domain.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/self-hosting/manage/custom-domain.md b/docs/docs/self-hosting/manage/custom-domain.md index 57da596985..65186d558b 100644 --- a/docs/docs/self-hosting/manage/custom-domain.md +++ b/docs/docs/self-hosting/manage/custom-domain.md @@ -48,7 +48,7 @@ Check out the [reverse proxy configuration examples](/self-hosting/manage/revers ## Organization Domains Note that by default, you cannot access ZITADEL at an organizations domain. -Organization level domains [are intended for routing users by their login methods to their correct organization](http://localhost:3000/docs/guides/solution-scenarios/domain-discovery). +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](/apis/resources/system/system-service-add-domain#adds-a-domain-to-an-instance). Be aware that you won't automatically have the organizations context when you access ZITADEL like this.