[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["没有我需要的信息","missingTheInformationINeed","thumb-down"],["太复杂/步骤太多","tooComplicatedTooManySteps","thumb-down"],["内容需要更新","outOfDate","thumb-down"],["翻译问题","translationIssue","thumb-down"],["示例/代码问题","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-04-23。"],[[["\u003cp\u003eBefore publishing, determine your add-on's target audience and choose between public or private visibility, bearing in mind this choice is permanent.\u003c/p\u003e\n"],["\u003cp\u003eEnsure your add-on meets all publication requirements, has proper collaborator access, and undergoes thorough testing before publishing.\u003c/p\u003e\n"],["\u003cp\u003eCreate a version of your add-on and record its version number or deployment ID for configuration during the publishing process.\u003c/p\u003e\n"],["\u003cp\u003eSet up a standard Google Cloud project and link it to your Apps Script project, as the default project cannot be used for publishing.\u003c/p\u003e\n"],["\u003cp\u003ePublish your add-on through the Google Workspace Marketplace once all the preparatory steps are completed.\u003c/p\u003e\n"]]],["Publishing an add-on involves making it available for users. Key actions include: determining if the add-on should be public (for all users) or private (domain-specific), ensuring it meets publication requirements, and verifying collaborators have edit access. Testing the add-on thoroughly, creating a version (snapshot of code), and generating a standard Google Cloud project are also essential. Finally, following the specific publishing steps will make the add-on available on the Google Workspace Marketplace.\n"],null,["When you publish your add-on, you make it available for others to find, install,\nand use.\n\nBefore you publish\n\nDetermine your audience\n\nTo let any user find and install your add-on, publish it *publicly*. When you\npublish your add-on publicly, the Google team reviews your add-on before it's\npublished live on Google Workspace Marketplace.\n\nTo limit your add-on to users in a specific domain, publish it *privately*. When\nyou publish your add-on privately to your domain, the Google team doesn't review\nyour add-on before it's published.\n\nIf you built your add-on in Apps Script,\nmake sure it aligns with Apps Script's intended use for\nlightweight add-ons. If your\nadd-on is designed for a large number of users or needs\nhigh resource demands and scalability, consider a\n[different runtime](/workspace/add-ons/guides/alternate-runtimes)\nenvironment.\n| **Warning:** Once you save your visibility option during the publication process, you can't change your selection later. Make sure you know what visibility your add-on needs before you start the publication process.\n\nReview the add-on publication requirements\n\nReview the add-on publication requirements for your add-on type and verify that\nyour add-on satisfies all of them. See [Areas of review](/workspace/marketplace/about-app-review).\n| **Note:** Even if you plan to publish privately to your domain, make sure your add-on meets the publishing requirements. It's important to provide an optimal experience for your users.\n\nVerify collaborator access\n\nYour add-on's Apps Script project is owned by either a single user account\n(usually your own account) or a [shared drive](/apps-script/guides/collaborating#collaborating_with_shared_drives).\nTo publish the add-on, a script collaborator must act as the publisher,\nwhich includes [creating a standard Google Cloud project](#create-standard-project).\n\nTo publish the add-on, you must have edit access to the script project. If\nyou're not the script project owner, your Workspace account must belong to the\nsame domain as the project owner.\n\nTo verify collaborator access, see the overview for [Building Google Workspace add-ons](/workspace/add-ons/how-tos/building-workspace-addons#set-up-projects).\n\nTest your add-on\n\nMake sure your add-on is fully functional and not a work in progress.\n\nFor testing purposes, you can install unpublished add-ons (also called Developer\nadd-ons). You can share unpublished add-ons with others by sharing the Apps\nScript project.\n\n- For Google Workspace add-ons, see [Test Google Workspace add-ons](/workspace/add-ons/how-tos/testing-workspace-addons).\n- For Editor add-ons, see [Test Editor add-ons](/workspace/add-ons/how-tos/testing-editor-addons).\n\nCreate a version of your add-on\n\n[Create a version of your add-on](/apps-script/guides/versions#creating_a_version)\nand record the version number. A *version* is a snapshot of code that your\npublished add-on uses.\n\n- **If you publish an Editor add-on**, you need to use the version number when you configure the Google Workspace Marketplace SDK.\n- **If you publish a Google Workspace add-on**, you need to use the deployment ID of the version you want to publish.\n\nIf your add-on uses an Apps Script library, you must also create and use a\nversion of the library's script project. For more information, see [Libraries](/apps-script/guides/libraries).\n\nCreate a standard Google Cloud project\n\nWhen you build your add-on in Apps Script, a default Google Cloud project is\nautomatically 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 standard\nGoogle Cloud project:\n\n1. Open the [Google API Console projects list](https://console.developers.google.com/project).\n2. Click **Create Project**.\n3. Fill out the project information for your add-on.\n4. Click **Create**.\n\nAfter you create your standard Google Cloud project, [switch your Apps Script\nproject from your default Google Cloud project to the standard Google Cloud project](/apps-script/guides/cloud-platform-projects#switching_to_a_different_standard_gcp_project).\n\nPublish your add-on\n\nWhen you're ready to publish your add-on, follow the steps to publish an app in\nthe Google Workspace Marketplace. See [How to publish](/workspace/marketplace/how-to-publish)."]]
