Use the Custom Settings payload to send XML code that enables or disables specific Launcher settings. Some Launcher features can only be configured through XML pushed through the custom settings payload. In addition, many Launcher features are released for configuration through XML before the native toggles are added to the Launcher profile payload.
For each <characteristic> tag added under custom settings, define a unique UUID to avoid conflict errors. If two custom settings are targeting the same application and have the same UUID, only one of the settings will be processed on the device.
To avoid conflict errors with Launcher targeted XML, you can add multiple XML parameter tags into one characteristic tag. For example,
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="DisableFocusMonitoring" value="True"/>
<parm name="WriteSecurePermissionSettings" value="True"/>
</characteristic>****
Be sure to use the correct characteristic type depending your profile type:
- For Android profiles, use characteristic type = "com.airwatch.android.androidwork.launcher".
- For Android Legacy profiles, use characteristic type = "com.airwatch.android.kiosk.settings".
Below are Launcher features admins can enable through custom XML:
Granular Settings Control in Launcher
Admins can now choose which Launcher Settings items are shown to users. This allows admins to curate the Launcher Settings list based on their workflow and limit exposure to only the settings users need.
Use the following Custom XML to control which Launcher Settings items are displayed.
Example: Hide selected Launcher Settings items
<characteristic type="com.airwatch.android.androidwork.launcher"
uuid="568bc89d-1df8-4cc9-a841-e5a24aac54321">
<parm name="LauncherSettingsControl" value="
{"blockedApplications":"false",
"deviceDetails":"false",
"aboutLauncher":"false",
"userInformation":"false",
"reloadProfile":"false",
"syncHub":"false"}"/>
</characteristic>
Set the value to false to hide the item from Launcher Settings.
Hide the “For You” Page from Launcher
Admins can now hide the “For You” page entry point from Launcher. For organizations that are not using the “For You” experience, this provides more Home screen real estate and limits access to a part of the application that is not part of the user workflow.
Example: Hide the “For You” button
<characteristic type="com.airwatch.android.androidwork.launcher"
uuid="568bc89d-1df8-4cc9-a841-e5a24aac54321">
<parm name="HideForYouButton" value="
{"hide":"true","staging":"true"}"/>
</characteristic>
Optional Logout on Device Reboot
Admins can now configure Launcher to log out the current user when the device reboots instead of keeping the session suspended. This helps improve security for shared device deployments.
This feature is configured using the existing InActivityTimer custom XML in the Launcher profile. There is no separate feature flag. The custom XML itself acts as the toggle.
Example: Logout on reboot (Device Sleep trigger, 10 min timeout)
Use this example to force logout when the device sleep/reboot trigger occurs.
<characteristic type="com.airwatch.android.androidwork.launcher">
<parm name="InActivityTimer" value="{
"InActivityType" : 1,
"InActivityAction" : 2,
"InActivityTimeout" : 10
}"/>
</characteristic>
Example 2 — Logout on reboot (User Interaction trigger, 10 min timeout)
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="<your-uuid>">
<parm name="InActivityTimer" value="{
"InActivityType" : 2,
"InActivityAction" : 2,
"InActivityTimeout" : 10
}"/>
</characteristic>
| Parameter | Value | Description |
|---|---|---|
| InActivityType | 1 = Device Sleep, 2 = User Interaction | Defines what triggers the inactivity behavior |
| InActivityAction | 2 = Logout | Forces logout instead of session suspension |
| InActivityTimeout | Integer, in minutes | Defines how long before the inactivity action is triggered |
Hide the “For You” Button from Launcher
Admins can hide the For You button from Launcher using the HideForYouButton custom XML setting.This is useful for organizations that are not using the For You experience and want to simplify the Launcher UI or reclaim space on the Launcher screen.
-
Hide = Use "true" to hide the button or "false" to keep it visible.
-
Staging: Controls when the hide takes effect.
<parm name="HideForYouButton" value='{"hide":"true","staging":"true"}'/>
How to configure common scenarios:
| Goal | Config |
|---|---|
| Hide on pre-login/CICO screens only | {"hide":"true","staging":"true"} |
| Hide on all post-login screens only | {"hide":"true","staging":"false"} |
| Hide everywhere | Set both configs-One with staging=true and one with staging=false (must be configured separately) |
| Show everywhere (default) | Remove the config, or set {"hide":"false", ...} |
Hide the “Log Off” Button in Launcher Settings
Admins can now hide the “Log Off” button from Launcher Settings.
This is useful for organizations using third-party login and logout workflows, such as Imprivata MDA, where exposing a separate Launcher logout option could disrupt the intended workflow or cause failures in the third-party application flow.
Example: Hide the Log Off button
<characteristic type="com.airwatch.android.androidwork.launcher"
uuid="568bc89d-1df8-4cc9-a841-e5a24aac54321">
Extended App Data Clear Triggers
Launcher can now automatically clear application data at multiple points in the device lifecycle. To prevent sensitive data from persisting between users on shared devices, administrators can configure automatic data clearing when:
- The device unlocks
- The device reboots
- The device connects to power
This ensures each user session starts with a clean slate in shared device environments.
To turn on this feature:
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="LauncherEventActions" value=" {
"LauncherEventActions": {
"DeviceUnlock": ["ClearAppData"],
"DeviceReboot": ["ClearAppData"],
"PowerConnection": ["ClearAppData"]
}
}"/>
</characteristic>
To turn off this feature:
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="c91f8b32-7d44-4f7a-9c12-0f1d92a6b781">
<parm name="LauncherEventActions" value= "False"/>
</characteristic>
Configurable Header Font Size
Administrators can now configure the Launcher header (title bar) font size to improve readability across different device sizes and operational environments.
Supported font size options include (not case-sensitive):
- EXTRA_SMALL
- SMALL
- MEDIUM
- LARGE
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24ac54321">
<parm name="TitleBarTextSize" value="MEDIUM"/>
</characteristic>
Quick PIN Re-Authentication for Shared Devices
Shared device deployments now support PIN unlock for inactivity timeouts. When a device locks due to inactivity, users can quickly unlock it using their PIN instead of completing a full sign-in. This streamlines workflows in frontline environments where workers frequently step away from shared devices.
With no packages to be allowed on Inactivity screen
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc09d-1df8-4kl9-a041-e5a24acdb7ec">
<parm name="PinLock" value="{"PinLock":{"allowedPackages":" "}}"/>
</characteristic>
When certain app packages are required to be allowed in Inactivity Screen
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc09d-1df8-4kl9-a041-e5a24acdb7ec">
<parm name="PinLock" value="{"PinLock":{"allowedPackages":"com.google.android.contacts,com.google.android.gms,com.example.myapp "}}"/>
</characteristic>
Block Specific Activities Within Allowed Apps
Use this to block access to specific activities inside apps that are otherwise allowed in Launcher.
Note: Use with caution. Incorrect activity blocking may break core app functionality or user workflows.
<characteristic uuid="0e05cccf-0fd3-4eee-9fd7-622c1228c778" type="com.airwatch.android.androidwork.launcher">
<parm name="DeniedActivities" value="{"DeniedActivities": [{"pName": "com.example.calendarapplication","cName": "com.example.calendarapplication.MainActivity"}, {"pName": "com.android.chrome","cName": "org.chromium.chrome.browser.ChromeTabbedActivity"}]}"/>
</characteristic>
Available from Workspace ONE Launcher 25.05 or later.
Admin-Controlled Notification Sounds for Apps
Admins can now assign fully customizable notification sounds to specific apps on supported devices. This allows organizations to standardize distinct sounds for high-priority or time-sensitive notifications, making it easier for users to recognize and respond accordingly. The chosen sound is entirely up to the admin and can vary across teams or workflows, ensuring alignment with organizational needs.
For each supported app (identified by package name), admins can define one or more sound titles in priority order. If the first sound is unavailable on the device (e.g., due to OEM differences in system tones), Launcher automatically falls back to the next sound in the list.
Note: This feature is available in Workspace ONE Launcher 24.05 or later.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="NotificationCustomSound" value="{
"NotificationCustomSound": [
{
"packageName": "com.android.notify1",
"soundTitle": "test1, Sticky, Cosmic Radio"
},
{
"packageName": "com.android.notify2",
"soundTitle": "Beat Box Android, Crystal, Coin1"
},
{
"packageName": "com.whatsapp",
"soundTitle": "Aldebaran, Cosmic Radio, Coconuts"
},
{
"packageName": "com.google.android.gm",
"soundTitle": "Wobble, Xenon, End Note"
},
{
"packageName": "com.Slack",
"soundTitle": "Thallium, Crystal, Duet"
}
]
}"/>
</characteristic>
Show Launcher Bluetooth Setting
In some devices, user can enter application settings while the Bluetooth setting is activated (eg. Samsung phones). To prevent this Admin can use this custom XML. If this is passed, Launcher will show its own Bluetooth setting instead of the native one. In this, the user can only turn Bluetooth on/off, make the device visible, pair, connect and disconnect from other devices.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="ShowLauncherBluetoothSetting" value="True"/>
</characteristic>
Font Size Adjustment Support
This custom XML allows you to adjust device level font size using Display Setting within Launcher. There are a few things to note with this feature:
-
To enable the Font setting option under Launcher Settings, you must also enable the Display Settings. This is because the Font option is available within the Display Settings section of the Launcher.
-
You should configure the grid layout to 4×4 to ensure proper display when the font scale is set to "Largest." This prevents the launcher canvas from becoming disoriented or misaligned due to increased text size.
Use the following custom XML to implement this feature:
<characteristic uuid="0e05cccf-0fd3-4eee-9fd7-622c1228c778" type="com.airwatch.android.androidwork.launcher"> <parm name="FontSetting" value="True"/> </characteristic>
NoteAvailable with Launcher 25.05 for Android.
Enhanced Section Labels for Multi-App Canvas
This custom XML allows for further customization of section label in multi-app canvas for better user visibility and grouping.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec"> <parm name="SectionDetails" value="{"SectionDetails": [ {"textColor": "#FFFFFF","backgroundColor": "#F377F7","textSize": "12","textPosition": "0"}, {"textColor": "#FFFF12","backgroundColor": "#FE993E","textSize": "5","textPosition": "2"} ]}"/> </characteristic>
Available from Workspace ONE Launcher 25.05 or later.
Logout Notification Sound Control
By default, the notification posted plays sound on every lock and unlock. If you wants to suppress the sound of notification admin can implement this XML to mute the sound.
<characteristic uuid="0e05cccf-0fd3-4eee-9fd7-622c1228c778" type="com.airwatch.android.androidwork.launcher">
<parm name="LogoutSharedDeviceNotificationFeature" value="{"enableFeature":true,"titleText":"Title Text changed_6","contentText":"Body Text","logoutText":"Logout Button Text","suppressSound":true}
"/>
</characteristic>
Available from Workspace ONE Launcher 25.05 or later.
Toggle Between Light and Dark Mode
Empower your users with the flexibility to choose their preferred display mode. This feature allows end users to toggle between Dark Mode and Light Mode directly from the Launcher menu, enhancing accessibility and personal comfort—especially for those with visual preferences or impairments.
<characteristic uuid="0e05cccf-0fd3-4eee-9fd7-622c1228c778" type="com.airwatch.android.androidwork.launcher"> <parm name="EnableUserThemeChange" value="True"/> </characteristic>
Available from Workspace ONE Launcher 25.02 or later.
Admin Mode Auto-Timeout for Elevated Security
Admin Mode now features an automatic timeout, seamlessly transitioning back to user mode to safeguard against unauthorized privileged actions and enhance device security.
Note: This feature applies to all Launcher modes (shared device, guest, vendor, single app, and offline modes). The timer value is measured in minutes, and it is recommended to configure this setting at the organization level rather than the user level for optimal management.
<characteristic uuid="0e05cccf-0fd3-4eee-9fd7-622c1228c778" type="com.airwatch.android.androidwork.launcher">
<parm name="AutoExitAdminMode" value="1"/>
</characteristic>
Available from Workspace ONE Launcher 24.11 or later.
Enhanced Navigation with Bottom Bar on Launcher Canvas
This update ensures navigation buttons (back, home, recent apps) remain clearly visible, even against background images, by adding a consistent polished background color.
Note: Since the navigation bar color parameter is not supported in the DDUI profile (UEM), customers currently using the DDUI profile for branding will need to transition. To apply the new navigation bar color, the DDUI profile should be updated by removing it and incorporating the new XML configuration into the custom settings profile.
<characteristic uuid="0e05cccf-0fd3-4eee-9fd7-622c1228c778" type="com.airwatch.android.androidwork.launcher">
<parm name="AllowBranding" value="{"titleColor":"#FF0000","titleTextColor":"#FF0000","accentColor":"#FF0000","highlightColor":"#FF0000","statusBarColor":"#FF0000","navigationBarColor":"#FF0000"}" />
</characteristic>
Available from Workspace ONE Launcher 24.11 or later.
Honeywell Autorotate Configuration
This configuration on Honeywell devices turns off screen rotation upon exiting the Launcher application.
<characteristic uuid="0e05cccf-0fd3-4eee-9fd7-622c1228c778" type="com.airwatch.android.androidwork.launcher"> <parm name="DisableAutoRotationOnExit" value="True"/> </characteristic>
Available from Workspace ONE Launcher 24.08 or later.
Custom Device Settings During Device Check-In
Ability to configure the following device settings while device is checked in:
- Notification Settings
- Date & Time Settings
- Wi-Fi Settings
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb167"> <parm name="StagingCustomSettings" value="{"CustomSettings":[{"name":"STAGE_LANG_SETTINGS","pName":"com.android.settings","cName":"com.android.settings.Settings$LanguageAndInputSettingsActivity"}, {"name":"STAGE_DISP SETTING","action":"android.settings.DISPLAY_SETTINGS"}]}" /> </characteristic>
Note: Custom Settings need to be assigned to the Staging User.
Available from Workspace ONE Launcher 24.08 or later.
Shared Device Notification & Logout Action from Lock Screen
Ability to see the logged in user and log them out from Lock Screen
<characteristic uuid="0e05cccf-0fd3-4eee-9fd7-622c1228c778" type="com.airwatch.android.androidwork.launcher"> <parm name="LogoutSharedDeviceNotificationFeature" value="{"enableFeature":true,"titleText":"Title Text","contentText":"Body Text","logoutText":"Logout Button Text"} "/> </characteristic>
Note: To ensure proper functionality of this feature, it is essential that Keyguard is activated. For optimal performance, we also recommend enabling the status bar and notification panel.
Available from Workspace ONE Launcher 24.08+
Admin Ability to Customize Verbiage on Device Passcode Screen
Ability to customize the verbiage on the device passcode screen"
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-113424ce9-a041-e5a623acdb957"> <parm name="ConfigureLauncherViewProperties" value="{"require_passcode_screen": [{ "resourceId":"change_passcode_text","text":"Passcode Text"}, { "resourceId":"change_passcode_button","text":"Passcode button Text", "textColor":"#00FF00"} ]}" /> </characteristic>
Available from Workspace ONE Launcher 24.08+
Dynamic App Availability
The Dynamic App Availability features gives you enhanced control over application visibility within the Launcher Canvas.
-
Configurable Timeout: Admins can now set a timeout period. Once this period elapses without an application being downloaded or available, the application will automatically be removed from the Launcher Canvas and relocated to an 'unlisted applications' menu within the Launcher settings pane.
-
Automatic Restoration: Should the applications become available again, they will seamlessly reappear on the canvas during profile pushes, reloads, refreshes, check-ins, and client upgrades.
Note: If another application occupies the space on the canvas previously held by a removed application (even if the latter is downloaded), the removed application will not return to its original position. For example, if an application is removed due to unavailability, and a user manually fills its space with another application, the original application will not return to the canvas upon being downloaded.
<characteristic uuid="0e05cccf-0fd3-4eee-9fd7-622c1228c778" type="com.airwatch.android.androidwork.launcher"> <parm name="GhostAppFeature" value="{"timeOutInSeconds":15,"showSettingsMenuOption":true}"/> </characteristic>
Note: This feature is available in Workspace ONE Launcher 24.05 or later.
Speed Lock
Speed Lock is designed to prioritize safety and convenience for users on the move and restricts device usage while in motion.
Some of the features include:
-
Canvas Application Addition on the Go: Uers can add applications to the canvas even while the device is in motion. This flexibility ensures seamless access to essential tools without compromising safety.
-
Autolaunch Capability: Launcher can autolaunch applications, such as maps, to further enhance user safety during device usage. This feature streamlines access to critical functionalities while minimizing distractions.
Important: If you previously configured Speed Lock through DDUI (UEM Profile), you have to remove that profile and transition to Custom Settings to access these new capabilities with no interruption of functionality.
<characteristic uuid="0e05cccf-0fd3-4eee-9fd7-622c1228c778" type="com.airwatch.android.androidwork.launcher">
<parm name="SpeedLockdownSettings" value="{"speed":"4", "unit":"0"
, "timeThreshold":"10"
, "troubleshootPasscode":"1234"
, "headerText":"Too Fast"
, "messageText":"Stop to unlock"
, "listOfApplications":"com.android.chrome
,com.google.android.gm","launchAppOnStartup":"com.example.multiapp1"
,"durationToMoveToSpeedLockCanvas":10}" />
</characteristic>
| Setting | Description |
|---|---|
| Speed | The speed above which a device will get locked. |
| Time Threshold | If the vehicle speed is below the configured speed limit for the timeThreshold seconds, then the user will come out of speed lock mode. |
| Troubleshoot Passcode | In case the speed API is giving the wrong result, the user can come out of speed lock mode using the troubleshoot passcode. |
| Duration to move to Speed Lock Canvas | Set the duration that the older speed lock screen, which features a car icon, will appear for a default duration of 5 seconds. After this period, the screen transitions to the speed lock canvas screen. |
A few things to consider when using this feature:
- You can pin multiple applications to the canvas simultaneously. Simply use the BundleID of the application followed by the parameter 'listOfApplications' to add or remove as many activities as desired.
- For getting the location accuracy we use Google's API com.google.android.gms.location.LocationListener.
This feature is available in Workspace ONE Launcher 24.05 or later.
Unpair Bluetooth Device on Check-in
This configuration will unpair any previously connected Bluetooth devices. This is especially targeted for CICO, where users may connect their individual Bluetooth peripherals.
Available in Workspace ONE Launcher 24.02 or later.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb704">
<parm name="UnpairBluetoothDevices" value="True"/>
</characteristic>
Ability to Control Device Brightness via Launcher
This allows seamless control on setting the device's brightness level. You can configure the 'DisplayBrightnessLevel' attribute to tweak the brightness. (For example, '25' or '75', for 25% or 75%).
Available in Workspace ONE Launcher 24.02 or later
Note: This feature does require an additional permission android.permission.WRITE_SETTINGS'. Granting this permission requires manual interaction on the device and CANNOT be granted silently/
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb785">
<parm name="SetDeviceBrightness" value="True" />
<parm name="DeviceBrightnessLevel" value="15" />
</characteristic>
Configure Waiting for Profile Screen
When there is a delay in receiving the Launcher Profile or if the Launcher profile itself is not assigned then the device will go to Waiting for profile Screen. This Custom XML can be used to provide a descriptive text to the user in the form of a dialog.
This Custom settings should be assigned to the set of Users to whom the Launcher Profile is not assigned.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ed">
<parm name="NoLauncherProfileAssigned" value="True"/>
</characteristic>
To customize the content shown in cases where the profile is assigned to the end user but a delay is observed in receiving the profile, then the admin can use the below custom XML.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ed">
<parm name="ConfigureLauncherViewProperties" value=
"{"waiting_for_profile_screen":
[
{ "resourceId":"waiting_for_profile_info_text","text":"Test123"}]}"/>
Block Access to Launcher until Tunnel is Ready
This feature allows a splash screen to block access to the device until Tunnel ready-state is received. This ensures a user cannot access applications or device until Tunnel is established.
Available in Workspace ONE Launcher 23.11 or later
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7098">
<parm name="WaitForTunnelConfigurationCompletion" value="True"/>
</characteristic>
Show 'Logout' bar on in Guest/Vendor Mode
This allows for a prominent bar to appear that informs the user if they are in Guest or Vendor Mode.
Available in Workspace ONE Launcher 23.11 or later.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb752">
<parm name="ShowLogoutButtonOnHomeScreen" value="True"/>
</characteristic>
Hotswap Enhancement to Stop Multiple Refreshes
Adding this configuration ensures that when Hotswap is configured, the device does not refresh multiple times after showing Launcher Canvas
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb752">
<parm name="CacheProfile" value="True"/>
</characteristic>
Enable Edge Panel on Samsung Devices
This enables Edge Panel on Samsung Devices.
Available in Workspace ONE Launcher 23.11 or later
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb752">
<parm name="EnableEdgePanel" value="True"/>
</characteristic>
Restrict Self Launch on Package Update
In Single app mode, whenever an app is upgraded, on the package update event, the launcher starts itself. If the admin wants to control the self-launch on package update then the below XML can be configured.
Available in Workspace ONE Launcher 23.04 or later
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ed">
<parm name="RestrictSelfLaunchOnSingleAppModePackageUpdate" value="True"/> </characteristic>
ByPass Battery optimization
This configuration allows admin to bypass the battery optimization which would allow the launcher to run in the background process to run even when the app is in Doze mode. Available in Workspace ONE Launcher 23.04 or later
Recommended, assigning this custom setting to the OG Level so that all the devices under the OG will get this custom setting. This is a one-time operation when the app run for the first time.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ed">
<parm name="BypassBatteryOptimizationPermission" value="True"/> </characteristic>
All File Access Permission
Launcher requires the file access permission to access the external storage.
Available in Workspace ONE Launcher 23.08 or later
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ed">
<parm name="AllFileAccessPermissionForLauncher" value="True"/> </characteristic>
Allow Split-window Mode Inside Launcher
Split-screen mode fills the screen with two apps, showing them either side by side or one above the other. Configure the below custom setting to allow end users to open apps in split-window mode. By default, this feature is disabled.
Admin has to note that if we allow split-window then on Samsung devices users can open any app in the pop-up view. Launcher will not be able to block the pop-up view if we use the below custom XML.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="548bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="AllowMultiWindowMode" value="True"/>
</characteristic>
Restart Device Setting
If you want to let users restart Launcher, enable this setting. By default, the "Restart Launcher" is not available to end users.
To enable this settings, use the following XML code:
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="548bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="EnableDeviceRestartLauncherSetting" value="True"/>
</characteristic>
Use Settings Wi-Fi Action
On some tablets, the Action WifiManager.ACTION_PICK_WIFI_NETWORK is not working correctly. To resolve this problem, use this custom XML to force Launcher to uses Settings.ACTION_WIFI_SETTINGS.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="UseSettingsWifiAction" value="True"/>
</characteristic>
Add Hub To Force Stop Blacklist
On some Samsung devices, Workspace ONE Intelligent Hub was force stopping resulting in Workspace ONE Launcher not getting focus monitor broadcasts. Launcher needs these broadcasts to block applications. Use this custom XML to add Workspace ONE Intelligent Hub to the force stop blacklist:
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name=" AddHubToForceStopBlacklist" value="true"/>
</characteristic>
Hide Settings Option from Single App Floating Action Button
Available in Workspace ONE Launcher 21.10+
The new single app floating button presents quick access to settings, the Launcher menu, and the logout button. To hide the settings button from the expanded menu, use the following custom XML:
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="HideSingleAppSettingsFab" value="True"/>
</characteristic>
Override the duration that Launcher shows the Clearing Data Screen
Available in Workspace ONE Launcher 21.10+
Launcher shows the clearing data screen while queuing the commands to clear app data. To override the duration that Launcher shows this screen, use the following XML. This may be desired to ensure any asynchronous tasks like profile removal is completed before the next user checks out the device.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="ClearAppWaitTimeout" value="10"/>
</characteristic>
This is also supported on iOS, but the configuration is found in the custom SDK settings in UEM. The configuration to be used should be:
{
"ClearAppWaitTimeout":10
}
Turn on
Dark Mode
Available in Workspace ONE Launcher 21.09 or later
Enable Launcher's dark mode to apply Launcher's dark theme and change the home screen icons and labels to white.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="EnableDarkTheme" value="True"/>
</characteristic>
Turn off Launcher's Search Bar
Available in Workspace ONE Launcher 21.09 or later
Hide Launcher's search bar. The search bar allows users to search for applications on the home screen across pages and folders.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="DisableSearch" value="True"/>
</characteristic>
Turn on Flashlight
Available in Workspace ONE Launcher 21.09 or later
Add the flashlight toggle to the quick access section in the Launcher menu.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="AllowFlashlight" value="True"/>
</characteristic>
FocusMonitoring API
Available in Workspace ONE Launcher 4.9 or later
On Samsung devices, Launcher defaults to using the Samsung Focus Monitoring API. This allows Launcher to automatically foreground applications without the user having to grant the Android Usage Access Permission. The admin can disable this feature using the following custom XML. Disabling this feature on Samsung devices will require users to grant the usage access permission on the first launch of Launcher.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="DisableFocusMonitoring" value="True"/>
</characteristic>
Show Popup Notifications
Available in Workspace ONE Launcher 4.8 or later
Admins can generate popup notifications regardless of channel priority using this custom XML. To show popups, the notification bar cannot be disabled. Admins can create popups regardless of how the app sending the notification prioritizes its notification channel.
After Android O, popups will only show if the app sending the notification sets a notification channel to show popups, but this custom XML bypasses that behavior.
For generating popups for all allowed apps:
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="ShowPopupNotification" value="True"/>
</characteristic>
For generating popups for specific apps:
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="ShowPopupNotification" value="com.application1.package, com.application2.package"/>
</characteristic>
Hide Enable Notifications Button
Available in Workspace ONE Launcher 4.8 or later
Admins can hide the “Enable Notifications” button from the Launcher dropdown menu by using the following custom XML.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="AllowEnableNotification" value="False"/>
</characteristic>
Disable Sensor Orientation
Available in Workspace ONE Launcher 4.8 or later
Use this setting to prevent the device from switching to reverse portrait mode or reverse landscape orientation. To ensure this permission has been granted, admins can push the prompt write setting permission custom XML.
This feature requires the write settings permission to set orientation device-wide.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="DisableSensorOrientation" value="True"/>
</characteristic>
Speed Lockdown
Available in Workspace ONE Launcher 4.7 or later
Use this custom XML to block device access when exceeding a specified speed threshold.
<parm name="SpeedLockdownSettings" value="{"speed":"20", "unit":"0", "timeThreshold":"10000", "troubleshootPasscode":"1234", "headerText":"Too Fast", "messageText":"Stop to unlock"}" />
The default values are as followed:
- Unit = 1 (m/h)
- TimeThreshold = 5000 (5 seconds)
- HeaderText = "Device Locked"
- MessageText = "Come to a complete stop to unlock device"
The accepted values are as followed:
-
Speed > 0
-
Unit = 0 - km/h , 1 - m/h (default = m/h)
-
TimeTheshold > 0 (in milliseconds)
-
TroubleshootPasscode (length > 0)
-
HeaderText (length > 0 chars < 15 chars)
-
MessageText (length > 0 chars < 30 chars)
Write Settings Permission
Available in Workspace ONE Launcher 4.6 or later
Use this custom XML to show the "Write Settings Permission" prompt during initial setup. Note, the write settings permission allows users to modify settings you give access to. This permission is already required for screen orientation lock changes to take effect device-wide. By default, the write settings permission is requested when a user attempts to modify settings.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="WriteSecurePermissionSettings" value="True"/>
</characteristic>
Skip overlay Permission Screen
Use this custom XML to hide the 'Draw over other apps permission" prompt during initial setup. Note, the draw over permission is required for adding overlays and restricting apps. Using Launcher without the Draw over permission (or Appear on Top permission) could turn off Launcher's ability to block restricted applications and features. Note Overlays like floating buttons and popup notifications will not work without Draw Over Other apps permission.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="SkipOverlayPermissionScreen" value="True"/>
</characteristic>
For Android 10 and later, it is not recommended to use this setting because the Android framework makes this permission as a mandatory permission if an app is required to launch from background. To block the denied list of applications, Launcher needs this permission to launch itself from the background and pin itself to Foregroud to not allow the denied list of apps. Without this permission, Launcher would be unable to block the denied list of apps.
Actionbar Settings
Available in Workspace ONE Launcher 4.6 or later
Actionbar Settings
You can customize the CICO action bar's behavior by using the following custom XML.
- If you would like to retain the value of the action bar title from the previous user, set the retainChildTitle parameter to True. Note, retaining the child title will also retain calculated lookup values from the previous user.
- The defaultTitle parameter defines the title value for when no previous user has yet checked out the device.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="ActionBarSettings" value="{"retainChildTitle":"True", "defaultTitle":"Omnissa - Airwatch"}" />
</characteristic>
Available in Workspace ONE Launcher 4.6 or later
Wallpaper Scale Type
Available in Workspace ONE Launcher 4.5 or later
By default, Launcher stretches the Home Screen wallpaper to fit the different aspect ratios for landscape or portrait. Use the following custom XML to define different wallpaper scale methods for landscape and portrait.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="WallpaperScaleType" value=" {"portraitScaleType":"FIT_CENTER", "landscapeScaleType":"FIT_XY"}"/>
</characteristic>
Staging Admin Passcode
Available in Workspace ONE Launcher 4.4.1 or later
Use this custom XML to enable the admin mode option on the check-in check-out screen. Users can exit the Workspace ONE Launcher from the check-in/check-out screen by entering the password specified in XML. After checkout, the admin passcode will be replaced by the end user profile admin passcode. Assign this custom XML to the staging user:
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="StagingAdminPasscode" value="1234"/>
</characteristic>
Allowlist Activities on Check-in Check-out Screen
Available in Workspace ONE Launcher 4.4 or later
Allow specific activities that Launcher may otherwise block when on the check-in check-out screen (when Launcher is assigned to the staging user). This includes native popups or UI elements. Use the following custom XML by specifying the package name and class name. Assign this custom XML to the staging user.
This feature requires the Appear on Top (Draw Over Other Apps) Permission and Usage Access (or Focus Monitoring on Samsung) Permission.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="AllowStagingActivities" value="{"AllowStagingActivities": [ {"pName": "com.android.settings","cName": "com.android.settings.LanguageSettings"}, {"pName": "com.android.settings","cName": "com.android.settings.WifiPicketActivity"} ]}"/>
</characteristic>
Allow Log Collection
Available in Workspace ONE Launcher 4.4 or later
If admin wants to collect logs for a certain use case or in certain scenarios, use this custom XML and request the debug logs from the Workspace ONE UEM console:
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec"><parm name="AllowLogCollection" value="True"/></characteristic>
Note: From 22.11+ the default value for the custom parameter AllowLogCollection is changed to true so that the logs will be available all the time to upload to UEM. If any customer does not want to auto collect the logging then AllowLogCollection should be sent as False.
Allow Staging Profile
Available in Workspace ONE Launcher 4.2.1 or later
If the customer assigns a single profile to all the users at the parent Organization Group level, then use this custom XML:
<characteristic type="com.airwatch.android.androidwork.launcher"
uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec"><parm name="AllowStagingProfile"
value="True"/></characteristic>
Force Reset Launcher Layout on Profile Update
Available on Workspace ONE Launcher 4.2 or later
Use this custom XML to reset the Launcher Home Screen layout to the admin configured layout with every profile update. By default, Launcher preserves any app rearrangement on the device after profile updates.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="AllowProfileReset" value="True"/>
</characteristic>
Set Launcher as Default after Reboot
Available on Workspace ONE Launcher 4.2 or later
This custom XML allows Workspace ONE Launcher to open and lockdown the device after reboot regardless of the previous state. By default, if Launcher was in admin mode or un-pinned to the Home Screen before the device was rebooted, the device reboots to the default native Launcher. This setting only applies to Honeywell, Zebra and Samsung devices.
In cases where the launcher opens after a delay, the length of time can be defined in seconds in the XML below:
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="AllowLaunchOnReboot" value="5"/>
</characteristic>
Allow Staging Settings
Available in Workspace ONE Launcher 4.1 or later
In Workspace ONE Launcher, the option of toggling Wi-Fi is only available in the staging screen. If a user wants to configure Wi-Fi settings, long press on the Wi-Fi icon to launch the native Wi-Fi settings. Since this setting has to be accessed in the staging screen, the below custom xml must be pushed for the staging user \parent organization group). This can be configured by using below flag.
Enabling access to a specific settings page requires the Appear on Top (Draw Over Other Apps) Permission.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="AllowStagingSettings" value="True"/></characteristic>
Customize Floating Home Button
Available with Workspace ONE Launcher 4.0 or later
Admins can enable Launcher's floating home button to serve as a dedicated home button when the native home button is unavailable. Note, the floating home button only applies to multi-app and template mode.
By default, Launcher running on Android 8 and below devices does not support displaying a home and recent apps button. In this case, Launcher defaults to displaying the floating home button. Note, admins can enable Launcher's legacy methods to re-enable the home and recent apps button (see Enable Launcher's Legacy Methods).
<characteristic
type="com.airwatch.android.androidwork.launcher"
uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec"><parm name="HomeFloatingButtonSetting" value="{"Size":"Small","Color":
"#F377F7","TimeToFade":"5","FadeValue":"3"}"/></characteristic>
Admins can customize the floating home button using this custom XML.
Size: Indicates the size of the Floating Home button. The possible values: Small, Medium, Large.TimetoFade: Indicates the time in seconds for Floating Home button to fade away.Color: Indicates the color of the Floating Home button. color must be specified in a Hex code Eg: #F377F7.FadeValue:Indicates the amount of fading required.
Remove Floating Home Button
Available with Workspace ONE Launcher 4.0 or later
Use the following custom XML to disable the floating home button.
Note, the floating home button serves as an alternative home button when the native home button is unavailable.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="RemoveHomeFloatingButtonSetting" value="True"/></characteristic>
Enable Floating Home Button
Available with Workspace ONE Launcher 4.0 or later
On some devices, the native Android home button may be inaccessible. You can use this custom XML to manually display a floating home button in multi-app mode.
<characteristic type="com.airwatch.android.androidwork.launcher"
uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec"><parm name="AllowHomeFloatingSetting" value="True"/></characteristic>
Customize Single App Floating Action Button
Available with Workspace ONE Launcher 4.0 or later
In Single application mode, Launcher provides a Floating Action button for users to access different launcher settings. This button can be configured by using the below setting:
This feature requires the Appear on Top (Draw Over Other Apps) Permission.
<characteristic
type="com.airwatch.android.androidwork.launcher"
uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec"><parm name="SingleAppFloatingButtonSetting" value="{"Size":"Small","TimeOut":
"2","FixPosition":"true"}"/></characteristic>
Size: Indicates the size of the floating action button. Possible values: Small, Medium, Large.Timeout: Indicates the time in seconds for floating button to fade away. Should be an integer only.FloatingTimeoutValuecustom flag is now deprecated from version 4.0 instead we should use this flag.FixPosition: When enabled, the user cannot move the floating action button. It is positioned at the right end corner. This setting replaces theFixSettingsPositionfrom previous versions.
Allow Localized App Names
Available with Workspace ONE Launcher 4.0 or later
By default, application names in Launcher populate according to the app name set in the console. Use this custom XML to localize app names based on the device's language setting.
<characteristic
type="com.airwatch.android.androidwork.launcher"
uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec"><parm name="AllowLocalizedAppNames" value="True"/></characteristic>
Skip Usage Access Permission
Available with Workspace ONE Launcher 4.0 or later
Admins use Launcher to prevent access to blocked apps and content. To detect which app is in the foreground, Launcher uses the advanced permission, usage access. On initial setup, if Launcher cannot grant the permission on behalf of the user, Launcher prompts the user to manually grant the permission. Some device OEMs require device end users to grant apps with usage access permission on their devices.
Admins can use this custom XML skip the usage access permission prompt. However, by doing so, Launcher may not gain usage access and may not be able to block manage device access.
<characteristic
type="com.airwatch.android.androidwork.launcher"
uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec"><parm name="SkipUsageAccessPermission" value="True"/>
</characteristic>
Use Legacy Launcher Methods (Skip COSU Setup)
Available with Workspace ONE Launcher 4.0 or later
Enabling this feature allows Launcher to use Workspace ONE's legacy methods in place of native Android's lock task APIs for device lockdown. Starting with Launcher 4.0, Launcher uses lock task mode by default to restrict device access.
<characteristic
type="com.airwatch.android.androidwork.launcher"
uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec"><parm name="SkipCosuSetup" value="True"/></characteristic>
Devices running Android 8 and older may have the status bar, home button, and recent tasks button disabled by default while in lock task mode. Other apps on the device may also require control over lock task mode. In these cases, admins can enable Launcher's legacy methods using this custom XML to manage legacy devices or ensure Launcher works correctly with other lock task apps.
Selective App Cache Clearing
Available with Workspace ONE Launcher 3.3 or later
The Workspace ONE UEM console setting labeled "Clear App data on logout" clears the data of all assigned applications after logging out. Admins can specify package IDs to skip clearing by using the following XML:
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
parm name="DonotClearAppDataSet" value="com.airwatch.browser,com.samsung.klmsagent"/>
</characteristic>
Restrict Folder Renaming
Available with Workspace ONE Launcher 3.3 or later
Admins can restrict users from renaming folders by using the following custom XML. By default, Launcher enables users to rename and rearrange the app canvas.
<characteristic type="com.airwatch.android.androidwork.launcher"
uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec"><parm name="DisableFolderRename" value="True"/></characteristic>
Add Custom Device Settings
Available with Workspace ONE Launcher 3.2 or later
Admins can provide access to any native settings menu by defining the package and class name. These settings will populate as a row item in the Launcher settings page.
This feature requires the Appear on Top (Draw Over Other Apps) Permission and Usage Access (or Focus Monitoring on Samsung) Permission.
Required Parameters:
SettingNameto be displayed on Launcher settings screen.PackagenameandclassnameorAction nameof the desired native setting.
Settings activity actions can be found in Android Settings Documentation. Use the Constant Value for the action value.
If only Action is used:
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="CustomSettings" value="
{
"CustomSettings": [
{
"name": "Location Settings",
"action": "android.settings.LOCATION_SOURCE_SETTINGS"
}]
}"/>
</characteristic>
If packageName and class name is used:
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="CustomSettings" value="
{
"CustomSettings": [
{
"name": "Manage Applications Settings",
"pName": "com.android.settings",
"cName": "android.settings.MANAGE_APPLICATIONS_SETTINGS"
}]
}"/>
</characteristic>
For additional information, please see the Android Developer Settings page.
Launcher Branding
Available with Workspace ONE Launcher 3.2 or later
Provides a proper combination of Action Bar color and Status Bar color (Light and dark) as recommended by Google. You may set different colors according to you company’s brand colors .
Auto Branding: If you do not want to specify individual colors you can use this flag. In order for this to work, title bar icon (logo) must be present.The extracted colors for branding are from the company logo.
To enable and implement this feature the below flag must be pushed down through the custom settings payload:
<characteristic type="com.airwatch.android.androidwork.launcher"
uuid="eadfebd8-7f4c-4837-b9dd-dfcf31bd84e6">
<parm name="AllowAutoBranding"
value="true" />
</characteristic>
To personalize, then you can specify the title bar color, title text color, primary accent color, status bar color, and highlight color. Colors must be specified in hexadecimal color format:
<characteristic type="com.airwatch.android.androidwork.launcher"
uuid="eadfebd8-7f4c-4837-b9dd-dfcf31bd84e6"><parm name="AllowBranding"
value="
{"titleColor":"#FC002E","titleTextColor":
"#F377F7","accentColor":"#36E712","highlightColor":"#4E993E","statusBarColor":"#FC002E"}"/>
</characteristic>
Allowlist Specific App Activities
Available with Workspace ONE Launcher 3.2 or later
Allow specific app activities to come to the foreground that Launcher may otherwise block. This includes native popups or UI elements. Use the following custom XML by specifying the package name and class name.
This feature requires the Appear on Top (Draw Over Other Apps) Permission and Usage Access (or Focus Monitoring on Samsung) Permission.
Note: The activity names in Android are case sensitve.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="CustomActivities" value="
{
"CustomActivities": [
{
"pName": "com.android.settings",
"cName": "com.android.settings.localepicker.LocalePickerWithRegionActivity"
},
{
"pName": "com.android.settings",
"cName": "com.android.settings.Settings$WifiNetworkDetailsActivity"
}]
}"/>
</characteristic>
Remove Welcome Screen
Available with Workspace ONE Launcher 3.2 or later
In older versions, Launcher displays a welcome screen when it is pushed to the device. This can be removed by clicking the “Dismiss” (Cancel) button on the right lower corner. The below flag can be used to remove the Welcome screen.
<characteristic type="com.airwatch.android.androidwork.launcher"
uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="RemoveWelcomeScreen"
value="True"/>
</characteristic>
Inactivity Timer
Available with Workspace ONE Launcher 3.2 or later
Admins can specify an amount of time in which the device will automatically lock the Launcher screen and require the previously signed in user to re-enter their password to re-access the Launcher screen. Instead of relying on the user to manually lock their device session when not in use, you can specify how much idle time is allowed before the device automatically locks. You can specify a list of apps to run in the foreground while the device is locked.
If a new user wants to unlock a device that is locked into another users account, they can log out the previous user and sign in as themselves.
Note: Inactivity Timer is compatible with Workspace ONE Access authntication from Launcher versions 25.10+ and Workspace ONE Intelligent Hub 25.10+ for Android.
To enable and implement this feature, the setting must be pushed down through the custom settings payload:
<characteristic type="com.airwatch.android.androidwork.launcher"
uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="InActivityLock"
value="True"/>
</characteristic>
Admins can also specify a list of apps that can run in the foreground while the inactivity lock is enabled. (Requires 21.09 or later)
<characteristic type=“com.airwatch.android.androidwork.launcher” uuid=“568bc89d-1df8-4ce9-a041-e5a24acdb7ec”>
<parm name=“InActivityLock” value=“com.android.chrome,com.demo.application”/>
</characteristic>
Admins can specify the timeout value in minutes using the following extra parameter.
<characteristic type="com.airwatch.android.androidwork.launcher"
uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="InActivityLock"
value="True"/>
<parm name="InActivityTimeout"
value="10"/>
</characteristic>
This setting is not to be confused with the Auto Logout security setting which can be turned on to log out a user from a device after the specified time.
Inactivity Timer in Guest and Vendor Mode
This extends the use of Inactivity Timer from regular Check-in Check-Out to Guest and Vendor Mode.
Available in Workspace ONE Launcher 23.11 or later.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="InActivityLock" value="True"/>
<parm name="InActivityTimeout" value="10"/>
</characteristic>
Inactivity Timeout Enforcement (Launcher 24.11 and later)
Starting with Launcher 24.11, you can set up an inactivity timeout to help keep your device secure. That means if users stop interacting with the device for a set amount of time, the device can automatically go to sleep. When the timeout is reached, users are required to reauthenticate or logout depending on the security settings.
This behavior depends on the value set for InActivityAction in the custom XML:
- 1 = Reauthenticate
- 2 = Log out
To make this work, Launcher needs permission to change a system setting on the device. If not already enabled, users will see a prompt on their device asking them to Go to Settings and enable Modify system settings or Change system settings. This permission allows Launcher to control the device's screen timeout settings to enforce your organization's security policies.
This new inactivity setting can also replace the older inactivity settings. You choose how inactivity is measured with the value in the InactivityType field:
- InActivityType = 1 (legacy method): Launcher measures inactivity based on how long the screen stays off. It checks the time between the screen turning off and turning back on, and compares that to the configured InActivityTimeout value.
- InActivityType = 2 (system timeout method): Launcher sets the device’s system screen timeout to match the configured InActivityTimeout value. This requires the Modify system settings permission to be granted to Launcher. Once enabled, Android will automatically turn off the screen after that amount of time.
Allowed apps after reauthentication
You can choose which apps are still accessible when the inactivity sign-in screen appears. This is controlled by the value in the InActivityAllowedPackages field, and it works with both inactivity modes.
Custom XML for Inactivity action based on screen timeout with re-authentication action
Note: Change the values based on your organization's requirements.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="5628b3c839e-31d324a23-1452-1a310241-e5a24act3dbr7">
<parm name="InActivityTimer" value="{
"InActivityType" : 2,
"InActivityAction" : 1,
"InActivityTimeout" : Time in minutes after which the InActivityAction must be enforced,
"InActivityAllowedPackages" : "com.android.chrome,com.boxer.email"
}"/>
</characteristic>
Inactivity custom XML based on screen timeout with logout action
Note: Change the values based on your organization's requirements.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="5628b3c839e-31d324a23-1452-1a310241-e5a24act3dbr7">
<parm name="InActivityTimer" value="{
"InActivityType" : 2,
"InActivityAction" : 2,
"InActivityTimeout" : Time in minutes after which the InActivityAction must be enforced,
"InActivityAllowedPackages" : "com.android.chrome,com.boxer.email"
}"/>
</characteristic>
Inactivity custom XML based on legacy inactivity calculation with re-authentication action
Note: Change the values based on your organization's requirements.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="5628b3c839e-31d324a23-1452-1a310241-e5a24act3dbr7">
<parm name="InActivityTimer" value="{
"InActivityType" : 1,
"InActivityAction" : 1,
"InActivityTimeout" : 5,
"InActivityAllowedPackages" : "com.android.chrome,com.boxer.email"
}"/>
</characteristic>
Inactivity custom XML based on legacy inactivity calculation with logout action
Note: Change the values based on your organization's requirements.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="5628b3c839e-31d324a23-1452-1a310241-e5a24act3dbr7">
<parm name="InActivityTimer" value="{
"InActivityType" : 1,
"InActivityAction" : 2,
"InActivityTimeout" : 5,
"InActivityAllowedPackages" : "com.android.chrome,com.boxer.email"
}"/>
</characteristic>
Hot Swap Profile Caching:
Available with Workspace ONE Launcher 3.2 or later
As check in/check out is done frequently, users often check out the same device but have to wait for a considerable amount of time for the profile to get applied after checking out. Workspace ONE can expedite this by caching profile per user when the user checks out that particular device for the first time.
Note, user profile caching is only supported via UEM basic user authentication.
To enable and implement this feature, the setting must be pushed down through the custom settings payload:
<characteristic type="com.airwatch.android.androidwork.launcher"
uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="CacheProfile"
value="True"/>
</characteristic>
Allow WebView inside Launcher:
Available with Workspace ONE Launcher 3.2 or later
Launcher's built in web view is disabled by default, requiring a browser to be installed and allowed to open web bookmarks. Admins can enable the built-in browser using the following custom XML.
<characteristic type="com.airwatch.android.androidwork.launcher"
uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="AllowBuiltInBrowser"
value="True"/>
</characteristic>
Dynamically add shortcuts to Launcher screen:
Available with Workspace ONE Launcher 3.2 or later
Admins can display a shortcut to an app activity on Launcher's home screen by using the below flag by specifying the "shortcut name, package name, activity name" or "shortcut name, action name".
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="CustomShortcuts" value="{"CustomShortcuts":
[{"name":" Manage Applications Settings","pName":"com.android.settings","cName":
"com.android.settings.Settings$DateTimeSettingsActivity"},
{"name": "Locale Settings","pName":
"com.android.settings","cName": "com.android.settings.Settings$LocalePickerActivity"}]}"/>
</characteristic>
Open Native settings in tablets:
Available with Workspace ONE Launcher 3.2 or later
In some of the tablets, native settings such as Wi-Fi, Bluetooth, Language etc. are opened in a fragmented view which allows users to access other settings as well, in such a case user can easily get out of launcher. So, by default, Launcher does not allow users to open settings unless they use the below flag. If the admin thinks that it is safe to open native settings in that particular tablet then he can use this flag and all the native settings which are allowed can be accessed. This is usually used along with dynamically allowed list settings flag (CustomSettings), custom shortcuts, custom activities and for notification access.
<characteristic type="com.airwatch.android.androidwork.launcher"
uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="CanLaunchNativeSettings"
value="True"/>
</characteristic>
If you on want a particular native setting to be accessed and not other settings, use the flag: forceLaunch. This flag is used individually with each setting. If admin uses the flag: canLaunchNativeSettings,then all the allowed native settings can be accessed. If you want a particular setting, use the forceLaunch flag. This is usually used along with dynamically allow list setting flag (CustomSettings), custom shortcuts, custom activities and for notification access.
<characteristic type="com.airwatch.android.androidwork.launcher"
uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="CustomShortcuts"
value="{"CustomShortcuts": [
{"name": "Manage Applications
Settings","forceLaunch": "true","pName":
"com.android.settings","cName":
"com.android.settings.Settings$DateTimeSettingsActivity"},
{"name":
"Locale Settings","pName":
"com.android.settings","cName":
"com.android.settings.Settings$LocalePickerActivity"}
]}"/></characteristic>
In the above XML (Customshortcuts) both Manage Applications and Locale Settings shortcuts will be visible on the Launcher screen, but users can only access Manage Application settings since it uses the forceLaunch flag.
The flagsforceLaunch or canLaunchNativeSettings must be present for custom settings to be visible on Launcher settings screen.
Clear Application Defaults
Available with Workspace ONE Launcher 3.2 or later
When opening a media file, Android presents a dialog with all the applications which support that particular format. If an end-user chooses an application as the default application, then files of the same media type are opened by this default application. Admins can configure Launcher to clear application defaults on session check-ins.
This API is only supported by certain OEMs. We recommend testing your use case before deployment.
<characteristic type="com.airwatch.android.androidwork.launcher"
uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="AllowClearAppDefaults"
value="True"/>
</characteristic>
In some devices, Workspace ONE cannot clear application defaults automatically. For those cases, admins can present the user with a prompt to clear application defaults manually. This will navigate the user to a native settings screen to clear the appllication defaults.
<characteristic type="com.airwatch.android.androidwork.launcher"
uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="CannotClearAppDefaults"
value="True"/>
</characteristic>
Boot Up Launchers
Available with Workspace ONE Launcher 3.2 or later
There are some boot up applications which run after the device is restarted. These boot up applications are allowed even though they are listed as not allowed on the console. The UEM console maintains a list of allowed applications in Launcher profile but after reboot Workspace ONE Launcher takes some time to load this profile.
During this loading time, Launcher does not have any knowledge of the allowed apps therefore all applications are opened. To prevent this, users can send the below custom setting flag providing the package name of all the boot up applications which are to be allowed.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="BootupLauncher" value="com.sonyericsson.initialbootsetup, com.sonyericsson.setupwizard,com.honeywell.systemtools.autoinstall/>
</characteristic>
ByPass Battery Optimization
Available with Workspace ONE Launcher 23.04 or later
In order to bypass Doze mode and to run in the background, this custom XML bypasses the battery optimization settings on Android devices. It is recommended to assign this custom XML at the top Organization Group so all the devices assigned to your OG gets this setting.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ed">
<parm name="BypassBatteryOptimizationPermission" value="True"/> </characteristic>
Restrict Self Launch on Single App Mode
Available with Workspace ONE Launcher 23.04 or later
In Single App mode, the Launcher restarts itself whenever an app is updated. If you want to control the self-launch on package update, you can use the following XML:
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ed">
<parm name="RestrictSelfLaunchOnSingleAppModePackageUpdate" value="True"/> </characteristic>
Was this page helpful?