如果使用者的資料與業務無關，且使用者拒絕邀請，邀請函會通知使用者，如果管理員為他們建立新的 Google 帳戶，他們可能需要重新命名電子郵件地址。管理員可以建立新的受管理帳戶，並逐出消費者帳戶的主要電子郵件地址，進而造成衝突。使用者每次登入個人 Google 帳戶時，系統都會要求他們將電子郵件地址重新命名為其他電子郵件地址。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[[["\u003cp\u003eThe Cloud Identity User Invitation API helps manage unmanaged accounts during user onboarding to Google Workspace or Cloud Identity domains.\u003c/p\u003e\n"],["\u003cp\u003eUnmanaged accounts are consumer accounts whose email domain matches a verified Google Workspace or Cloud Identity domain, created because users signed up for consumer Google services with their work or school email.\u003c/p\u003e\n"],["\u003cp\u003eThis API automates key resolution tasks, like determining eligibility, sending invitations, listing unmanaged accounts, looking up specific invitations, and canceling sent invitations.\u003c/p\u003e\n"],["\u003cp\u003eThe user invitation process allows administrators to take ownership of business-related data from consumer accounts or inform users to rename their email if it's personal.\u003c/p\u003e\n"],["\u003cp\u003eThe API can be set up by following the steps in \u003ca href=\"/identity/docs/how-to/setup-user-invitations\"\u003eSetting up the User Invitation API\u003c/a\u003e, and more information on conflict resolution can be found in the Google Admin Help Center under \u003ca href=\"https://support.google.com/a/answer/6178640\"\u003eFind and manage existing accounts\u003c/a\u003e.\u003c/p\u003e\n"]]],[],null,["# User Invitation API overview\n============================\n\nThe Cloud Identity User Invitation API allows you to identify and manage\nunmanaged accounts as part of onboarding users to your Google Workspace or\nCloud Identity domain.\n|\n| **Beta**\n|\n|\n| This product is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA products are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nUnmanaged accounts are defined by the following criteria:\n\n- the email address is a consumer account and it's the primary email address of the account, and\n- the domain of the email address matches an existing verified Google Workspace or Cloud Identity domain\n\nThese accounts generally exist because one of the customer's users has signed\nup for consumer Google services using their work or educational email address.\nWhen the customer then signs up for Google Workspace or Cloud Identity\nand provisions a user account with the same primary email address as an\nexisting unmanaged account, that unmanaged account becomes conflicted and\nneeds to be resolved.\n\nThe User Invitation API makes key resolution tasks automatable:\n\n- Determine if a given email address is eligible to join the customer's domain (must meet both criteria)\n- Send ad-hoc or batch email invitations to eligible email addresses so they can join the customer's domain\n- Retrieve a list of unmanaged accounts, filterable by their invitation state. All unmanaged accounts on the customer's domain are treated as unsent user invitations (`state==NOT_YET_SENT`) until they are sent.\n- Look up a specific invitation by email address\n- Cancel already-sent invitations\n\nThe user invitation flow allows both the end user and the administrator to\nensure that any data created using the consumer account is managed by the\ncorrect entity:\n\n- If the end user has business-related data under the consumer account and accepts the invitation, the administrator can take ownership and manage the data according to the customer's policies.\n- If the end user's data is not business-related and they decline, the invitation gives the user notice that they may need to rename the email address later if the admin creates a new Google account for them. The administrator can create a new managed account and evict the primary email address of the consumer account, creating the conflict. The end user will then be asked to rename their email address to another email address every time they log in to their personal Google account.\n\nNext steps\n----------\n\nHere are a few next steps you might take:\n\n- To set up the API, refer to [Setting up the User Invitation API](/identity/docs/how-to/setup-user-invitations).\n- To understand how account conflict resolution works in the Admin Console, read [Find and manage existing accounts](https://support.google.com/a/answer/6178640) in the Google Admin Help Center."]]
