Page Summary

outlined_flag

• Before publishing, determine your add-on's target audience and choose between public or private visibility, bearing in mind this choice is permanent.

• Ensure your add-on meets all publication requirements, has proper collaborator access, and undergoes thorough testing before publishing.

• Create a version of your add-on and record its version number or deployment ID for configuration during the publishing process.

• Set up a standard Google Cloud project and link it to your Apps Script project, as the default project cannot be used for publishing.

• Publish your add-on through the Google Workspace Marketplace once all the preparatory steps are completed.

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 itpublicly. When youpublish your add-on publicly, the Google team reviews your add-on before it’spublished live on Google Workspace Marketplace.

To limit your add-on to users in a specific domain, publish itprivately. Whenyou publish your add-on privately to your domain, the Google team doesn’t reviewyour add-on before it’s published.

If you built your add-on in Apps Script,make sure it aligns with Apps Script's intended use forlightweight add-ons. If youradd-on is designed for a large number of users or needshigh resource demands and scalability, consider adifferent runtimeenvironment.

Review the add-on publication requirements for your add-on type and verify thatyour add-on satisfies all of them. SeeAreas of review.

Your add-on’s Apps Script project is owned by either a single user account(usually your own account) or ashared drive.To publish the add-on, a script collaborator must act as the publisher,which includescreating a standard Google Cloud project.

To publish the add-on, you must have edit access to the script project. Ifyou're not the script project owner, your Workspace account must belong to thesame domain as the project owner.

To verify collaborator access, see the overview forBuilding Google Workspace add-ons.

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 Developeradd-ons). You can share unpublished add-ons with others by sharing the AppsScript project.

• For Google Workspace add-ons, seeTest Google Workspace add-ons.
• For Editor add-ons, seeTest Editor add-ons.

Create a version of your add-on

Create a version of your add-on and record the version number. Aversion is a snapshot of code that yourpublished add-on uses.

• If you publish an Editor add-on, you need to use the version number whenyou configure the Google Workspace Marketplace SDK.
• If you publish a Google Workspace add-on, you need to use the deployment ID ofthe version you want to publish.

If your add-on uses an Apps Script library, you must also create and use aversion of the library's script project. For more information, seeLibraries.

Create a standard Google Cloud project

When you build your add-on in Apps Script, a default Google Cloud project isautomatically created for it. However, you can’t use the default Google Cloud project to publish your app. Instead, use the steps below to create a standardGoogle Cloud project:

1. Open theGoogle API Console projects list.
2. ClickCreate Project.
3. Fill out the project information for your add-on.
4. ClickCreate.

After you create your standard Google Cloud project,switch your Apps Scriptproject from your default Google Cloud project to the standard Google Cloud project.

Publish your add-on

When you’re ready to publish your add-on, follow the steps to publish an app inthe Google Workspace Marketplace. SeeHow to publish.