When you publish your add-on, you are making it available for others to find, install, and use. Publishing an add-on is a complex and time-consuming process, so be sure to follow the provided instructions carefully to avoid unnecessary delays.
Before attempting to publish an add-on, familarize yourself with the the publishing terms below.
When you are ready, see Publish editor add-ons for full publication instructions.
The following terms are used frequently when discussing add-on publication.
A text, image, video, or URL component of an add-ons listing. During the publication process you must create or provide a number of assets. Some assets are required and others are optional.
See Assets needed for Marketplace listings for descriptions of assets you can provide.
The process wherein add-ons submitted for public publication are examined by Google to ensure they meet all requirements and guidelines for public add-ons.
See Add-on review for more details.
Chrome Web Store migration
Originally, add-ons were published to the Chrome Web Store, and could optionally be published in the G Suite Marketplace to make them domain-wide installable. As of December 2019, all add-ons are published to the G Suite Marketplace. For more details, see Chrome Web Store migration.
Another name for an unpublished add-on.
Domain administrators can find and install any add-on published in the G Suite Marketplace for all or some users in their domain. If a domain user instead installs the add-on for themselves directly, it is known as an individual install.
While configuring your add-on for publication to the G Suite Marketplace, you can elect to allow or prevent individual installs; individual installs are enabled by default. Note that a user's domain policies may prevent them from installing an add-on even if individual installs are enabled.
The entry describing your add-on in the G Suite Marketplace once it's published. Listings consist of a combination of text, images, video, and URL assets that you must create or provide during the publication process. The add-on listing functions as an advertisement for your add-on, and so should be designed and built carefully.
An add-on publication state. Published add-ons have successfully completed the publication process and appear in the G Suite Marketplace.
An add-on publication state. Unpublished add-ons (also called developer add-ons) have not completed the publication process and are not listed in the G Suite Marketplace. This doesn't mean the add-on is incomplete—it's possible to create and use an add-on without publishing it. You can even share unpublished add-ons for others to install and use.Note: An Apps Script project that is bound to a Google Doc, Sheet, Slide, or Form is essentially an unpublished editor add-on that functions just for that file.
Whether a published add-on is available to everyone (public) or only users in the same domain as the publishing account (private). Only published add-ons have a meaningful visibility status.
Private add-ons are only visible to users in the same domain as the add-on publishing account. They can't be installed by outside users. Private add-ons do not require add-on review. Private visibility is sometimes referred to as My Domain visibility.
Public add-ons are visible globally in the G Suite Marketplace. Anyone can see and install them if their domain policies allow it. Public add-ons must go through the add-on review process before they are published. This review process can take several days to complete, and may require you to make changes to your add-on code.