App Permissions

With Appetize's app permissions, users can manage who has access to their app, can debug apps or view network traffic logs and more.

Who can run your app

See Sharing App Identifier Links.

By default, only users signed in to your account will have access to your App Identifier link.

See Sharing Build Identifier Links.

By default, anybody who has your app's Build Identifier link, i.e. its buildId (previously known as publicKey), will have permission to run your app.

Some customers want to restrict access, so that only authenticated users may run their app. For this purpose, we have a configuration option which can be set at either the account-level or the app-build-level.

Account Level Permissions

You can apply account-wide permissions on your Account.

App Build Level Permissions

App Build Level Permissions will override Account Level Permission Defaults. We recommend using Account Level Defaults. In the future we will introduce more granular ways to provide permissions for your apps.

For the app-level setting, navigate to your Dashboard, select your preferred app and then select the build you want to change permissions for:

and finally configure the option under Settings > App Permissions.

App Level Permissions can also be applied when uploading the app via our REST API. See Create new app and Update existing app for more information.

Permissions

Configure the permissions below to determine whether you need to be authenticated to the account or simply have the Embed or View link for an app in order to perform the following actions.

PermissionDescription

run

Run your application

networkProxy

Specify a network proxy when running the app

networkIntercept

Use Appetize's intercepting proxy when running the app

debugLog

View your app's NSLog/Logger or Logcat output

adbConnect

Debug your app by connecting ADB to the hosted emulator

androidPackageManager

Allow the installation of additional APK's while your app is running

Last updated