When you publish your add-on, you make it available for others to find, install, and use.
Before you publish
Determine your audience
To let any user find and install your add-on, publish it publicly. When you publish your add-on publicly, the Google team reviews your add-on before it’s published live on G Suite Marketplace.
To limit your add-on to users in a specific domain, publish it privately. When you publish your add-on privately to your domain, the Google team doesn’t review your add-on before it’s published.
Review the add-on publication requirements
Review the add-on publication requirements for your add-on type and verify that your add-on satisfies all of them. See Areas of review.
Test your add-on
Make sure your add-on is fully functional and not a work in progress.
For testing purposes, you can install unpublished add-ons (also called Developer add-ons). You can share unpublished add-ons with others by sharing the Apps Script project.
Create a version of your add-on
Create a version of your add-on and record the version number. A version is a snapshot of code that your published add-on uses.
- If you publish an Editor Add-on, you need to use the version number when you configure the G Suite Marketplace SDK.
- If you publish a G Suite Add-on, you need to use the deployment ID of the version you want to publish.
Create a standard Google Cloud Platform project
When you build your add-on in Apps Script, a default Google Cloud Platform (GCP) project is automatically created for it. However, you can’t use the default GCP project to publish your app. Instead, use the steps below to create a standard GCP project:
- Open the Google API Console projects list.
- Click Create Project.
- Fill out the project information for your add-on.
- Click Create.
After you create your standard GCP project, switch your Apps Script project from your default GCP project to the standard GCP project.
Verify collaborator access
Your add-on’s Apps Script project is owned by either a single user account (usually your own account) or a shared drive. When you publish your add-on, a single user account acts as the publisher.
The person who publishes the add-on must have edit access to the add-on script project, but they don’t need to be the script project owner. However, the script project owner must belong to the same domain as the account that is used to publish the add-on.
Before you start the publishing process, be sure to determine and review your project collaborator access settings.
Publish your add-on
When you’re ready to publish your add-on, follow the steps to publish an app in the G Suite Marketplace. See How to publish.