Review process

Confirm that your add-on behavior meets the requirements.

Your add-on is reviewed according to the procedures in our add-ons test plan. Follow its testing procedures with your public add-on before submitting for publication. Failures in these tests can significantly increase the time required for your add-on to be approved.

Create a screen recording demonstrating how your application uses each requested OAuth scope. For the purposes of developing an add-on, we recommend showing the add-on installation flow and creation of an add-on attachment.

Once recorded, upload the screen recording to YouTube as an unlisted video to YouTube. An unlisted video can only be reached using its link. You'll be prompted for the video link when starting the OAuth verification process. The OAuth team then views the video when reviewing your add-on application.

Review each of the following configuration settings in your Google Cloud project.

• In your Cloud project's Auth Audience page:
  • Publishing status is In production.
  • User type is External.
• In your Cloud project's Auth Branding page:
  • All required fields are complete.
  • Ensure that your application home page doesn't link to the app itself, but rather to information about your product(s).
• In your Cloud project's Auth Data Access page:
  • At least one of the .../auth/userinfo.email or .../auth/userinfo.profile non-sensitive scopes are specified.
  • 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.
  • 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.
• The following API libraries are Enabled:
  • Google Classroom API
  • Google Workspace Marketplace SDK

In your Google Workspace Marketplace SDK App Configuration page:

• Classroom add-on is checked under App Integration
• The landing URI for your add-on is provided in the Attachment Setup URI.
• All Allowed Attachment URI Prefixes are provided.
• The list of OAuth Scopes exactly matches the scopes specified in the OAuth consent screen and in your application code.
• The Developer Email under Developer Links is a regularly monitored email address. The Marketplace team uses this address to communicate with you.
• App Visibility is set to Public and the Unlisted box is checked.

Check that your project's Google Workspace Marketplace Store Listing page complies with the Listing considerations.

Allow the following Marketplace review team user accounts access to your application. Also add the two teacher users as Draft Testers for your add-on application.

• teacher@marketplacetest.info
• teacher2@marketplacetest.info
• student@marketplacetest.info
• student2@marketplacetest.info

You'll receive an email from the Marketplace team when they begin their review. If the reviewers must perform any setup steps to use these accounts with your product, reply to the email with detailed instructions.

The Trust & Safety team must check that your add-on appropriately uses the OAuth scopes that your application requests. Initiate verification from your Google Cloud project's Auth Verification Center. Click Prepare for verification.

A confirmation dialog lists the configured values from the Auth Branding, Audience, and Data Access pages. Verify that the information is correct, then click Confirm to proceed.

The OAuth verification team processes your verification request. The reviewers communicate with you using the email addresses configured in your OAuth Consent screen. They will inform you of any concerns and when verification is complete.

This process typically requires 3-5 working days if you are only using Sensitive OAuth scopes. Additional time and actions may be required if you are using any Restricted OAuth scopes.

Click PUBLISH at the bottom of your Google Cloud project's Google Workspace Marketplace Store Listing page. The Marketplace review team tests the add-on against Google Workspace and Classroom add-on requirements.

The Marketplace review team communicates directly with the Developer Email address specified in the Google Workspace Marketplace SDK App Configuration page. You are notified about any concerns with your add-on, or to inform you that it has been approved for publication. We recommend budgeting 2-3 weeks for this process.