Mengonfigurasi layar izin OAuth dan memilih cakupan
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Saat Anda menggunakan OAuth 2.0 untuk otorisasi, Google akan menampilkan layar izin kepada pengguna yang mencakup ringkasan project Anda, kebijakannya, dan cakupan akses otorisasi yang diminta. Mengonfigurasi layar izin OAuth aplikasi Anda menentukan apa yang ditampilkan kepada pengguna dan peninjau aplikasi, serta mendaftarkan aplikasi Anda sehingga Anda dapat memublikasikannya nanti.
Untuk menentukan tingkat akses yang diberikan ke aplikasi Anda, Anda perlu mengidentifikasi dan
mendeklarasikan cakupan otorisasi. Cakupan otorisasi adalah string URI OAuth 2.0 yang berisi nama aplikasi Google Workspace, jenis data yang diakses, dan tingkat akses. Cakupan adalah permintaan aplikasi Anda untuk menggunakan data Google Workspace, termasuk
data Akun Google pengguna.
Saat aplikasi Anda diinstal, pengguna akan diminta untuk memvalidasi cakupan yang digunakan oleh aplikasi. Secara umum, Anda harus memilih cakupan yang paling berfokus dan menghindari permintaan cakupan yang tidak diperlukan aplikasi Anda. Pengguna lebih
bersedia memberikan akses ke cakupan terbatas yang dijelaskan dengan jelas.
Semua aplikasi yang menggunakan OAuth 2.0 memerlukan konfigurasi layar izin, tetapi Anda hanya perlu mencantumkan cakupan untuk aplikasi yang digunakan oleh orang di luar organisasi Google Workspace Anda.
Tips: Jika Anda tidak mengetahui informasi layar izin yang diperlukan, Anda dapat menggunakan informasi placeholder sebelum rilis.
Demi alasan keamanan, Anda tidak dapat menghapus layar izin OAuth 2.0 setelah Anda mengonfigurasinya.
Jika sudah mengonfigurasi , Anda dapat mengonfigurasi setelan Layar Izin OAuth berikut di Branding, Audiens, dan Akses Data.
Jika Anda melihat pesan yang menyatakan belum dikonfigurasi, klik Mulai:
Di bagian Informasi Aplikasi, di Nama aplikasi, masukkan Nama aplikasi.
Di Email dukungan pengguna, pilih alamat email dukungan yang dapat dihubungi pengguna jika mereka memiliki pertanyaan tentang izin mereka.
Klik Berikutnya.
Di bagian Audiens, pilih jenis pengguna untuk aplikasi Anda.
Klik Berikutnya.
Di bagian Informasi Kontak, masukkan Alamat email tempat Anda dapat menerima notifikasi tentang perubahan apa pun pada project Anda.
Jika Anda memilih Eksternal untuk jenis pengguna, tambahkan pengguna pengujian:
Klik Audiens.
Di bagian Pengguna pengujian, klik Tambahkan pengguna.
Masukkan alamat email Anda dan pengguna uji resmi lainnya, lalu klik Simpan.
Jika Anda membuat aplikasi untuk digunakan di luar organisasi Google Workspace Anda, klik Akses Data>Tambahkan atau Hapus Cakupan. Sebaiknya lakukan praktik terbaik berikut saat
memilih cakupan:
Pilih cakupan yang memberikan tingkat akses minimum yang diperlukan oleh aplikasi Anda. Untuk daftar cakupan yang tersedia, lihat Cakupan OAuth 2.0 untuk Google API.
Tinjau cakupan yang tercantum di setiap dari tiga bagian: cakupan tidak sensitif, cakupan sensitif, dan cakupan terbatas. Untuk cakupan apa pun yang tercantum di bagian
"Cakupan sensitif Anda" atau "Cakupan terbatas Anda", coba identifikasi
cakupan alternatif yang tidak sensitif untuk menghindari peninjauan tambahan yang tidak perlu.
Beberapa cakupan memerlukan peninjauan tambahan oleh Google. Untuk aplikasi yang hanya digunakan secara internal oleh organisasi Google Workspace Anda, cakupan tidak tercantum di layar izin dan penggunaan cakupan sensitif atau terbatas tidak memerlukan peninjauan lebih lanjut oleh Google. Untuk mengetahui informasi selengkapnya, lihat
Kategori cakupan.
Setelah memilih cakupan yang diperlukan oleh aplikasi Anda, klik Simpan.
Untuk mengetahui informasi selengkapnya tentang cara mengonfigurasi izin OAuth, lihat
Mulai menggunakan .
Kategori cakupan
Beberapa cakupan memerlukan peninjauan dan persyaratan tambahan karena tingkat atau jenis akses yang diberikan. Pertimbangkan jenis cakupan berikut:
[null,null,["Terakhir diperbarui pada 2025-08-04 UTC."],[[["\u003cp\u003eWhen using OAuth 2.0 for authorization with Google Workspace APIs, you need to configure an OAuth consent screen that defines the access your app requests and displays this information to users.\u003c/p\u003e\n"],["\u003cp\u003eYou should carefully select authorization scopes to provide your app with the minimum necessary access to Google Workspace data, as users are more likely to grant consent to apps with limited and clearly defined scopes.\u003c/p\u003e\n"],["\u003cp\u003eAll apps require an OAuth consent screen, but explicitly listing scopes is necessary only for apps used outside your organization, and certain scope categories necessitate additional reviews by Google.\u003c/p\u003e\n"],["\u003cp\u003eTo configure your OAuth consent screen, you'll need to provide app details, select the user type (internal or external), define the necessary scopes, and potentially add test users if applicable.\u003c/p\u003e\n"],["\u003cp\u003eSensitive and restricted scopes require additional verification and security assessments due to their access levels to user data, so consider using non-sensitive alternatives whenever possible.\u003c/p\u003e\n"]]],["OAuth 2.0 requires configuring a consent screen, defining the app's project details, policies, and authorization scopes. Scopes, which specify the level of data access, should be narrowly defined. Configuration involves setting the app name, support email, audience, and contact information in the Google Cloud console. If the app is for external users, you must add and select appropriate scopes, choosing the least sensitive option. Different scope categories—non-sensitive, sensitive, and restricted—have varied review requirements.\n"],null,["When you use OAuth 2.0 for authorization, Google displays a consent screen to\nthe user including a summary of your project, its policies, and the requested\nauthorization scopes of access. Configuring your app's OAuth consent screen\ndefines what is displayed to users and app reviewers, and registers your app\nso you can publish it later.\n| **Note:** Some Google Workspace APIs, such as the Google Drive API, have documentation covering API-specific authentication and authorization information. Ensure you read that documentation before continuing with this page.\n\nTo define the level of access granted to your app, you need to identify and\ndeclare *authorization scopes*. An authorization scope is an OAuth 2.0 URI string\nthat contains the Google Workspace app name, what kind of data it accesses, and\nthe level of access. Scopes are your app's requests to work with Google Workspace data, including\nusers' Google Account data.\n\n\nWhen your app is installed, a user is asked to validate the scopes used\nby the app. Generally, you should choose the most narrowly focused scope\npossible and avoid requesting scopes that your app doesn't require. Users more\nreadily grant access to limited, clearly described scopes.\n\nAll apps using OAuth 2.0 require a consent screen configuration, but you only\nneed to list scopes for apps used by people outside your Google Workspace\norganization.\n\n**Tip:** If you don't know required consent screen information, you can use\nplaceholder information prior to release.\n\nFor security reasons, you can't remove the OAuth 2.0 consent screen\nafter you've configured it.\n\nConfigure OAuth consent\n\n1. In the Google Cloud console, go to Menu menu \\\u003e **Google Auth platform** \\\u003e **Branding** .\n\n [Go to Branding](https://console.cloud.google.com/auth/branding)\n2. If you have already configured the Google Auth platform, you can configure the following OAuth Consent Screen settings in [Branding](https://console.cloud.google.com/auth/branding), [Audience](https://console.cloud.google.com/auth/audience), and [Data Access](https://console.cloud.google.com/auth/scopes). If you see a message that says **Google Auth platform not configured yet** , click **Get Started**:\n 1. Under **App Information** , in **App name** , enter an **App name**.\n 2. In **User support email**, choose a support email address where users can contact you if they have questions about their consent.\n 3. Click **Next**.\n 4. Under **Audience**, select the user type for your app.\n 5. Click **Next**.\n 6. Under **Contact Information** , enter an **Email address** where you can be notified about any changes to your project.\n 7. Click **Next**.\n 8. Under **Finish** , review the [Google API Services User Data Policy](https://developers.google.com/terms/api-services-user-data-policy) and if you agree, select **I agree to the Google API Services: User Data Policy**.\n 9. Click **Continue**.\n 10. Click **Create**.\n 11. If you selected **External** for user type, add test users:\n 1. Click **Audience**.\n 2. Under **Test users** , click **Add users**.\n 3. Enter your email address and any other authorized test users, then click **Save**.\n3. If you're creating an app for use outside of your Google Workspace\n organization, click **Data Access** **\\\u003e** **Add or Remove Scopes**. We recommend the following best practices when\n selecting scopes:\n\n - Select the scopes that provide the minimum level of access required by your app. For a list of available scopes, see [OAuth 2.0 Scopes for Google APIs](/identity/protocols/oauth2/scopes).\n - Review the scopes listed in each of the three sections: non-sensitive scopes, sensitive scopes, and restricted scopes. For any scopes listed in the \"Your sensitive scopes\" or \"Your restricted scopes\" sections, try to identify alternative non-sensitive scopes to avoid unnecessary additional reviews.\n - Some scopes require additional reviews by Google. For apps used only internally by your Google Workspace organization, scopes aren't listed on the consent screen and use of restricted or sensitive scopes doesn't require further review by Google. For more information, see [Scope categories](/workspace/guides/configure-oauth-consent#scope_categories).\n4. After selecting the scopes required by your app, click **Save**.\n\n\nFor more information about configuring OAuth consent, see\n[Get started with the Google Auth platform](https://support.google.com/cloud/answer/15544987).\n\nScope categories\n\nSome scopes require additional reviews and requirements\nbecause of the level or type of access they grant. Consider the following types\nof scopes:\n\n| | | | [Basic app verification](https://support.google.com/cloud/answer/9110914#ver-prep&zippy=%2Csteps-to-prepare-for-verification) required | [Additional app verification](https://support.google.com/cloud/answer/9110914#ver-prep&zippy=%2Csteps-to-submit-your-app) required | [Security assessment](https://support.google.com/cloud/answer/9110914#sec-assess&zippy=%2Csecurity-assessment) required |\n|---|------------------------------------------|-------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|\n| | **Non-sensitive scopes** *(recommended)* | Grant access only to limited data that's immediately relevant to a specific action. | check | --- | --- |\n| | **Sensitive scopes** | Grant access to personal user data, resources, or actions. | check | check | --- |\n| | **Restricted scopes** | Grant access to highly-sensitive or extensive user data or actions. | check | check | check |\n\nNext step\n\n[Create access credentials](/workspace/guides/create-credentials) for your app."]]
