AI-generated Key Takeaways
-
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's web app configuration, which is only used if the project is deployed as a web app.
| JSON representation |
|---|
{
"access": string,
"executeAs": string
}
|
access
string
The levels of permission for running the web app. The valid settings are the following:
-
MYSELFindicates only the user who deployed the app can run it. -
DOMAINindicates only users in the same domain as the deploying user can run it. -
ANYONEindicates any user who is logged in. -
ANYONE_ANONYMOUSindicates any user, even if not logged in.
executeAs
string
The identity under which the web app executes. The valid settings are the following:
-
USER_ACCESSINGindicates the web app runs as the user accessing it. -
USER_DEPLOYINGindicates the web app runs as the user who deployed it.
ExecutionApi
The script project's API executable configuration. This is only used 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. The valid settings are the following:
-
MYSELFindicates only the user who deployed the script can run it. -
DOMAINindicates only users in the same domain as the deploying user can run it. -
ANYONEindicates any user who is logged in. -
ANYONE_ANONYMOUSindicates any user, even if not logged in.

