Enable and configure the Google Workspace Marketplace SDK

If you haven't already done so, in your Google Cloud project, enable the Google Workspace Marketplace SDK.

1. Open the Google Cloud console.
2. At the top, click Select a project. If a different Google Cloud project is already open, click the Cloud project name to switch Cloud projects.
3. Select your app’s Cloud project and click Open.
4. At the top, in the search bar, type Google Workspace Marketplace SDK and press enter.
5. On the Google Workspace Marketplace SDK page, click Enable.

Warning: Make sure you enable the Google Workspace Marketplace SDK, not the API. The Google Workspace Marketplace API is a different tool used to integrate with Google's licensing and billing services.

Fill out the Google Workspace Marketplace SDK App Configuration page

1. In the Google Workspace Marketplace SDK, at the left, click App Configuration.
2. Fill out each section with the information about your app. Learn more about each section below.
3. At the bottom, click Save.

App configuration settings

App extension

App extension is the app integration you want to publish, such as a Google Workspace Add-on or a Google Chat app. You must choose at least one option. In some cases, you can include multiple app integrations in your app listing. See List app integrations together.

Depending on which app integrations you choose, you might need to provide more information and enable relevant APIs in your Google Cloud project. The following describes the additional setup needed for each:

Google Workspace Add-on

To publish a Google Workspace Add-on, you must provide the add-on’s deployment ID. To find the deployment ID, follow these steps:

1. Open your Google Workspace Add-on in the Apps Script editor.
2. Click Deploy > Manage deployments.
3. Under the deployment ID, click Copy.

If you built your Google Workspace Add-on in a coding language other than Google Apps Script, follow the steps below to get the deployment ID from the Google Cloud deployment resource.

1. On the App Configuration page under "Google Workspace Add-on," click Deploy using cloud deployment resource > Select Deployment.
2. Select the deployment you want to publish.
3. Click Select.

Google Chat app

To publish a Google Chat app, you must configure the Google Chat API. See Publishing apps.

Web app

To publish a web app, you must provide its universal nav URL, the URL that points to the web app from the Google apps menu . Your web app must be in production and fully functional.

When you fill out the Store Listing page, you must provide additional icons sized to 96x96 and 48x48 pixels.

If you built your web app in Apps Script, to get the universal nav URL, follow these steps:

1. Open your Google Workspace Add-on in the Apps Script editor.
2. Click Deploy > New deployment.
3. Under "Select type," click Web app.
4. Fill out the options and click Deploy.
5. Click Copy.

Drive app

To publish a Drive app, you must enable and configure the Drive API.

Editor Add-on (Docs, Sheets, Slides, Forms)

To publish an Editor Add-on, you must provide the project script ID and version you want to publish.

To find the project script ID, follow these steps:

1. Open the add-on in the Apps Script editor.
2. At the left, click Project settings .
3. Under "IDs," copy the script ID.

To find the version, follow these steps:

1. Open the add-on in the Apps Script editor.
2. At the top right, click Deploy > Manage deployments.
3. The version number is under "Configuration."

OAuth scopes

Provide a complete list of the OAuth scopes your app requires. The OAuth scopes you enter here should match what you display in your OAuth consent screen and if applicable, Apps Script manifest.

If you include more than one app integration, make sure you add the scopes from each one to the Google Workspace Marketplace SDK App Configuration page and your OAuth consent screen.

Always use the narrowest scopes possible (for example, don't include a full Drive scope if you only need a read-only scope).

For Apps Script projects, see Scopes for more details.

Developer information

These fields appear on your app's store listing page.

Fields
Trader status	Due to consumer protection laws, consumers based in the European Economic Area (EEA) must be informed whether a merchant on the Google Workspace Marketplace is a trader or a non-trader: Trader—A trader is a person who acts for purposes relating to a trade, business, craft, or profession; or in the name of or on behalf of a trader. Non-trader—A non-trader (consumer) is a person who acts for non-professional purposes. If unspecified, "Trader status unspecified" appears on your app's store listing page.
Developer mailing address	Required for traders. Not collected for non-traders. The location of your business. Enter a valid mailing address where you can be contacted.
Developer name	The name to display as the author of the app. If you are a trader, provide your trading name or legal name.
Developer website URL	The website that describes you (or your organization) as the developer.
Developer email	The email address that's used as a point of contact. It’s not included in your app listing. Make sure this email address is kept up to date—it’s used: If Google needs to contact the developer—for example, during the app review process. To send feedback from Editor add-ons if a Report Issue URL isn’t provided on the Store Listing page.
Application website URL	Optional. The website that further describes your app.

Listing data

Add a Google Analytics ID to track your app listing in Google Analytics (optional). For more information, see Get analytics on app usage.

Installation settings

The installation settings determine if users or Workspace admins can install your app from your store listing page on the Google Workspace Marketplace.

Note: For Google Chat apps, you can only select Individual + Admin Install. Currently, only administrators can install Chat apps directly from the Google Workspace Marketplace. Individuals can install Chat apps from Google Chat. For details about how installation works, see Publishing Chat apps.

• Individual + Admin Install (default): The app can be installed by individual users or by admins for their domain, organizational unit, or a group of users. A user's domain policies might prevent them from installing an app even if individual installs are enabled.
• Admin Only Install: The app can only be installed by admins for their domain, organizational unit, or a group of users. Your app only shows up in Google Workspace Marketplace search results for admins and people who aren't logged in to their Google Account. Choose this option if your app requires domain installation.

App visibility

Warning: Once you choose a visibility option and save the App Configuration page, you can't change your selection later.

You see the App Visibility option if you’re using a Google Workspace account (an account created by your work or school organization). If you’re using a consumer account (an account ending with “@gmail.com”), you can only publish publicly.

• Public: The app can be found and installed by people outside of your domain. If you choose public visibility, Google reviews and approves your app listing before it's published.
• Private: Only people within your domain can find and install your app.

If you choose to publish as Unlisted, the app listing won't show in browse or search results. Users can only access the app’s store page with the direct URL.