Les modules complémentaires Google Classroom sont désormais disponibles pour tous les développeurs. Pour en savoir plus, consultez la documentation sur les modules complémentaires.
Configurez votre domaine de test pour autoriser les utilisateurs à installer toutes les applications Marketplace afin de pouvoir installer et tester votre application avant sa publication. Si vous souhaitez tester le processus d'installation de l'application avec des paramètres de domaine plus restrictifs, vous pouvez modifier ce paramètre après avoir publié votre application.
Créez un projet Google Cloud. Il vous servira à configurer votre module complémentaire, à envoyer des requêtes d'API, et à authentifier et autoriser les utilisateurs. Vous pouvez également utiliser un projet Cloud existant.
Si vous définissez la visibilité de l'application sur publique, ajoutez les adresses e-mail de tous les utilisateurs tests à la liste des testeurs de version préliminaire. Lorsque vous avez terminé, sélectionnez ENREGISTRER COMME BROUILLON.
Connectez-vous à votre domaine de démonstration en tant qu'utilisateur test. Installez votre module complémentaire à partir de l'URL de l'application dans la configuration de votre fiche Google Workspace Marketplace.
Développement
Développez le module complémentaire et testez-le avec vos utilisateurs test.
Créez une fiche Google Workspace Marketplace pour le projet public.
Ajoutez vos comptes utilisateur de test en tant que testeurs de brouillon du SDK Marketplace. Enregistrez vos modifications sous forme de brouillon.
Mettez à jour le projet public avec le code de votre module complémentaire.
Envoyez une
demande de validation OAuth pour votre projet public. Vous devrez enregistrer une courte vidéo montrant l'utilisation des champs d'application des modules complémentaires à l'aide de l'un des comptes de testeur de version préliminaire.
Examen des travaux des élèves. L'iFrame "Examen des devoirs des élèves" n'est requis que si la pièce jointe est de type activité.
Google Workspace Marketplace
Le Google Workspace Marketplace présente des applications pour les entreprises qui peuvent être ajoutées à un domaine entier ou à des comptes Google Workspace individuels. Marketplace est intégré à la console d'administration Google. Les administrateurs de domaine peuvent ainsi trouver, installer et autoriser rapidement des applications pour des utilisateurs ciblés.
Sauf indication contraire, le contenu de cette page est régi par une licence Creative Commons Attribution 4.0, et les échantillons de code sont régis par une licence Apache 2.0. Pour en savoir plus, consultez les Règles du site Google Developers. Java est une marque déposée d'Oracle et/ou de ses sociétés affiliées.
Dernière mise à jour le 2025/08/29 (UTC).
[null,null,["Dernière mise à jour le 2025/08/29 (UTC)."],[],[],null,["# Developer journey\n\nThe following is a quick overview of steps when developing a\nClassroom add-on.\n| **Important:** Subscribe to the Google for Education [Developer Announcement group](//groups.google.com/g/classroom-dev-announce) to receive updates about add-ons and Google Classroom API.\n\nOnboarding\n----------\n\n1. You will need test users with the Teaching \\& Learning or Plus [editions of\n Google Workspace for Education](//edu.google.com/intl/ALL_us/workspace-for-education/editions/compare-editions/). If you don't have administrator access to a Google Workspace for Education domain with either of these licenses, complete the steps to [get a\n developer test domain](/workspace/classroom/support/access#get_a_developer_test_domain) and then submit our [domain upgrade request form](//docs.google.com/forms/d/e/1FAIpQLSeBARH7nviEOyqFp3OWKVR6m4621UW9ELzUFI_XDu5ENqUUGw/viewform?usp=sf_link). The domain will be provisioned with 10 Google Workspace for Education Plus licenses.\n2. Configure your test domain to [allow users to install all\n Marketplace applications](https://support.google.com/a/answer/172931) so that you can install and test your app before it's published. If you want to test the app installation process with more restrictive domain settings, you can change this setting after publishing your app.\n3. [Create teacher and student accounts](/workspace/classroom/add-ons/developer-guides/project-configuration#test_accounts) for testing. Once the license is approved for your demo domain, [assign seats to each of your test accounts](//support.google.com/a/answer/1727173).\n4. [Create a Google Cloud project](/workspace/classroom/add-ons/developer-guides/project-configuration#project-creation). You'll use it configure\n your add-on, make API requests, and authenticate and authorize users. You\n can use also an existing Cloud project.\n\n | **Warning:** Pay particular attention to the **App Visibility** . This setting controls whether your add-on will be accessible by end users and *cannot be\n | changed later*.\n5. [Configure OAuth](/workspace/classroom/add-ons/developer-guides/project-configuration#oauth) for your project.\n\n6. [Create a Google Workspace Marketplace listing](/workspace/classroom/add-ons/developer-guides/project-configuration#workspace_marketplace_name-listing) for the\n demo project.\n\n - If you set the App Visibility to **public** , add the email addresses of *all* test users to the list of **Draft testers** . Choose **SAVE DRAFT** when finished.\n\n | **Key Point:** A project in **draft** state lets you preview and test changes before publishing them. See [Update your app listing with drafts](/workspace/marketplace/manage-app-listing#update_your_app_listing_with_drafts) for more information about this feature.\n7. Sign in to your demo domain as a test user. Install your add-on from the\n **App URL** in your Google Workspace Marketplace listing configuration.\n\nDevelopment\n-----------\n\n7. Develop the add-on and test it with your test users.\n\nPublishing\n----------\n\n8. In the [Google Cloud project you want to publish](/workspace/classroom/add-ons/developer-guides/project-configuration#create_a_public_gcp_project), ensure the following:\n 1. OAuth consent screen:\n 1. User Type: **External**\n 2. Publish Status: **In Production**\n 3. Scopes: [Configure **all** scopes](/workspace/classroom/add-ons/developer-guides/project-configuration#required_classroom_add-ons_scopes) requested by the web app.\n 2. Google Workspace Marketplace SDK App Configuration Screen:\n 1. App Visibility: **Public**\n 2. Listing Type: **Unlisted**\n 3. Scopes: [Configure **all** scopes](/workspace/classroom/add-ons/developer-guides/project-configuration#required_classroom_add-ons_scopes) requested by the web app.\n9. [Create a Google Workspace Marketplace listing](/workspace/classroom/add-ons/developer-guides/project-configuration#google_workspace_marketplace_listing) for the public project. Add your test user accounts as Marketplace SDK Draft testers. Save your changes **as a Draft**.\n10. Update the public project with your add-on code.\n11. As one of the Draft testers, install the add-on by visiting its [Marketplace listing URL](//console.cloud.google.com/apis/api/appsmarket-component.googleapis.com/googleapps_sdk_publish).\n12. Submit an [OAuth verification request](/workspace/classroom/add-ons/developer-guides/review-process-overview#complete_oauth_verification) for your public project. You will need to record a short video demonstrating the use of the add-ons scopes using one of the Draft tester accounts.\n13. [Publish the public add-on](/workspace/classroom/add-ons/developer-guides/review-process-overview#complete-review) for Marketplace review.\n14. Upon approval, change the Marketplace SDK Listing status to **listed**.\n\nRequired integrations\n---------------------\n\nThe following are required to build a Classroom add-on.\n\n1. Google Single Sign-On\n\n - [Google Identity Platform](/identity/choose-auth). Google offers a variety of authentication options.\n - [Integration case studies](/identity/sign-in/case-studies).\n\n See the [frictionless sign-in page](/workspace/classroom/add-ons/developer-guides/frictionless-signin) for information about how to implement\n sign-in following best practices.\n2. Submission to Google Workspace Marketplace as a\n Classroom add-on\n\n3. iframe implementations\n\n - [Attachment Discovery](/workspace/classroom/add-ons/get-started/iframes/attachment-discovery-iframe)\n - [Teacher View](/workspace/classroom/add-ons/get-started/iframes/teacher-iframe)\n - [Student View](/workspace/classroom/add-ons/get-started/iframes/student-iframe)\n - [Student Work Review](/workspace/classroom/add-ons/get-started/iframes/grader-iframe). The Student Work Review iframe is only required if the attachment provides an activity-type attachment.\n\nGoogle Workspace Marketplace\n----------------------------\n\nThe [Google Workspace Marketplace](/marketplace) showcases enterprise applications\nthat can be added to an entire domain or to individual Google Workspace\naccounts. The Marketplace\nis integrated with the [Google Admin console](//admin.google.com/) so that domain\nadministrators can quickly find, install, and authorize apps for targeted users.\n\nSome key concepts to be familiar with are:\n\n- [OAuth](/workspace/classroom/add-ons/developer-guides/project-configuration#oauth) behavior and requirements.\n- The [Google Workspace Marketplace developer documentation](/workspace).\n- The [education section](//workspace.google.com/marketplace/category/education) of Google Workspace Marketplace."]]
