Stay organized with collections Save and categorize content based on your preferences.
Before building your Editor add-on, review the Apps Script quotas and limitations to ensure your project design aligns with these guidelines. Familiarizing yourself with these limits early in your development process can help prevent potential issues later on. Apps Script is ideal for lightweight add-on development for yourself, your team, or your organization. However, if you anticipate building a large-scale add-on that needs to handle many users, requires low latency, or demands full control over your infrastructure, consider developing a Google Workspace add-on on a different runtime environment.
Follow this general procedure when building an Editor add-on:
An Editor add-on is a standalone Apps Script project. The standalone script guide provides instructions to create new projects. You can also just open a new script. If you do this, the project file (initially named Untitled project) is placed in your root Drive folder.
When you collaborate with others in developing an add-on, a single user account owns the add-on project. When you publish an add-on, a single user account acts as the publisher. The publishing account must have edit access to the add-on script project, but it doesn't need to be project owner.
It's very important to avoid situations where you lose access to an add-on's code or settings because the owner of the project left your organization.
To prevent losing access to add-on code, we encourage you to use shared drives when you collaborate on an add-on. Placing your add-on script file in a shared drive ensures that no single account is the sole owner of the project.
It is also recommended that you add collaborators to the script project's Cloud Platform (GCP) project. This helps ensure someone on your team always can access the add-on's Cloud settings.
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. Code the add-onOnce you have created a script project, you can begin writing code to define the add-on appearance and behavior. You use the Apps Script HtmlService to construct the add-on user interface—dialogs and sidebars— using conventional HTML and CSS. Editor add-ons can define custom menu items as well.
As you code, refer to the Editor add-on style guide for guidelines on how to design your add-on user experience. Also, be sure you understand and program for the different authorization lifecycle states your add-on can encounter.
Test the add-onYou can test Editor add-ons before they are published to ensure they behave as expected. Testing requires you to create a test configuration and use a testing document, spreadsheet, form, or presentation.
See Test an Editor add-on for details.
Publish the add-onPublishing your add-on makes it available to others, either publicly or just users in your domain. Before you start the publishing process, be sure to review the publication overview.
Editor add-ons are published to the Google Workspace Marketplace. Publicly available add-ons must complete add-on review before they are published.
See Publishing an Editor add-on for more details.
Except 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. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-06 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-06 UTC."],[[["Editor add-ons are built using Apps Script, requiring a standalone Apps Script project and code for the add-on's functionality and user interface."],["Thorough testing is crucial before publishing using a dedicated test configuration and sample documents, ensuring the add-on functions as intended."],["Collaboration involves shared ownership and access, recommending the use of shared drives and adding collaborators to the Cloud Platform project for sustained accessibility."],["Publishing 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."],["The 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."]]],["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"]]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4