Falaah Falaah AI

Device Management

Pair tablets and screens with a setup code or Android zero-touch enrollment, watch fleet health, send remote commands, and see what each one actually did.

A managed device is a tablet or screen you have paired with Muin: a donation kiosk, a lobby signage panel, a counter till. Once paired you can see whether it is checking in, change what it runs, and act on it without standing in front of it.

When you’d use this

  • Bringing a new tablet up as a kiosk or a signage screen.
  • Finding out why a screen in another building has gone dark.
  • Taking a screen out of kiosk mode so somebody on site can use it.
  • Rolling out the same change to every panel in a building at once.
  • Stopping a lost or stolen tablet from reaching your data.

Everything sits in the sidebar under Devices & Kiosk.

Entry What it is for
Get a screen live The guided four-step path for a new signage screen
Device Registry Every paired device, and where you pair a new one
Pending Pairings Setup codes that have been generated but not yet used
Fleet Dashboard Health at a glance, and the per-device detail view
Quiet hours When a screen may not restart itself for an update
Kiosk Configs What a paired device actually runs
Board Layouts How a signage panel is divided
Kiosk Campaigns The donor-facing ask a kiosk shows
Fleet Commands The log of every command, and what the device did with it
Device Locations Floors, areas and rooms within a location

Pairing a device

Pairing starts in the console and finishes on the device. Device Registry carries the wizard, which runs in three phases.

  1. Details: name the device, choose its type, pick its location, choose its security level, and optionally pick the kiosk config it should run.
  2. Pairing: Muin mints a six-digit setup code and shows it with a QR code. The panel waits, reading Waiting for device…, and flips to Paired by itself when the device claims the code. You do not have to leave the page to find out whether it worked.
  3. Paired: the device is in the registry with the name, type, location, security level and config you chose.

On the device, open the Muin Go app and enter the code, or scan the QR.

The code carries your intent, and the claim applies it. Everything you set in step 1 travels with the code and is stamped onto the device when it claims it, so one pairing produces exactly one device record. Generate codes in bulk, and revoke unused ones, from Pending Pairings.

Android zero-touch enrollment

For Android tablets you can skip the Muin-side wizard and enroll through Android’s own device-management path instead. Muin mints an enrollment QR code that the Android setup wizard scans out of the box, and the enrollment survives a factory reset.

The QR can also carry the venue Wi-Fi, so the tablet joins the network by itself with nobody typing a password on a wall-mounted screen. Treat that QR as a credential: it is single-use and expires in fifteen minutes, the network password is stored nowhere, and the console replaces an expired code with a prompt to generate a fresh one. Without embedded Wi-Fi the token lasts an hour.

Android fixes the device’s mode at enrollment, and Muin cannot change it afterwards. A tablet enrolled under a policy that is not a kiosk policy will never enter kiosk lockdown, however many times you reassign it, and the device will keep reporting itself as compliant while it does. The only fix is a factory reset and a fresh enrollment. Mint the enrollment code against the policy the screen is actually going to live on.

Security levels

The security level you choose at pairing decides how firmly the device is held on the Muin app:

Level What it means
Lock task mode The app is the device owner and the system holds it in lock task mode. The strongest option, and the one a public kiosk wants.
Launcher Muin Go becomes the device’s launcher.
App level The app holds itself in place with an in-app overlay only. The weakest, and the right choice for a staff tablet that is also used for other things.

A locked kiosk sits in a Locked state: that is its resting condition, not a fault. Three things can get a stranded device out of it: the kill-switch gesture on the device, the kiosk staff panel behind its PIN, and the turn off kiosk command from the console.


Watching the fleet

Fleet Dashboard is the health board: how many devices are paired, how many are checking in, which ones carry an unresolved alert, and battery state across the fleet. Open a device for its own detail view, with its connectivity, its battery, what it is currently running and its recent activity.

Devices report in on a regular heartbeat, so “last seen” is the number to trust when a screen looks wrong. Fleet > alert settings is where you set the thresholds (how long offline counts as offline, how low a battery has to go) and who is emailed. Those recipients start empty, so a screen that dies emails nobody until you fill them in.


Device locations

A device’s location comes from your central Locations registry. Device Locations adds the sub-placement underneath it: a floor, an area or a room. That is what turns “offline” into “the panel in the second-floor hallway”, which is the difference between a useful alert and a puzzle.


Remote commands

Open a device from the Fleet Dashboard to act on it, or broadcast to many at once from the dashboard.

Command What it does Platforms
Lock Puts the device into its locked kiosk state Android and iOS
Unlock for maintenance Releases the lock so somebody on site can use the device Android and iOS
Turn off kiosk Reverses the lockdown while leaving the device enrolled and configured Android and iOS
Force config sync Pulls the latest configuration and campaigns now Android and iOS
Wipe config Clears the device’s configuration Android and iOS
Update app Asks the device to take its app update Android and iOS
Display sleep / Display wake Turns the panel off and on Android and iOS
Collect logs Pulls the device’s own recent log buffer for support Android and iOS
Broadcast config Pushes a configuration to a set of devices Android and iOS
Restart app Restarts Muin Go on the device Android only
Capture screenshot Takes a picture of what is on the screen Android only
Clear app data Clears the app’s local data Android only
Factory reset Wipes the device Android only

Lock asks you to confirm; unlock does not. Restoring service is never the dangerous direction.

There is no plain “reboot” command. A reboot or a device-wide wipe is an Android device-management action rather than a Muin one, and the app notices when it has happened.

A command is applied by the device, not by the console. Muin tells you the command was sent and that it will apply at the device’s next check-in, because an offline device applies nothing until it reconnects. A success message that claimed the device was locked would be a claim Muin cannot make.

Where you see what actually happened

Fleet Commands is the log, and it is the honest answer. Every command moves through pending, delivered, acknowledged and executed, or lands on failed, timed out or expired. The page refreshes itself, so you can watch a command land without reloading. Filter by status, by command type or by device.


Staff devices

Phones and tablets people sign into with their own account are listed separately, under Settings > Security > Mobile Devices, with revoke and reset pairing actions. Owners and admins see every device in the organization; everyone else sees only the devices they set up themselves. That is the screen to use when a phone is lost.


What it affects

  • What a screen shows: a config sync or a broadcast changes the board or the ask at the device’s next check-in.
  • Whether a kiosk can be walked away from: the security level chosen at pairing is what holds the app in place.
  • Who is told when a screen dies: the alert recipients on the fleet alert settings, nobody by default.
  • The audit trail: every command records who sent it, when, and what the device did.

When it goes wrong

What you see What it means What to do
A device shows offline It has stopped checking in. Network, power or the panel itself. Check “last seen”, then the connection on site.
A command sits at pending The device has not checked in since you sent it. Commands wait; they apply on reconnect. If it never arrives, the device is genuinely down.
A command lands on timed out It was delivered but the device did not report back. Read the row in Fleet Commands, then retry. Repeated timeouts on one device is a hardware conversation.
A command is refused as unsupported Four commands are Android-only: restart app, screenshot, clear app data and factory reset. Use one of the cross-platform commands instead.
A tablet never enters kiosk lockdown, but reports itself healthy It was enrolled under a policy that is not a kiosk policy, and Android fixed that at enrollment. Factory reset the device and enroll it again against the kiosk policy.
A pairing code was generated but never used Somebody left the flow before entering it on the device. Revoke it in Pending Pairings and generate a fresh one.
An enrollment QR carrying Wi-Fi has stopped working It is single-use and expires in fifteen minutes. Generate a new one when you are standing at the device, not before.
A tablet is stuck in kiosk mode with nobody able to use it It is locked, which is the intended resting state. Send turn off kiosk, use the staff panel behind its PIN, or the on-device kill-switch gesture.
A screen restarted itself during a service No quiet-hours window covers that time. Add the window under Devices & Kiosk > Quiet hours.

Next step

Decide what the paired device runs: Kiosk Campaigns for a donation station, or Digital Signage for a board. For an unattended Android donation tablet end to end, see QuickPay setup.