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.
When you upload an app to Appetize, you receive a link to view your app. This link includes the app's assigned publicKey, and looks like this:
https://appetize.io/app/:publicKey
This
publicKey is an unguessable cryptographically generated 128-bit random string. By default, anybody who has your app's link, i.e. its publicKey, will have permission to run your app. Your app link can be easily shared with whomever you'd like, or embedded into your own applications.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 app-level or the account-level.
App Level Permissions will override Account Level Permission Defaults
%20(1)%20(1)%20(2).png?alt=media)
Select "Manage" under your app
and finally configure the option under 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.
%20(2).png?alt=media)
Example App Level Permissions
%20(1).png?alt=media)
Example Account Level 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.
Permission | Description |
|---|---|
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 modified 21d ago