Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Panduan ini menjelaskan proses peninjauan untuk add-on Classroom.
Baca dengan cermat, karena ada tindakan mendesak yang harus Anda lakukan.
Add-on Anda harus diverifikasi OAuth oleh tim Trust & Safety dan disetujui oleh tim Google Workspace Marketplace. Untuk informasi umum tentang verifikasi OAuth, lihat FAQ verifikasi OAuth. Untuk
informasi umum tentang proses peninjauan aplikasi Google Workspace Marketplace, lihat Tentang peninjauan aplikasi.
Menyelesaikan pengembangan add-on
Meninjau persyaratan add-on
Konfirmasi bahwa perilaku add-on Anda memenuhi
persyaratan.
Menguji add-on Anda
Add-on Anda ditinjau sesuai dengan
prosedur dalam
rencana pengujian add-on kami. Ikuti prosedur pengujiannya dengan add-on publik Anda sebelum mengirimkannya untuk dipublikasikan. Kegagalan dalam pengujian ini dapat meningkatkan waktu yang diperlukan untuk menyetujui add-on Anda secara signifikan.
Merekam video demo
Buat rekaman layar yang menunjukkan cara aplikasi Anda menggunakan setiap cakupan OAuth yang diminta. Untuk tujuan pengembangan add-on, sebaiknya tunjukkan alur penginstalan add-on dan pembuatan lampiran add-on.
Setelah direkam, upload rekaman layar ke YouTube sebagai video
tidak publik ke YouTube. Video tidak publik hanya dapat diakses
menggunakan link-nya. Anda akan diminta untuk memberikan link video saat memulai
proses verifikasi OAuth. Tim OAuth kemudian menonton video tersebut saat
meninjau aplikasi add-on Anda.
Mempersiapkan publikasi
Periksa konfigurasi project Cloud Anda
Tinjau setiap setelan konfigurasi berikut di
project Google Cloud Anda.
Setidaknya salah satu cakupan .../auth/userinfo.email atau
.../auth/userinfo.profiletidak sensitif
ditentukan.
Semua cakupan lainnya yang diperlukan oleh add-on Anda ditentukan. Untuk
add-on Classroom, hal ini harus mencakup cakupan
sensitive.../auth/classroom.addons.teacher dan
.../auth/classroom.addons.student.
Untuk kolom Video demo, Anda harus memberikan link
ke video YouTube yang menunjukkan cara Anda menggunakan data dari
cakupan yang diminta. Berikan link ke rekaman screencast yang direkam sebelumnya.
Add-on Classroom dicentang di bagian
Integrasi Aplikasi
URI halaman landing untuk add-on Anda disediakan di
Attachment Setup URI.
Semua Awalan URI Lampiran yang Diizinkan disediakan.
Daftar Cakupan OAuth sama persis dengan cakupan yang ditentukan di layar izin OAuth dan dalam kode aplikasi Anda.
Email Developer di bagian Link Developer adalah alamat email yang
dipantau secara rutin. Tim
Marketplace menggunakan alamat ini untuk berkomunikasi
dengan Anda.
Visibilitas Aplikasi disetel ke Publik dan kotak
Tidak publik dicentang.
Izinkan akun pengguna tim peninjau Marketplace berikut mengakses aplikasi Anda. Tambahkan juga dua pengguna pengajar sebagai
Penguji Draf untuk aplikasi add-on Anda.
teacher@marketplacetest.info
teacher2@marketplacetest.info
student@marketplacetest.info
student2@marketplacetest.info
Anda akan menerima email dari tim Marketplace saat mereka memulai peninjauan. Jika peninjau harus melakukan langkah-langkah penyiapan untuk menggunakan akun ini dengan produk Anda, balas email ini dengan petunjuk mendetail.
Menyelesaikan verifikasi OAuth
Kirim untuk verifikasi
Tim Kepercayaan & Keamanan harus memeriksa apakah add-on Anda menggunakan cakupan OAuth yang diminta aplikasi Anda dengan tepat. Mulai
verifikasi dari
Pusat Verifikasi
Autentikasi project Google Cloud Anda. Klik Siapkan untuk verifikasi.
Dialog konfirmasi mencantumkan nilai yang dikonfigurasi dari halaman Branding Auth,
Audiens, dan Akses Data. Pastikan informasi sudah benar,
lalu klik Konfirmasi untuk melanjutkan.
Berkomunikasi dengan tim verifikasi
Tim verifikasi OAuth akan memproses permintaan verifikasi Anda. Peninjau akan berkomunikasi dengan Anda menggunakan alamat email yang dikonfigurasi di layar Izin OAuth Anda. Mereka akan memberi tahu Anda jika ada masalah dan saat
verifikasi selesai.
Proses ini biasanya memerlukan 3-5 hari kerja jika Anda hanya menggunakan
Cakupan OAuth sensitif. Waktu dan tindakan tambahan mungkin diperlukan jika
Anda menggunakan
Cakupan OAuth terbatas.
Menyelesaikan ulasan Google Workspace Marketplace
Kirim untuk ditinjau
Klik PUBLIKASIKAN di bagian bawah halaman
Listingan Toko Google Workspace Marketplace project Google Cloud Anda. Tim peninjauan Marketplace menguji add-on berdasarkan persyaratan add-on Google Workspace dan Classroom.
Berkomunikasi dengan tim peninjau
Tim peninjauan Marketplace berkomunikasi langsung
dengan alamat Email Developer yang ditentukan di
Google Workspace Marketplace SDK
Konfigurasi Aplikasi. Anda akan diberi tahu jika ada masalah dengan add-on Anda, atau untuk memberi tahu Anda bahwa add-on tersebut telah disetujui untuk dipublikasikan. Sebaiknya alokasikan anggaran selama 2-3 minggu untuk proses ini.
Setelah persetujuan publikasi
Setelah disetujui di Marketplace, listingan add-on Anda tersedia di semua domain Google Workspace for Education di wilayah yang Anda pilih. Batalkan pilihan Tidak Tercantum di
Konfigurasi Aplikasi Marketplace SDK agar listingan
add-on Anda muncul di hasil penelusuran dan saat
penjelajahan.
[null,null,["Terakhir diperbarui pada 2025-08-29 UTC."],[],[],null,["# Review process\n\nThis guide describes the review process for Classroom add-ons.\nRead through carefully, as there are time-sensitive actions that you must\nperform.\n| **Key Point:** Thoroughly review the items in this guide *before publishing your\n| add-on*.\n\nYour add-on must be OAuth verified by the Trust \\&\nSafety team and approved by the Google Workspace Marketplace team. For general\ninformation about OAuth verification, see the [OAuth verification FAQ](//support.google.com/cloud/answer/9110914#zippy=%2Csteps-for-apps-requesting-sensitive-scopes%2Csteps-to-prepare-for-verification). For\ngeneral information about the Google Workspace Marketplace app review process\nsee [About app review](/workspace/marketplace/about-app-review).\n\nFinalize add-on development\n---------------------------\n\n\u003cbr /\u003e\n\n#### Review add-on requirements\n\nConfirm that your add-on behavior meets the\n[requirements](/workspace/classroom/add-ons/requirements).\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n#### Test your add-on\n\nYour add-on is reviewed according to the\nprocedures in our\n[add-ons test plan](/static/workspace/classroom/assets/classroom_add_ons_test_plan.pdf). Follow its testing\nprocedures with your public add-on before\nsubmitting for publication. Failures in these tests can significantly\nincrease the time required for your add-on to be\napproved.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n| **Key Point:** The add-ons test plan contains the same tests used by the Google Workspace Marketplace review team. You should proactively test that your add-on produces expected behaviors in all applicable tests.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n#### Record a demo video\n\nCreate a screen recording demonstrating how your application uses each\nrequested OAuth scope. For the purposes of developing an\nadd-on, we recommend showing the\nadd-on installation flow and creation of an\nadd-on attachment.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nOnce recorded, upload the screen recording to YouTube as an\n*unlisted* video to YouTube. An unlisted video can only be reached\nusing its link. You'll be prompted for the video link when starting the\nOAuth verification process. The OAuth team then views the video when\nreviewing your add-on application.\n\n\u003cbr /\u003e\n\nPrepare for publication\n-----------------------\n\n\u003cbr /\u003e\n\n#### Check your Cloud project configuration\n\nReview each of the following configuration settings in your\n**Google Cloud project**.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n| **Caution:** When checking these configuration settings, make sure the correct Cloud project is selected at the top of the Google Cloud console.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n- In your Cloud project's [Auth Audience](//console.cloud.google.com/auth/audience) page:\n - Publishing status is **In production**.\n - User type is **External**.\n- In your Cloud project's [Auth Branding](//console.cloud.google.com/auth/branding) page:\n - All required fields are complete.\n - Ensure that your application home page doesn't link to the app itself, but rather to information about your product(s).\n- In your Cloud project's [Auth Data Access](//console.cloud.google.com/auth/scopes) page:\n - At least one of the `.../auth/userinfo.email` or `.../auth/userinfo.profile` **non-sensitive** scopes are specified.\n - *All other scopes* required by your add-on are specified. For Classroom add-ons, this should include the **sensitive** `.../auth/classroom.addons.teacher` and `.../auth/classroom.addons.student` scopes.\n - For the **Demo video** field, you must provide a link to a YouTube video that demonstrates how you use the data from the requested scopes. Provide the link to the screencast recorded earlier.\n- The following [API libraries](//console.cloud.google.com/apis/library) are **Enabled** :\n - [Google Classroom API](//console.cloud.google.com/apis/library/classroom.googleapis.com)\n - [Google Workspace Marketplace SDK](//console.cloud.google.com/apis/library/appsmarket-component.googleapis.com)\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n#### Check your Marketplace SDK\nsettings\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n| **Caution:** When checking these configuration settings, make sure the correct Cloud project is selected at the top of the Google Cloud console page.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nIn your\n[Google Workspace Marketplace SDK App Configuration](//console.cloud.google.com/apis/api/appsmarket-component.googleapis.com/googleapps_sdk) page:\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n- **Classroom add-on** is checked under App Integration\n- The landing URI for your add-on is provided in the **Attachment Setup URI**.\n- All **Allowed Attachment URI Prefixes** are provided.\n- The list of **OAuth Scopes** exactly matches the scopes specified in the OAuth consent screen and in your application code.\n- The **Developer Email** under Developer Links is a *regularly monitored* email address. The Marketplace team uses this address to communicate with you.\n- App Visibility is set to **Public** and the **Unlisted** box is checked.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nCheck that your project's\n[Google Workspace Marketplace Store Listing](//console.cloud.google.com/apis/api/appsmarket-component.googleapis.com/googleapps_sdk_publish) page complies with the\n[Listing considerations](/workspace/classroom/add-ons/developer-guides/project-configuration#workspace_marketplace_name-listing).\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n#### Allow reviewer access\n\nAllow the following Marketplace review team user\naccounts access to your application. Also add the two teacher users as\n[Draft Testers](/workspace/marketplace/manage-app-listing#draft-app-listing) for your add-on application.\n\n- `teacher@marketplacetest.info`\n- `teacher2@marketplacetest.info`\n- `student@marketplacetest.info`\n- `student2@marketplacetest.info`\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nYou'll receive an email from the Marketplace\nteam when they begin their review. If the reviewers must perform any setup\nsteps to use these accounts with your product, reply to the email with\ndetailed instructions.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n| **Important:** Reviewers may connect to your application from Argentina, Canada, and the United States. Ensure these regions are not blocked in your implementation and allowed under **Distribution** in the Marketplace SDK [Store Listing](//console.cloud.google.com/apis/api/appsmarket-component.googleapis.com/googleapps_sdk_publish) page. You can change the Distribution configuration after your add-on is approved.\n\n\u003cbr /\u003e\n\nComplete OAuth verification\n---------------------------\n\n\u003cbr /\u003e\n\n#### Submit for verification\n\nThe Trust \\& Safety team must check that your add-on\nappropriately uses the OAuth scopes that your application requests. Initiate\nverification from your Google Cloud project's\n[Auth Verification\nCenter](//console.cloud.google.com/auth/verification). Click **Prepare for verification**.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nA confirmation dialog lists the configured values from the Auth Branding,\nAudience, and Data Access pages. Verify that the information is correct,\nthen click **Confirm** to proceed.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n#### Communicate with the verification team\n\nThe OAuth verification team processes your verification request. The\nreviewers communicate with you using the email addresses configured in your\nOAuth Consent screen. They will inform you of any concerns and when\nverification is complete.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nThis process typically requires 3-5 working days if you are only using\n[Sensitive OAuth scopes](/identity/protocols/oauth2/production-readiness/sensitive-scope-verification). Additional time and actions may be required if\nyou are using any\n[Restricted OAuth scopes](/identity/protocols/oauth2/production-readiness/restricted-scope-verification).\n\n\u003cbr /\u003e\n\nComplete Google Workspace Marketplace review\n--------------------------------------------\n\n\u003cbr /\u003e\n\n#### Submit for review\n\n| **Tip:** You can apply for Marketplace review and OAuth verification simultaneously. However, your application must complete OAuth verification before it can receive final Marketplace approval.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nClick **PUBLISH** at the bottom of your Google Cloud project's\n[Google Workspace Marketplace Store Listing](//console.cloud.google.com/apis/api/appsmarket-component.googleapis.com/googleapps_sdk_publish) page. The\nMarketplace review team tests the\nadd-on against Google Workspace and\nClassroom add-on requirements.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n#### Communicate with the review team\n\nThe Marketplace review team communicates directly\nwith the Developer Email address specified in the\nGoogle Workspace Marketplace SDK\n[App Configuration](//console.cloud.google.com/apis/api/appsmarket-component.googleapis.com/googleapps_sdk) page. You are notified about any concerns with your\nadd-on, or to inform you that it has been approved\nfor publication. We recommend budgeting 2-3 weeks for this process.\n\n\u003cbr /\u003e\n\nAfter publication approval\n--------------------------\n\nAfter Marketplace approval, your\nadd-on listing is available in all Google Workspace for Education\ndomains in the regions you selected. Unselect the **Unlisted** option in the\nMarketplace SDK [App Configuration](//console.cloud.google.com/apis/api/appsmarket-component.googleapis.com/googleapps_sdk) to make your\nadd-on listing appear in search results and when\nbrowsing."]]
