Secure Device Mode

Overview

Secure Device is a Launcher feature that restricts device access to authorized users by requiring a mandatory sign-in. If access is not verified within the configured timeframe, the device triggers an alarm to alert the user.

What Changed in Launcher 4

In Launcher 3, Secure Device settings are configured within the launcher.json "settings" section.

In Launcher 4, these settings are moved to a new "secureDevice" configuration. An added "enable" field improves readability while references to "unsecure" or "secure" are removed from the start of the variables.

Field	Launcher 3 Functionality	Launcher 4 Functionality
Enable secureDevice	N/A	Configured using the enable field (true or false)
Timeout Settings	unsecuredDeviceTimeoutInSecs	timeoutInSecs
Screen Off Timeout	N/A	screenOffTimeoutInSecs
Sound Volume	unsecuredDeviceSoundVolume	soundVolume
Enable Effects	unsecuredDeviceEffects	enableEffects
Effects Sound	unsecuredDeviceEffectsSound	effectsSound
Alarm Sound	unsecuredDeviceAlarmSound	alarmSound
Snooze Duration	secureDeviceSnoozeDuration	snoozeDuration
Max Snooze Count	secureDeviceMaxSnoozeCount	maxSnoozeCount

Admin Guide

1. The Secure Device feature is disabled by default. To enable it, set the enable field to true and ensure the timeoutInSecs field is assigned a value greater than zero; otherwise, the feature will remain enabled.

2. When the enable field is set to true and the timeoutInSecs field has a value greater than zero, a message will appear on the user device stating: "Login is required within 10 s or an alarm will sound."

3. The snooze duration and maximum snooze count can also be configured. By default, these values are set to 120 seconds and 1, respectively.

4. If the user fails to login with an uncradled device within the configured timeout period, the alarm will sound. To stop the alarm, the user must either enter their login credentials or return the device to the cradle.

User Guide

1. If the feature is enabled, the message "Login is required within 10 s or an alarm will sound." will appear on the screen.

1. Enter your login details within the configured timeout period.

1. If you fail to log in with an uncradled device, the device will play a looping alarm.

2. To stop the alarm, you have two options: either log in with your credentials or place the device back in the cradle.

1. Depending on your organization's configuration, you may have the option to snooze the alarm within a specified timeframe.

2. If you are unable to log in and want to prevent the alarm from playing, place the device back in the cradle.

Enabling Secure Device

To enable the feature, set secureDevice to true and assign timeoutInSecs a value greater than zero.

• If secureDevice = true but timeoutInSecs is not set, the feature won't work.

• If timeoutInSecs ＞ 0 but secureDevice = false, the feature won't work.

Additionally, you can include the optional screenOffTimeoutInSecs to specify the time after which the device's screen turns off due to inactivity.

"secureDevice": {
   "enable": true,
   "timeoutInSecs": 30,
   "screenOffTimeoutInSecs": 30, // Optional, if applicable
}

Configuring Sound Effects and Alarm Settings

Users can customize the sound effects and alarm settings within the configuration. Default settings for soundVolume and enableEffects are shown below:

"secureDevice": {
   ...
   "soundVolume": 100,
   "enableEffects": false,
   "effectsSound": "assets: mediafile",
   "alarmSound": "assets: mediafile",
   ...
}

Defining Snooze Settings

To temporarily disable alarms or sounds, define the maximum number of allowed snoozes and the snooze duration in seconds in the configuration. Default settings are shown below.

"secureDevice": {
   ...
   "maxSnoozeCount": 1,
   "snoozeDuration": 120,
   ...
}

StartLogin Functionality

The user can opt to cradle the device without logging in. But if the startLogin is enabled in the configuration, the login page will automatically be displayed on the screen once the device is uncradled. The user must enter their login details within the configured timeout period; otherwise, the device will play a looping alarm. Default is false.

"secureDevice": {
   ...   
   "startLogin": true,
   ...
}

Putting It All Together

For the example described above, the full configuration for the Secure Device feature is as follows:

"secureDevice": {
   "enable": true,
   "timeoutInSecs": 30,
   "screenOffTimeoutInSecs": 30, // Optional, if applicable
   "maxSnoozeCount": 1,
   "soundVolume": 100,
   "startLogin": true,
   "enableEffects": true,
   "effectsSound": "assets: mediafile",
   "alarmSound": "assets: mediafile",
   "snoozeDuration": 120
}