> ## Documentation Index
> Fetch the complete documentation index at: https://firespark.cloud/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up kiosks

> Create a kiosk channel, link tablets by code, optionally connect Google Play, then publish the private app.

A **kiosk** is an in-store tablet that stays on your ordering app. Customers walk up, place an order, and the ticket goes to the same kitchen systems you already use.

Fire spark does not treat the kiosk as a separate menu product. The tablet reads the same operational menu as your other channels, with a composed offer if you want combos first. See the [Kiosk](https://firespark.cloud/docs/integrations/channels/kiosk.md) overview for that product model.

This guide is the setup path. Link tablets from **Devices** with the code shown on the splash screen. [Connecting a Google Play account](https://firespark.cloud/docs/guides/channels/kiosk/connect-google-play.md) is optional until you want MDM lock or private APK rollouts.

## Why kiosk setup is different

App and web channels run on phones and browsers the customer already owns. A kiosk is hardware you put on the floor:

* The tablet must stay on your kiosk app, not the public Play Store
* Staff should not be able to install other apps or leave the ordering screen
* You need a way to enroll many tablets with a QR, not by installing an APK by hand
* You need a way to push a new version of the app to every store without walking tablet to tablet

Google provides that control through **Android Enterprise** and **Managed Play**. Fire spark uses your Google Play account to talk to those Google services. Without that link, you can still **claim a tablet by code**, push settings and commands, and take orders. You cannot lock the tablet to the private app or publish APKs from the dashboard.

## Create a kiosk channel

If you do not have a kiosk channel yet, follow [Set up channels](https://firespark.cloud/docs/guides/channels.md) and set **Type** to **Kiosk**.

When you open that channel from **Channels**, you land in the **kiosk hub** (`Channels →` the kiosk channel). The header describes devices, releases, and session settings. Tabs across the top are **Settings**, **Devices**, **Releases**, and **Health**.

> [!NOTE]
>
> Opening a kiosk channel does not open the generic channel page. It opens the
> kiosk hub so device and release work stay in one place.

## Work through the hub in this order

**1. Review Settings**

**Settings** is available before Play is connected. Use it for session timeouts and health thresholds. MDM fields (package name, lock mode) matter after Play is connected and you are ready to lock tablets.

**2. Link tablets on Devices**

Open **Devices** and click **Link device**. Type the hardware-stable code shown on the tablet splash (QR or text). The tablet polls [Link kiosk device](https://firespark.cloud/docs/storefront-api/kiosk/devices/link/post.md) until it is claimed, then stores store, channel, settings, and payment overrides.

**3. Connect Google Play (optional)**

A card on **Releases** asks you to **Connect a Google Play account** when you want MDM lock or private APKs. Follow [Connect a Google Play account](https://firespark.cloud/docs/guides/channels/kiosk/connect-google-play.md).

**4. Enroll tablets in MDM**

After Play is active, open each linked device and follow [Enroll a kiosk in MDM](https://firespark.cloud/docs/guides/channels/kiosk/enroll-mdm.md). That is Attach MDM, a factory reset, and the enrollment QR. Releases only install on enrolled tablets.

**5. Publish builds on Releases**

After tablets are `ENROLLED`, **Releases** uploads the private APK to Managed Play and rolls it out in phases. Dedicated release steps will live in a later guide.

**6. Watch Health**

**Health** groups tablets by store and flags low battery, offline, or not-operational devices. It does not require a separate Play action once devices are enrolled.

## What you see in the hub today

| Tab | What it is for | Needs Google Play? |
| - | - | - |
| Settings | Idle timeout, health thresholds, package name, lock mode | No, for session and health fields. MDM lock settings apply after Play is connected. |
| Devices | Link by tablet code, per-device payment overrides, remote commands | No. Play is only needed later to attach MDM. |
| Releases | Emergency hotfix or normal rollout | Yes. Releases stay blocked until Play is connected. |
| Health | Battery, offline, and not-operational counts per store | No. Useful after tablets exist. |

## Next

> [card] [Connect a Google Play account](https://firespark.cloud/docs/guides/channels/kiosk/connect-google-play.md)
>
> Why Fire spark needs Play, and how to connect a new account or reuse one already in this organization

> [card] [Enroll a kiosk in MDM](https://firespark.cloud/docs/guides/channels/kiosk/enroll-mdm.md)
>
> Attach MDM on a linked tablet, scan the QR after a factory reset, then use Releases

> [card] [Link kiosk device](https://firespark.cloud/docs/storefront-api/kiosk/devices/link/post.md)
>
> Storefront API for the tablet code, heartbeat, overrides, and realtime token


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.