For the complete documentation index, see llms.txt. This page is also available as Markdown.

Session Defaults

Every Appetize session starts from a set of defaults: device, language, timeouts, developer tools. Session Defaults sets those once for the whole organization, instead of repeating them in every link, embed and SDK call.

It lives under Organization → Session Defaults at appetize.io/organization/session-defaults. Admins only.

What's on the page

Twenty-eight settings in five sections:

Section
Covers

Session Behavior

How long a session lasts, and what happens when it starts and ends

Default Devices

The iOS and Android device and OS version a session opens on

Location and language

Language, locale, timezone, mock location, iOS keyboard

Display and presentation

Scale, orientation, appearance, device frame

Developer tools

Debug logs, ADB, intercept proxy, audio, automation recorder

Each one is the account-level default for a value you can already set per session, so every setting is documented where that per-session value is. JavaScript SDK configuration is the complete reference; Query Params Reference covers the same settings as URL parameters. Several also have their own page: Devices & OS Versions, Language and Locale, Mock Location, ADB tunnel, Debug logs.

Use the search box rather than scrolling. It matches names, descriptions and platform tags across all five sections.

How a value is chosen

Session time limit and Inactivity timeout are enforced by Appetize, so they apply to every session however it started (app link, embed, JavaScript SDK, CLI or REST API), and no query parameter overrides them. The first value set wins:

  1. The app build's own setting (Apps → your app → the build → Settings)

  2. Your session default

  3. Appetize's default: no time limit, 2 minute inactivity timeout

Every other setting is the session's starting configuration, so a per-session value wins over your default: ?device=pixel7&language=fr still does what it says.

  1. The query parameter, or config passed to the JavaScript SDK

  2. Your session default

  3. Appetize's default

Changing a setting

Default (…) means you have not set anything, and the value in brackets is what Appetize uses. Changes save as you make them (there is no save button) and each section header counts how many of its settings you have changed.

Picking Default again clears the stored value rather than pinning it, so you keep following Appetize's default if it changes later.

  • Session time limit: Unlimited, or 5 minutes to 8 hours.

  • Inactivity timeout: 30 seconds to 2 hours. See Session Inactivity Timeout for per-build timeouts.

  • Device and OS version save as a pair, so you cannot store a combination that would fail to start.

Defaults apply to sessions started from now on. A session that is already running is not affected.

The Permissions (Legacy) switches at the bottom of the page are covered in App Permissions.

Last updated

Was this helpful?