Overview
The Android KIOSK Policy allows organizations to lock down Android devices into a dedicated, single-purpose mode—commonly known as "Kiosk Mode." This is ideal for scenarios where devices are used for a specific application or set of applications, such as point-of-sale terminals, digital signage, or self-service kiosks. With the KIOSK Policy, administrators can control which apps and features are accessible, providing a secure and streamlined user experience.
Key Features
Kiosk Custom Launcher: Enable a custom launcher that restricts device access to only approved apps and settings.
Kiosk Customization: Configure the appearance and behavior of the kiosk environment, including branding, allowed actions, and UI elements.
Enhanced Security: Prevent users from exiting kiosk mode, accessing system settings, or installing unauthorized apps.
Remote Management: Apply, update, or remove kiosk policies remotely via the Swif platform.
When to Use Android KIOSK Policy
Retail stores using tablets for customer check-in or product browsing
Restaurants deploying self-ordering kiosks
Warehouses with dedicated inventory scanning devices
Schools or libraries providing public-use tablets
Any scenario where you need to restrict device functionality to a specific app or set of apps
How to Configure Android KIOSK Policy
Navigate to Policies
Log in to your Swif admin console and go to the Policies section.Create or Edit a Policy
Click Create Policy or select an existing policy to edit.
Choose Android as the platform.
Enable KIOSK Mode
Find the KIOSK Policy section.
Toggle Kiosk Custom Launcher Enabled to ON.
Configure Kiosk Customization options:
Select which apps are allowed in kiosk mode.
Customize the home screen layout and branding.
Set restrictions for navigation, notifications, and system access.
Assign the Policy
Assign the policy to the desired devices or groups.
Save and deploy the policy.
Device Behavior
Once the policy is applied, devices will reboot into kiosk mode.
Only the approved apps and features will be accessible.
Users will not be able to exit kiosk mode without administrator intervention.
Best Practices
Test your kiosk configuration on a sample device before deploying widely.
Clearly communicate to end-users how to use the kiosk device and who to contact for support.
Regularly review and update allowed apps and settings to ensure security and usability.
Troubleshooting
Device not entering kiosk mode?
Ensure the device is enrolled and the policy is assigned correctly. Check for connectivity issues.Need to exit kiosk mode?
Use the admin exit method configured in your policy (e.g., PIN code or remote unlock via Swif console).App not visible in kiosk mode?
Verify the app is installed on the device and included in the allowed apps list.
Additional Resources
Note: The Android KIOSK Policy is a powerful tool for device management. For advanced customization or troubleshooting, please refer to your organization’s IT administrator or contact Swif support.