判斷在合併 Google Workspace 機構後是否需要遷移 Google Chat 應用程式
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
如果您的 Google Workspace 機構或網域與其他機構或網域合併,您可能也需要遷移 Chat 應用程式。合併作業不一定會影響 Chat 應用程式,但如果 Chat 應用程式不再正常運作,您可能需要變更 Chat 應用程式的設定方式。
請管理員更新新機構的設定
遷移 Chat 應用程式前,請先向貴機構管理員確認管理設定是否會影響遷移作業。變更管理設定後,Chat 應用程式可能就會恢復完整功能,不需要遷移。
是否需要遷移 Chat 應用程式,取決於合併後 Google Workspace 機構的管理設定,這些設定可能會導致 Chat 應用程式停止運作。舉例來說,合併後 Google Workspace 機構的管理員可能必須將您的 Chat 應用程式加入許可清單,或允許使用者安裝 Chat 應用程式。詳情請參閱「允許使用者安裝 Chat 應用程式」。
判斷是否需要遷移 Chat 應用程式
如果符合任何下列條件,您的 Chat 應用程式可能仍可正常運作,不需要遷移:
- 您的即時通訊應用程式已發布至 Marketplace。
- 您是即時通訊應用程式開發人員,在首次儲存即時通訊應用程式設定時,是目的端環境的成員。
- Chat 應用程式只會透過電子郵件地址與特定使用者共用。機構合併後,使用者的電子郵件地址不會變更。
合併機構後,Chat 擴充應用程式的存取權
為確保 Chat 應用程式不會回覆不應有權傳送訊息的使用者,只有在建立應用程式的網域或機構中,使用者才能存取該應用程式。如果您在首次儲存 Chat 應用程式設定時,是目的端環境的成員,Chat 應用程式就會繼續正常運作。如果您在首次儲存 Chat 應用程式時是來源環境的成員,則使用者是否會保留或失去 Chat 應用程式的存取權,取決於 Chat 應用程式的共用方式:
- 如果您的 Chat 擴充應用程式是與「
DOMAIN_NAME
中的所有人」共用,合併後,現在屬於目標環境的使用者將無法存取您的 Chat 擴充應用程式。
- 如果 Chat 應用程式同時與特定使用者和群組共用,合併後,特定使用者仍可存取 Chat 應用程式,但群組會失去存取權。如要允許群組或整個網域傳送訊息給 Chat 應用程式,請遷移 Chat 應用程式。
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-08-29 (世界標準時間)。
[null,null,["上次更新時間:2025-08-29 (世界標準時間)。"],[[["\u003cp\u003eGoogle Workspace organization or domain mergers may require Chat app migration if functionality is affected due to administrative settings in the new environment.\u003c/p\u003e\n"],["\u003cp\u003eChat app migration may be unnecessary if the app is published on the Marketplace, the developer was initially a member of the destination environment, or it's shared with specific users whose email addresses remain unchanged.\u003c/p\u003e\n"],["\u003cp\u003eAccess to Chat apps post-merger is limited, and users might lose access depending on the app's sharing settings; migration may be necessary to grant access to the entire new domain or specific groups.\u003c/p\u003e\n"],["\u003cp\u003eAdministrators should update settings in the merged organization and check if those resolve any functionality issues before migrating the app.\u003c/p\u003e\n"]]],["Google Workspace mergers can affect Chat apps, potentially requiring migration. Administrators should check settings, such as allowlists or user installation permissions, as these could restore functionality. Migration might be unnecessary if the app is Marketplace-published, the developer was in the destination environment, or it's shared with specific unchanged email addresses. Post-merger access is limited to the original domain; domain-wide sharing loses destination users' access, and shared groups lose access unless the app is migrated.\n"],null,["# Determine if Google Chat apps need to migrate after merging Google Workspace organizations\n\nIf your Google Workspace organization or domain merges with another one, you\nmight need to migrate your Chat app too. Mergers don't\nalways affect Chat apps, but if your\nChat app is no longer behaving as expected, you might\nneed to change how the Chat app is configured.\n| **Note:** When your Google Workspace domain merges or changes, you receive an email saying that your organization has (or will soon have) a new domain administrator. For more information, see [My Google Account is now managed by an administrator](https://support.google.com/a/users/answer/9172697).\n\nAsk your administrator to update settings in the new organization\n-----------------------------------------------------------------\n\nBefore migrating your Chat app, check with your\norganization's administrator to see if administrative settings are affecting it.\nChanging an administrative setting might restore full functionality to your\nChat app and make migration unnecessary.\n\nWhether or not you have to migrate your Chat app is\ndetermined by administrative settings in the merged Google Workspace\norganization that might cause your Chat app to stop\nworking. For example, the administrator of the merged Google Workspace\norganization might have to add your Chat app to an\nallowlist, or might have to let users install th\nChat app. For more information, see\n[Allow users to install Chat apps](https://support.google.com/a/answer/7651360)\n\nDetermine if your Chat app need to migrate\n------------------------------------------\n\nIf *any* of the following conditions are true, then your\nChat app might remain fully functional with no need to\nmigrate:\n\n- Your Chat app is [published on the Marketplace](/workspace/marketplace/how-to-publish).\n- You, the Chat app developer, were a member of the destination environment when you first saved your Chat app configuration.\n- Your Chat app is only shared with specific users using their email addresses. Users' email addresses remain the same after the organizations are merged.\n\nChat apps access after merging organizations\n--------------------------------------------\n\nTo make sure that your Chat app doesn't respond to\nusers who shouldn't have permission to message it, access to your\nChat app remains limited to the domain or organization\nunder which it was created. If you were a member of the destination environment\nwhen you first saved your Chat app configuration,\nthen your Chat app continues to work as expected. If\nyou were a member of a source environment when you first saved your\nChat app, then whether people retain or lose access to\nyour Chat app is determined by how the\nChat app is\n[shared](/workspace/marketplace/how-to-publish#audience):\n\n- If your Chat app is shared with **Everyone in \u003cvar translate=\"no\"\u003eDOMAIN_NAME\u003c/var\u003e**, then after merging, users who are now part of the destination environment lose access to your Chat app.\n- If your Chat app is shared with both specific users and groups, then after merging, the specific users retain access to the Chat app, but the groups lose access. To allow groups or the entire domain to message your Chat app, migrate the Chat app.\n\nRelated topics\n--------------\n\n- [Migrate your Google Chat app](/workspace/chat/migrate-apps)\n- [Allow users to install apps](https://support.google.com/a/answer/7651360)"]]