Falaah Falaah AI

Device Management

Pair kiosk tablets and screens with a setup code or Android zero-touch enrollment, watch fleet health, see why and for how long a device went offline, 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
Screens 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 Screens 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.

You can also pair from your phone. A new TV shows an Add this screen QR code: in Muin Go, open Screens, tap Scan and scan it, then pick the board, name, location, lock level and exit PIN. The same scan can replace a screen that lost its pairing and keep its name, board, location and history. See Manage screens from your phone.

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.

The Health tab on a device answers “is it working, and if not, why”. The top row shows its current status, uptime, downtime incidents and version. Below that, the uptime chart covers each day, and opening an incident shows when it started, how long it lasted and the likely cause, such as the app stopping while the tablet stayed on, or the tablet losing power or network. The troubleshooting card reads the same facts and suggests what to check. The version card shows what the device runs, the latest version and when it was last updated.

The activity log on a device can be searched, filtered by category and date, and paged. Downtime and errors are categories of their own, so you can list every outage on a device. Collect logs is what fills the device log view, so it stays empty until somebody sends that command.

Devices report in on a regular heartbeat, so “last seen” is the number to trust when a screen looks wrong. Status follows that heartbeat: once a device has been silent past its offline threshold it reads Offline, whatever it last reported. 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: a role, a team or named people, and a single device can pick its own. With nobody picked, alerts go to the people on the Device alerts row of Settings > Notifications > Who gets what, which is your owners and admins until you change it.

After hours

A kiosk or signage screen can go dark when you are closed. Only the screen turns off. The tablet stays on and plugged in, keeps checking in, and keeps reporting its battery, connection type and signal strength, and status, so you can still see it.

  • Set the hours in the kiosk config’s display schedule: your own sleep windows, or Follow opening hours, which sleeps the screen whenever its location is closed and wakes it a set number of minutes before you open (0 to 120). Change the location’s opening hours and the screens following them pick up the change.
  • It wakes at the end of the window, when somebody taps it (if tap to wake is on), or when you press Wake now on the device page. Sleep now puts it to sleep early, until the next scheduled change.
  • You can see it: the device page reads Online · Asleep with the time it wakes, the activity log records each sleep and wake and what caused it, and the uptime chart shades sleep as asleep. Sleep is never counted as downtime.
  • Overnight outages wait for the morning. If a screen goes offline while it is asleep, nobody is emailed or paged at night. The next staff digest carries the full story: when it went offline, when it was last seen, whether it came back and when, how long it was down, its battery and charging, its Wi-Fi signal strength and the likely cause. If it is still offline at its scheduled wake, the normal outage email goes out then, and escalation starts counting from that point.
  • A screenshot is skipped while the screen is asleep. Wake it first.

Screensaver on one screen

The kiosk config decides whether its screens show the screensaver when nobody is using them. To change that for a single screen, open the device and use Screensaver under Power & schedule:

  • Follow this screen’s config uses the kiosk config’s setting.
  • Off on this screen never shows the screensaver on this screen.
  • On on this screen shows it on this screen even when the config has it off.

The screen picks up the change at its next check-in.

TV app updates

Google TV screens update themselves. When Muin releases a new TV app, a test screen takes it first. Once that screen runs the new build, every other TV behind it is sent the update. A TV holds the update during its quiet hours and installs it afterwards. Tablets managed by Google take their updates through Google Play.

Requiring a newer app build

On a Google-managed tablet, Require app build on the device’s version card sets the lowest Muin app build the tablet may run. Enter the build number and save. Google installs at least that build on the tablet. A build Google cannot deliver is refused with the reason. Clear removes the minimum and puts the tablet back on the shared policy.


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
Identify Shows the screen’s name and location full-screen for 10 seconds, so you know which box is which Android and iOS
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.

Find and label a screen

  • Identify on the device page shows the screen’s name and location on the TV or tablet for 10 seconds.
  • Print label on the device page prints a 2 x 1 inch label with the screen’s name, location and a QR code. Stick it on the back of the TV. Scanning it with Muin Go opens that screen’s page, even when the TV is off.
  • The staff panel on a TV or tablet shows a QR code too. Scanning it with Muin Go opens that screen’s page.

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 device’s own pick, else the fleet alert settings, else the Device alerts row in notification settings (owners and admins by default).
  • How often a phone buzzes: up to 3 push notifications per outage, at the start, after 15 minutes and after an hour. Anything later goes to the in-app inbox only. When the device comes back, the people who were pushed get one more push saying so. A device that drops again within 10 minutes of coming back is treated as the same outage.
  • Other phone alerts: a screen that loses its pairing or fails an app update also sends a push. Tapping any device push in Muin Go opens that screen’s page. Each person can switch off push for Device alerts under Settings > Notifications.
  • Which alerts email right away: the start of an outage gets one email. A failed device check, a device leaving its geofence, and a crash storm each email at most 3 times a day per device, at least an hour apart. Everything else, and anything past those limits, goes into the next morning’s staff digest.
  • When an alert is ignored: an offline, frozen-screen, failed device check or geofence alert that nobody acknowledges is escalated to the next tier, on the alert’s channels plus the ops Slack channel.
  • 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. Open its Health tab, read the likely cause on the latest incident, then check the connection on site.
A screenshot says the screen is offline The device has not checked in recently, so nothing can take the picture. Wait for it to reconnect. A connected device answers straight away. Google’s device management has no screenshot command.
A device is behind on its version An app update needs the device online. A full store build arrives on Google’s own schedule, up to about a day. Check the version card. Update app applies over-the-air updates only.
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 is dark but shows Online · Asleep It is in its after-hours sleep, and the tablet is fine. Press Wake now on the device page, tap the screen if tap to wake is on, or adjust the display schedule.
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 Screens for a donation station, or Digital Signage for a board. For an unattended Android donation tablet end to end, see QuickPay setup.