From b7af4c2162bf8ae1d97d99f764f7980cdfbd2d57 Mon Sep 17 00:00:00 2001 From: Tim Abbott Date: Thu, 31 May 2018 12:17:16 -0700 Subject: [PATCH] docs: Update multiple organization docs to clarify root domain story. Previously, we made it seem like it was a good idea to use a subdomain and a root domain at the same time. --- docs/production/multiple-organizations.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/docs/production/multiple-organizations.md b/docs/production/multiple-organizations.md index 94e82aa843..4aaf94c62b 100644 --- a/docs/production/multiple-organizations.md +++ b/docs/production/multiple-organizations.md @@ -70,8 +70,15 @@ into the database. Most Zulip servers host a single Zulip organization on the root domain (i.e. `zulip.example.com`). The way this is implemented internally involves the organization having the empty string (`''`) as its -"subdomain". You can mix having an organization on the root domain -and some others on subdomains (e.g. `it.zulip.example.com`). +"subdomain". + +You can mix having an organization on the root domain and some others +on subdomains (e.g. `subdivision.zulip.example.com`), but this only +works well if there are no users in common between the two +organizations, because the auth cookies for the root domain are +visible to the subdomain (so it's not possible for a single +browser/client to be logged into both). So we don't recommend that +configuration. ### The system bot realm