Android multi-app kiosk: add Camera app and restrict Wi-Fi to approved SSIDsSolved

For Android devices in multi-app kiosk, apps and Wi-Fi configurations are handled from the policy associated with the devices. To add apps to the Android multi-app kiosk:

1. Go to Policies.
2. Open the policy applied to the Android tablets.
3. Navigate to Kiosk Lockdown > Android Kiosk Lockdown > Multi App.
4. Add the required apps, such as Camera, WhatsApp, or any other approved application.
5. Save the policy and ensure it is associated with the target devices.

If the app is a managed Google Play app, Hexnode may install Google Play services or the Play Store components in the background as needed for silent app installation. The user does not need to interact with the Play Store in kiosk mode.

For Wi-Fi configuration:

1. Open the policy applied to the devices.
2. Go to Android > Networks > Wi-Fi.
3. Add each approved SSID with the required security type and password.
4. Push the policy to the enrolled tablets.

This configures the enrolled devices to use the specified Wi-Fi networks. It does not change the router, SSID, or password settings for non-enrolled devices. Any restrictions applied from Hexnode affect only the managed devices.

I tried adding multiple SSIDs to the policy, but while the tablet was in kiosk mode I couldn’t get to some of the Wi-Fi options for testing. Is that expected? Also, can Hexnode force the tablet to always connect to the nearest or strongest approved Wi-Fi?

Yes, kiosk mode can limit access to system settings, including Wi-Fi options, depending on how the kiosk policy is configured. For testing, you can temporarily exit kiosk mode or disable kiosk on a test device, verify the Wi-Fi configuration, and then re-enable kiosk once the network behavior is confirmed.

Regarding automatic switching, Hexnode can push approved Wi-Fi configurations to Android devices, but it cannot fully control Android’s internal Wi-Fi selection logic. Android decides which saved network to connect to based on signal strength, network history, priority, and OS-level behavior.

This means:

• Hexnode can configure multiple approved SSIDs on enrolled devices.
• Hexnode can help prevent users from manually adding or modifying networks if the relevant restrictions are applied.
• Hexnode cannot guarantee that the device will always connect to the nearest or strongest SSID. – Hexnode cannot guarantee that Android will not switch networks during an active transaction or workflow.
• Hexnode cannot prevent non-enrolled devices from seeing or connecting to the SSID. That must be handled at the network/router level using WPA security, password control, MAC filtering, VLANs, or other network-side controls.

If the goal is to prevent users from using unapproved networks, configure the approved SSIDs through policy and restrict user access to Wi-Fi settings where possible. If the goal is to control roaming behavior between access points or vehicles, that part depends on Android and the wireless network design rather than MDM alone.

That clears it up. So the policy is mainly for enrolled tablets, not for locking down the actual Wi-Fi network. We’ll push the SSIDs through Hexnode and handle the rest from the router/network side.

Correct. A good deployment flow would be:

1. Add the required apps to the multi-app kiosk policy.
2. Add all approved Wi-Fi SSIDs under the Android Wi-Fi network configuration.
3. Apply the policy to a small test group first.
4. Test the devices while they are physically within range of the configured SSIDs.
5. Re-enable or tighten kiosk restrictions after confirming the tablets connect as expected.

For production use, combine Hexnode’s Wi-Fi policy with proper network-side security. Hexnode manages the enrolled Android tablets, while routers and access points control who can see or join the wireless network itself.