Stay organized with collections
Save and categorize content based on your preferences.
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.
[[["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-01-27 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."]]],[]]
