确定合并 Google Workspace 组织后是否需要迁移 Google Chat 应用
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
如果您的 Google Workspace 组织或网域与另一个组织或网域合并,您可能还需要迁移 Chat 应用。合并并不总是会影响 Chat 应用,但如果您的 Chat 应用不再按预期运行,您可能需要更改 Chat 应用的配置方式。
请让管理员更新新组织中的设置
在迁移 Chat 应用之前,请咨询贵组织的管理员,了解管理设置是否会影响迁移。
更改管理设置可能会恢复 Chat 应用的完整功能,从而无需迁移。
您是否需要迁移 Chat 应用取决于合并后的 Google Workspace 组织中的管理设置,这些设置可能会导致您的 Chat 应用停止运行。例如,合并后的 Google Workspace 组织的管理员可能必须将您的 Chat 应用添加到许可名单中,或者必须允许用户安装该 Chat 应用。如需了解详情,请参阅允许用户安装 Chat 应用。
确定您的 Chat 应用是否需要迁移
如果满足以下任何条件,则您的 Chat 应用可能会完全正常运行,且无需迁移:
- 您的 Chat 应用已在 Marketplace 上发布。
- 您(Chat 应用开发者)在首次保存 Chat 应用配置时,是目标环境的成员。
- 您的 Chat 应用仅通过电子邮件地址与特定用户共享。组织合并后,用户的电子邮件地址保持不变。
合并组织后 Chat 扩展应用的访问权限
为确保您的 Chat 应用不会响应无权向其发送消息的用户,对您的 Chat 应用的访问权限仍仅限于创建该应用时所在的网域或组织。如果您在首次保存 Chat 应用配置时是目标环境的成员,那么您的 Chat 应用将继续按预期运行。如果您在首次保存 Chat 应用时是源环境的成员,那么用户能否保留或失去对您的 Chat 应用的访问权限取决于 Chat 应用的共享方式:
- 如果您的 Chat 应用是与
DOMAIN_NAME
中的所有人共享的,那么在合并后,现在属于目标环境的用户将无法再访问您的 Chat 应用。
- 如果您的 Chat 应用同时与特定用户和群组共享,那么在合并后,特定用户将保留对 Chat 应用的访问权限,但群组将失去访问权限。如需允许群组或整个网域向您的 Chat 应用发送消息,请迁移该 Chat 应用。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-08-29。
[null,null,["最后更新时间 (UTC):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)"]]