Page Summary
-
This document describes the resource configurations for web apps and API executables.
-
The web app configuration, used when a project is deployed as a web app, defines access permissions and the execution identity.
-
The API executable configuration, used when a project is deployed for API execution, defines access permissions.
-
Both web app and API executable configurations use a string field named
accessto specify permission levels for running the script. -
The web app configuration includes an additional string field
executeAsto determine the identity under which the web app runs.
The resource configurations used to define web apps and API executables.
Webapp
The script project web app configuration, used only if the project is deployed as a web app.
| JSON representation |
|---|
{
"access": string,
"executeAs": string
}
|
access
string
Web app execution permission levels. Valid settings include:
-
MYSELF: Only the deploying user can run the app. -
DOMAIN: Only users in the same domain as the deployer can run it. -
ANYONE: Any logged-in user. -
ANYONE_ANONYMOUS: Any user, even if not logged in.
executeAs
string
The identity under which the web app executes. Valid settings include:
-
USER_ACCESSING: The web app runs as the user accessing it. -
USER_DEPLOYING: The web app runs as the user who deployed it.
ExecutionApi
The script project API executable configuration, used only if the project is deployed for API execution.
| JSON representation |
|---|
{
"access": string
}
|
access
string
Determines who has permission to run the script from the API. Valid settings include:
-
MYSELF: Only the deploying user can run the script. -
DOMAIN: Only users in the same domain as the deployer can run it. -
ANYONE: Any logged-in user. -
ANYONE_ANONYMOUS: Any user, even if not logged in.
