![]() Configure the add-on's project manifest or deployment resource. Design your add-on's appearance and behavior. Java is a registered trademark of Oracle and/or its affiliates. When you want to build a new Google Workspace Add-on, follow this general procedure: Set up your add-on's projects and choose an owner and collaborators. For details, see the Google Developers Site Policies. See How to publish.Įxcept as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. When you’re ready to publish your add-on, follow the steps to publish an app in Project from your default Google Cloud project to the standard Google Cloud project. Fill out the project information for your add-on.Īfter you create your standard Google Cloud project, switch your Apps Script.Open the Google API Console projects list.Instead, use the steps below to create a standard However, you can’t use the default Google Cloud project to publish your app. When you build your add-on in Apps Script, a default Google Cloud project isĪutomatically created for it. If your add-on uses an Apps Script library, you must also create and use a If you publish a Google Workspace add-on, you need to use the deployment ID of.You configure the Google Workspace Marketplace SDK. If you publish an Editor Add-on, you need to use the version number when.A version is a snapshot of code that your ![]() For Editor Add-ons, see Test Editor Add-ons.Īnd record the version number.For Google Workspace add-ons, see Test Google Workspace add-ons.You can share unpublished add-ons with others by sharing the Apps Make sure your add-on is fully functional and not a work in progress.įor testing purposes, you can install unpublished add-ons (also called DeveloperĪdd-ons). To verify collaborator access, see the overview for Building Google Workspace Add-ons. You're not the script project owner, your Workspace account must belong to the To publish the add-on, you must have edit access to the script project. Which includes creating a standard Google Cloud project. To publish the add-on, a script collaborator must act as the publisher, (usually your own account) or a shared drive. Your add-on’s Apps Script project is owned by either a single user account It’s important to provide an optimalĮxperience for your users. ![]() Note: Even if you plan to publish privately to your domain, make sure yourĪdd-on meets the publishing requirements. Review the add-on publication requirements for your add-on type and verify that Review the add-on publication requirements Make sure you know what visibility yourĪdd-on needs before you start the publication process. Warning: Once you save your visibility option during the publication process, You publish your add-on privately to your domain, the Google team doesn’t review To limit your add-on to users in a specific domain, publish it privately. Published live on Google Workspace Marketplace. Publish your add-on publicly, the Google team reviews your add-on before it’s To let any user find and install your add-on, publish it publicly. Before you publish Determine your audience If you publish an Editor Add-on, you need to use the version number when you configure the Google Workspace Marketplace SDK. A version is a snapshot of code that your published add-on uses. Create a version of your add-on and record the version number. Test free version of our plugins and check its features or purchase selected widget with a 20% off.When you publish your add-on, you make it available for others to find, install,Īnd use. For Editor Add-ons, see Test Editor Add-ons.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |