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.
Last updated
With Appetize's app permissions, users can manage who has access to their app, can debug apps or view network traffic logs and more.
Last updated
See Sharing .
By default, only users linked to your organization and signed in to Appetize will have access to your App Identifier link.
See Sharing .
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 organization level or the app build level.
Set and control default session permissions across your organization by navigating to .
App Build Permissions will override Organization Session Default Permissions. We recommend using Organization Session Default Permissions. In the future we will introduce more granular ways to provide permissions for your apps.
and finally configure the option under Settings > App Permissions.
Configure the permissions below to determine whether you need to be authenticated with Appetize and linked to the organization or simply have the Embed or View link for an app in order to perform the following actions.
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
For the app-level setting, navigate to your , select your preferred app and then select the build you want to change permissions for:
App Level Permissions can also be applied when uploading the app via our REST API. See and for more information.
