Google Apps Script

Glossary

This page lists various terminology used in Google Apps Script and describes its meaning.

Active user

The user (Google account) that causes a script to execute. Depending on the execution method this may be different from the effective user. You can also think of this as the user at the keyboard.

More information: Scripts and Google Accounts

Container

A Google product that can contain scripts. For example Spreadsheets and Sites are both containers because new scripts can be created and be accessed from each of these products. Creating a script in a container typically makes it easier to access and manipulate the data in the container.

More information: Scripts and Containers

Container-bound script

A script which is created from within a container, such as Spreadsheet or Site. This script does not show up in Drive and is only accessible from within the container.

More information: Scripts and Containers

Effective user

The user (Google account) under whose identity a script executes. Depending on the execution method this may be different than the active user. The permissions of the effective user are used in the execution context.

More information: Scripts and Google Accounts

Execution Context

Every script executes in a secure sandbox and it has access to only authorized resources for a given identity. This secure sandbox can be called Execution Context.

Library

A script project that can be included into other scripts, allowing for common code to be shared. Unlike installing a script from the gallery, adding a library does not copy the script into your account. When adding a library you specify a version to use, as well as an identifier to reference it by.

More information: Managing Libraries, Managing Versions

Resource

An entity associated with a project that does not represent code. Libraries, triggers, properties and user interface components are script resources.

ScriptDb

A JavaScript Object database available in Google Apps Script. Each script project gets a private database which you can use to save, update and search for JavaScript Objects.

More information: ScriptDb

Scriptlet

A piece of Google Apps Script code that is embedded into an HTML template. The scriptlet is everything between the <? ?> tags.

More information: Html Service

Script project

A collection of files and resources in Google Apps Script, sometimes referred to simply as "the script". The script editor always has one and only one project opened at any given time. You can open multiple projects in multiple browser windows or tabs.

More Information: Managing Projects

Standalone script

A script that is accessible from Google Drive. Unlike a container-bound script, it is not attached to any specific Google product, like Spreadsheets or Sites.

More information: Scripts and Containers

Trigger

A resource in the project that causes a function to be run when a specified event takes place. Triggers can be created for user initiated events such as opening a spreadsheet or changing a cell value, or for time based events that fire every day, hour, etc.

More information: Understanding Triggers

Version

A snapshot of a script at a given point in time. Versions are automatically assigned a number when they are created, and a description can optionally be added.

More information:Managing Versions, Managing Libraries

Web app

A script which has been deployed such that users can access it using only a URL. This was previously known as publishing the script as a "service".

More information: Web Apps

Authentication required

You need to be signed in with Google+ to do that.

Signing you in...

Google Developers needs your permission to do that.