Manifests for Editor add-ons
An add-on uses a manifest file
to configure certain details about the app and its operation.
This documentation covers the details of configuring a manifest for a
Editor Add-on.
Manifest structure for Editor add-ons
The Apps Script manifest structure doesn't include any properties that are
specific to Editor add-ons. However, Editor add-on manifests can define the
general properties that are common to all Apps Script projects, such as
OAuth scopes and library dependencies.
See
Manifest structure
for a full list of potential manifest properties that Editor add-ons can use.
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-02-13 UTC.
[null,null,["Last updated 2025-02-13 UTC."],[[["Editor add-ons utilize a manifest file to define configuration details and operational aspects."],["The manifest structure for Editor add-ons leverages common Apps Script properties like OAuth scopes and library dependencies."],["While Editor add-ons don't have unique manifest properties, they can utilize general properties available to all Apps Script projects."],["A complete list of manifest properties applicable to Editor add-ons can be found in the Manifest structure documentation."]]],["Editor add-ons utilize a *manifest* file for configuration. While the manifest structure doesn't have properties unique to Editor add-ons, they can define general Apps Script project properties. These properties include OAuth scopes and library dependencies. A complete list of applicable manifest properties for Editor add-ons is available in the linked \"Manifest structure\" documentation. The manifest file details the app and its operations.\n"]]
