Web apps and API executables manifest resource

  • Resource configurations define how web apps and APIs execute within a project.

  • Web app configurations control access levels (MYSELF, DOMAIN, ANYONE, ANYONE_ANONYMOUS) and execution identity (USER_ACCESSING, USER_DEPLOYING).

  • API executable configurations manage access permissions for running scripts via the API, using similar access levels as web apps.

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 }
Fields
access

string

The levels of permission for running the web app. The valid settings are the following:

  • MYSELF indicates only the user who deployed the app can run it.
  • DOMAIN indicates only users in the same domain as the deploying user can run it.
  • ANYONE indicates any user who is logged in.
  • ANYONE_ANONYMOUS indicates any user, even if not logged in.
executeAs

string

The identity under which the web app executes. The valid settings are the following:

  • USER_ACCESSING indicates the web app runs as the user accessing it.
  • USER_DEPLOYING indicates 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 }
Fields
access

string

Determines who has permission to run the script from the API. The valid settings are the following:

  • MYSELF indicates only the user who deployed the script can run it.
  • DOMAIN indicates only users in the same domain as the deploying user can run it.
  • ANYONE indicates any user who is logged in.
  • ANYONE_ANONYMOUS indicates any user, even if not logged in.