[[["容易理解","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"]],["上次更新時間：2025-04-23 (世界標準時間)。"],[[["\u003cp\u003eEditor add-ons are built using Apps Script, requiring a standalone Apps Script project and code for the add-on's functionality and user interface.\u003c/p\u003e\n"],["\u003cp\u003eThorough testing is crucial before publishing using a dedicated test configuration and sample documents, ensuring the add-on functions as intended.\u003c/p\u003e\n"],["\u003cp\u003eCollaboration involves shared ownership and access, recommending the use of shared drives and adding collaborators to the Cloud Platform project for sustained accessibility.\u003c/p\u003e\n"],["\u003cp\u003ePublishing makes the add-on accessible to others, either publicly or within a domain, involving a review process for public listings on the Google Workspace Marketplace.\u003c/p\u003e\n"],["\u003cp\u003eThe add-on's appearance and behavior are defined using Apps Script's HTML service, allowing for custom menus, dialogs, and sidebars constructed with HTML and CSS.\u003c/p\u003e\n"]]],["Begin by creating a standalone Apps Script project, which can be done via a new script or through specific instructions. Next, code the add-on's appearance and functionality using Apps Script's HTML service for the user interface. Before releasing, test the add-on with a test configuration and document. To make the add-on available to users, publish it on the Google Workspace Marketplace after ensuring the add-on complies with publication guidelines. Utilizing shared drives for code access is encouraged.\n"],null,["Before building your Editor add-on, review the\n[Apps Script quotas and limitations](/apps-script/guides/services/quotas) to\nensure your project design aligns with these guidelines. Familiarizing yourself\nwith these limits early in your development process can help prevent potential\nissues later on. Apps Script is ideal for lightweight\nadd-on development for yourself, your team, or your\norganization. However, if you anticipate building a large-scale\nadd-on that needs to handle many users, requires low\nlatency, or demands full control over your infrastructure, consider developing\na Google Workspace add-on on a\n[different runtime](/workspace/add-ons/guides/alternate-runtimes) environment.\n\nFollow this general procedure when building an Editor add-on:\n\n1. Create an Apps Script project.\n2. Write code to define the add-on's appearance and behavior, using the built-in Apps Script [HTML service](/apps-script/reference/html).\n3. Test the add-on.\n4. Publish the add-on.\n\nCreate a script project\n\nAn Editor add-on is a [standalone](/apps-script/guides/standalone) Apps Script\nproject. The standalone script guide provides\n[instructions to create new projects](/apps-script/guides/standalone#creating_a_standalone_script).\nYou can also just\n[open a new script](https://script.google.com/create).\nIf you do this, the project file (initially named `Untitled project`) is\nplaced in your root Drive folder.\n| **Note:** If you intend to publish your add-on, you must use a [standard Cloud Platform (GCP) project](/apps-script/guides/cloud-platform-projects#standard_cloud_platform_projects).\n\nCollaboration\n\nWhen you collaborate with others in developing an add-on, a single user account\nowns the add-on project. When you publish an add-on, a single user account acts\nas the publisher. The publishing account must have edit access to the add-on\nscript project, but it doesn't need to be project owner.\n\n**It's very important to avoid situations where you lose access to an add-on's\ncode or settings because the owner of the project left your organization.**\n\nTo prevent losing access to add-on code, we encourage you to use\n[shared drives](/apps-script/collaborating#collaborating_with_shared_drives)\nwhen you collaborate on an add-on. Placing your add-on script file in a shared\ndrive ensures that no single account is the sole owner of the project.\n\nIt is also recommended that you\n[add collaborators to the script project's Cloud Platform (GCP) project](/apps-script/guides/cloud-platform-projects#adding_additional_owners_to_a_standard_gcp_project).\nThis helps ensure someone on your team always can access the add-on's\nCloud settings.\n| **Warning:** If you don't add collaborators to your add-on project, it is vital that you transfer ownership of the script project prior to the owner's account being shutdown or removed. Otherwise you could lose access to the add-on code and settings entirely.\n\nCode the add-on\n\nOnce you have created a script project, you can begin writing\ncode to define the add-on appearance and behavior. You use the Apps Script\n[HtmlService](/apps-script/reference/html) to construct the add-on user\ninterface---[dialogs and sidebars](/workspace/add-ons/concepts/dialogs)---\nusing conventional HTML and CSS. Editor add-ons can define custom\n[menu items](/workspace/add-ons/concepts/menus) as well.\n\nAs you code, refer to the [Editor add-on style guide](/workspace/add-ons/guides/editor-style)\nfor guidelines on how to design your add-on user experience. Also, be sure\nyou understand and program for the different\n[authorization lifecycle states](/workspace/add-ons/concepts/editor-auth-lifecycle)\nyour add-on can encounter.\n\nTest the add-on\n\nYou can test Editor add-ons before they are published to ensure they behave\nas expected. Testing requires you to create a\n[test configuration](/workspace/add-ons/how-tos/testing-editor-addons#create_a_test_configuration)\nand use a testing document, spreadsheet, form, or presentation.\n\nSee [Test an Editor add-on](/workspace/add-ons/how-tos/testing-editor-addons)\nfor details.\n\nPublish the add-on\n\nPublishing your add-on makes it available to others, either publicly or just\nusers in your domain. Before you start the publishing process, be sure to\nreview the [publication overview](/workspace/add-ons/how-tos/editor-publish-overview).\n\nEditor add-ons are published to the [Google Workspace Marketplace](https://workspace.google.com/marketplace/). Publicly available add-ons\nmust complete [add-on review](/workspace/marketplace/about-app-review) before they are published.\n\nSee [Publishing an Editor add-on](/workspace/add-ons/how-tos/publishing-editor-addons)\nfor more details."]]
