Appetize Docs
HomeDemoUploadPricing
  • Introduction
  • Platform
    • App Management
      • Uploading Apps
        • Android
        • iOS
      • App Dashboard
      • Running Apps
      • App Permissions
    • Device Sandbox
    • Embedding
    • Sharing
    • Session Inactivity Timeout
    • Query Params Reference
  • Features
    • Devices & OS Versions
    • Network Traffic Monitor
    • Debug Logs
    • UI Automation
    • Proxy
    • Language & Locale
    • Mock Location
    • Deep links
    • Launch Params
    • Media
    • Auto-grant Permissions
    • Custom Branding
    • Custom Launch Pages
    • Advanced Features
      • Android
        • ADB tunnel
        • Hide Password Visibility
      • Reserved Devices
  • Account
    • Invite your team
    • Single Sign-On
      • OpenID Connect
      • SAML
      • Azure Active Directory
      • Google Workspace (GSuite)
    • Reporting
      • Session History
      • Usage Summary
  • Infrastructure
    • Configure Network Access
    • Enterprise Hosting Options
  • JavaScript SDK
    • Configuration
    • Automation
      • Device commands
      • Touch interactions
    • API reference
      • Initialization
      • Client
      • Session
      • Types
        • AdbConnectionInfo
        • AppetizeApp
        • AndroidElementAttributes
        • Coordinates
        • DeviceInfo
        • Element
        • ElementBounds
        • IOSAccessibilityElement
        • IOSElementAttributes
        • NetworkRequest
        • NetworkResponse
        • SessionConfig
        • SwipeMove
        • RecordedAction
        • RecordedSwipeAction
        • RecordedKeypressAction
        • RecordedPosition
        • RecordedTapAction
        • RecordedTouchAction
        • UserInteraction
  • Testing
    • Getting Started
    • Writing Tests
    • Running Tests
    • Test Configuration
    • Continuous Integration
    • Record Tests (experimental)
    • Trace Viewer
    • Web Tests on Mobile Browsers
  • REST API
    • Create new app
    • Update existing app
    • Direct file uploads
    • Delete app
    • List apps
    • Usage summary
    • Devices & OS Versions
      • v1
    • IP Blocks
      • v1
  • Guides & Samples
    • Impersonation
    • Automate Sign-in Flow
    • Screenshot Automation
    • Unlock Device
    • Validate Analytics Events
    • Lock Your Device to One App
    • Test Accessibility Font Sizes
    • Common testing scenarios
    • Samples Repository
  • Deprecated
    • Cross-document messages
  • Changelog
  • Additional Support
    • Knowledge Base
    • Support Request
Powered by GitBook
On this page
  • Who can run your app
  • App Identifier Link
  • Build Identifier Link
  • Organization Session Default Permissions
  • App Build Permissions
  • Permissions
  1. Platform
  2. App Management

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.

PreviousRunning AppsNextDevice Sandbox

Last updated 2 months ago

Who can run your app

App Identifier Link

See Sharing .

By default, only users linked to your organization and signed in to Appetize will have access to your App Identifier link.

Build 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.

Organization Session Default Permissions

Set and control default session permissions across your organization by navigating to .

App Build Permissions

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.

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.

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

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.

Dashboard
Create new app
Update existing app
Organization -> Session Defaults
Example Organization App Build Permissions
Select the build you want to apply permission to
Example App Build Level Permissions
App Identifier Links
Build Identifier Links