Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Ringkasan User Invitation API
Cloud Identity User Invitation API memungkinkan Anda mengidentifikasi dan mengelola akun yang tidak dikelola sebagai bagian dari proses aktivasi pengguna ke domain Google Workspace atau Cloud Identity Anda.
Akun yang tidak dikelola ditentukan oleh kriteria berikut:
alamat email adalah akun konsumen dan merupakan alamat email utama akun tersebut, dan
domain alamat email cocok dengan domain Google Workspace atau Cloud Identity yang sudah diverifikasi
Akun ini umumnya ada karena salah satu pengguna pelanggan telah mendaftar ke layanan konsumen Google menggunakan alamat email kantor atau sekolahnya.
Jika pelanggan kemudian mendaftar ke Google Workspace atau Cloud Identity
dan menyediakan akun pengguna dengan alamat email utama yang sama dengan
akun yang tidak dikelola yang sudah ada, akun yang tidak dikelola tersebut akan bentrok dan
harus diselesaikan.
User Invitation API memungkinkan tugas penyelesaian kunci dapat diotomatiskan:
Tentukan apakah alamat email tertentu memenuhi syarat untuk bergabung dengan domain pelanggan (harus memenuhi kedua kriteria)
Mengirim undangan email ad-hoc atau batch ke alamat email yang memenuhi syarat agar mereka dapat bergabung ke domain pelanggan
Mengambil daftar akun yang tidak dikelola, yang dapat difilter menurut status undangan mereka. Semua akun yang tidak dikelola di domain pelanggan diperlakukan sebagai undangan pengguna yang belum dikirim (state==NOT_YET_SENT) hingga dikirim.
Mencari undangan tertentu berdasarkan alamat email
Membatalkan undangan yang sudah dikirim
Alur undangan pengguna memungkinkan pengguna akhir dan administrator memastikan bahwa data apa pun yang dibuat menggunakan akun konsumen dikelola oleh entitas yang tepat:
Jika pengguna akhir memiliki data terkait bisnis di akun konsumen dan menerima undangan, administrator dapat mengambil kepemilikan dan mengelola data sesuai dengan kebijakan pelanggan.
Jika data pengguna akhir tidak terkait dengan bisnis dan pengguna akhir menolak, undangan akan memberi tahu pengguna bahwa dia mungkin perlu mengganti nama alamat email di lain waktu jika admin membuat Akun Google baru untuknya. Administrator
dapat membuat akun terkelola baru dan mengeluarkan alamat email utama
akun konsumen, sehingga menimbulkan konflik. Pengguna akhir akan
diminta untuk mengganti nama alamat emailnya dengan alamat email lain setiap
kali dia login ke akun Google pribadinya.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[[["\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."]]
