Pushing settings to enrolled devices

Settings are sent as key-value pairs (see Managed App Configuration keys).

These can be pushed to enrolled devices through the EMM console interface or via an xml file.

The settings allow the EMM provider to:

  • Define the Tenant Info (the URL or company Code) to which the users connect.
  • Set the Tenant Info (the URL or company Code) to be read-only on the device.
  • Designate devices as "organizational" devices. This is used by organizations that customize access based on device-type.

  • Block local authentication features on the app. This setting will prevent the use of local authentication (biometrics, pin, passcode) in the UKG Pro Mobile App. This will impact login and any other features such as 'local authentication for punch."

Pushing a new URL

EMM: Pushing a new URL.

It is recommended that the tenantInfo key should be part of every push by the EMM console. Note that if a push does not contain tenantInfo, but other supported keys are pushed, the app will honor the pushed settings and the devices will still show the most-recently pushed TenantURL/Company Code. If no tenantInfo was ever pushed, then the user would have to manually enter the Tenant URL/Company Code.

Note: It is strongly recommended that after the tenantInfo key is pushed, all users should access the system once to ensure the new settings are in effect.

Removing pushed settings

EMM: Removing pushed settings.

When an EMM administrator performs a Push, all settings are updated, even settings that are not part of the push. If a key is not included in the push, this essentially clears the setting to the following:

  • tenantInfo – The most recently pushed URL/Company Code
  • readOnlyTenantUrl – False: users can enter/change the Tenant URL or Company Code manually.
  • isOrganizationalDevice – False: devices will not send an Organization Device flag to the system.
  • blockLocalAuthentication – False: Local authentication method (PIN, Passcode, Biometric) still in effect in the app.

Timing the update

EMM: timing the update.

Updates should occur within a published plan-maintenance window, especially when URL propagation is included. Pushing an updated URL will logout all logged-in users without saving their unsaved data.