Have more questions? Submit a request

Creating a new device policy

Device Policy is only available for devices using Device Plan Pro and higher.
Device policies are applied/checked on server ~2-6 minutes. Applet changes are propagated within this interval.

create-policy.gif

Adding new Policy

In Box navigate to Organize -> Device Policy and click Add Policy.

  1. Fill in a Device Policy name
  2. Select Organization under which you want use this policy

new-policy-01.png

 

Device Policy is limited to a single Organization and cannot be moved or transferred to another Organization.

Device Universal Policies

new-policy-device-universal.png

Set of policies that are available across all devices and do not require any device-specific options.

  1. Orientation
  2. Resolution
  3. Brightness & Brightness schedule
  4. Volume
  5. Temperature threshold
  6. Remote control lock
  7. Timezone and NTP

Scheduled Actions

new-policy-device-schedule.png

Scheduled actions managing the power state of the devices.

  1. Native Timers
  2. Proprietary Timers
  3. Scheduled Reboots

Device Specific

In this section, you can define device-specific options and keep a single Device Policy that works across all devices.

For each platform, you can set:

  1. Specific Core App version
  2. Specific Firmware

In case the device has a different Core App, the Device Policy will reinstall the Core App to the desired version.

Setting Samsung MagicInfo RM Server URL

For Tizen devices, you can adjust and set the MagicInfo RM Server URL. Tizen displays will set this URL and keep it set. 

Applet

In this section, you can define Applet and its configuration that will be set on the device.

Important notes:

  1. If a device doesn't have an Applet set up, it will use the Applet from its assigned Policy. If this Policy is later removed, the Applet will stay on the device to prevent any interruption in content, which is particularly useful during maintenance or certain configuration adjustments.

  2. When you replace a Policy (let's call it Policy A) that includes Applet A with a different Policy (Policy B) that includes Applet B, the device will then use Applet B.

  3. If an Applet is manually assigned to a device, it will be temporarily deactivated if there is also a Policy-assigned Applet linked to the device. Once any such Policy and its Applet are removed, the manually assigned Applet will become active again.

History Log

The history log keeps the complete history of any change made to the Device Policy, including information on how such change occurred. It provides you with a previous->next value overview.

new-policy-history-log.png

 

Was this article helpful?
0 out of 0 found this helpful
Share