Deploy via EMM

What is an EMM?

An enterprise mobility management platform (EMM) lets an IT team manage a group of Android tablets from one place. Examples include Microsoft Intune, Jamf Pro, Esper, Scalefusion, and Samsung Knox. After you enrol the Jonot apps through Managed Google Play, the EMM can send Managed Configurations to each device. These key/value settings take effect when the app starts and when an administrator changes them. You do not need a new APK build.

Enrolling in Managed Google Play

Before you can push configuration, your Jonot apps must be available in your EMM’s app catalogue:

1. Follow Google’s Import an app from Google Play guide to add Jonot Kiosk, Jonot Desk or Jonot Display to your Managed Google Play account.
2. In your EMM, add the required apps to each device profile.
3. The EMM automatically discovers each app’s managed-configuration schema (defined in app_restrictions.xml inside the APK). No manual schema import is needed.

Configuration keys

All keys are optional. Strings default to empty.

Key	Apps	Type	Effect
managerPin	Kiosk	string	Sets the manager PIN and skips the first-run PIN dialog. Use 4–32 digits.
allowEscapeHatch	Kiosk	bool	Enables the 5-tap top-right corner gesture. Defaults to true.
kioskUrlOverride	Kiosk	string	Overrides https://kiosk.jonot.io.
deskUrlOverride	Desk	string	Overrides https://desk.jonot.io.
displayUrlOverride	Display	string	Overrides https://display.jonot.io.
apiOriginOverride	Kiosk, Desk, Display	string	Overrides https://api.jonot.io.

Desk and Display do not support managerPin or allowEscapeHatch. Leave URL and API overrides blank for production. Use them only for staging or LAN deployments.

The apps do not support pairing through managed configuration. Remove pairingCode from existing EMM policies. The apps ignore that obsolete key; pushing, changing or clearing it does not pair or unpair a device.

Deploying settings in your EMM

The exact UI varies by EMM, but the general steps are:

1. In your EMM console, open the managed app configuration for Jonot Kiosk, Jonot Desk or Jonot Display.
2. The EMM renders the schema as a form. Fill in the keys you want to set; leave the rest blank to use defaults.
3. Assign the configuration to your device group or individual devices.
4. Push the configuration. The app receives it immediately if the device is online, or on next check-in.
5. The app reads and applies the new configuration. URL and origin changes reload the WebView. This resets any customer flow in progress.

Recommended per-deployment settings

• Kiosk managerPin: set a PIN that meets your organization’s policy, or leave blank for on-site setup. Push a new PIN to recover a forgotten PIN.
• Kiosk allowEscapeHatch: use true when staff need the manager menu. Set false only when no on-site management access is needed.
• Desk and Display: leave all keys blank for a standard production deployment.

URL overrides

You do not need the URL override keys for standard production deployments. Only set them if:

• You are testing against a staging environment.
• You have an on-premises offline host on a local network.

If you set a URL override, also ensure the device’s ALLOW_CLEARTEXT build config allows HTTP (for LAN URLs). This requires a custom build — the Play Store build always defaults cleartext to false.

Behaviour details

• Kiosk manager PIN (managerPin): Takes effect on the next manager-menu tap. A nonempty value replaces the on-device PIN at startup and on configuration changes. Clearing the setting keeps the stored PIN.
• Kiosk escape hatch (allowEscapeHatch): Takes effect immediately on configuration changes.
• URL/origin overrides: Recreate the app’s WebView and backend configuration when their effective values change. Any in-progress device flow resets.

Pair each device

Pairing requires approval from a signed-in Jonot administrator with access to the target location. EMM enrollment does not grant that access.

1. Open the Jonot app on the device, open its pairing screen and read the 7-character pairing code.
2. Sign in to the admin dashboard. Open device management for the target location, enter the device’s code and select its queue.
3. Confirm pairing. The device receives its credential and opens its setup or queue screen. If the code expires, request a new code from the device’s pairing screen.

Follow the illustrated instructions for Kiosk, Desk or Display. To re-pair a device, revoke its existing pairing in the dashboard and repeat the pairing flow when the device shows a new code.