General Settings

In this Global Settings section, you can configure general settings across various platforms. They are described below.

Re-Enrollment Settings

Enroll Devices to their last Group/Profile when applicable

Platforms: This setting is configurable for Android, Mac and iOS devices

To access, navigate to Utilities > Global Settings > General Settings > Re-Enrollment Settings

By default, it is toggled OFF. When enabled, it applies the last group or profile that was set on the device after it is re-enrolled without being deleted from the Dashboard. This is useful when the device is:

1. Factory reset, or
2. Re-enrolled via Zero-touch or DEP, or
3. If the user locally removed the MDM profile or re-enrolled the device on macOS.

Disabling this applies to the Group/Profile based on the QR/Device configuration used at the time of enrollment.

Simply toggle on the settings and click Save settings to enable it.

Enrollment Rules for Company-Owned Devices

With enrollment rules, the admins can restrict the enrollment of company-owned devices to a few by configuring certain checks. The devices that meet these configured rules get enrolled in Scalefusion, and the ones that do not remain unenrolled. With this, they can prevent enrollments from unauthorized devices.

In brief, the following rules can be applied to the enrollment of devices

1. For specified IMEIs/Serial Number
2. For specified make/models
   These rules are applicable only on Company Owned devices (Kiosk Enrollment)

How to Access

1. On the Scalefusion Dashboard, navigate to Utilities > Global Settings.
2. Under General Settings, you will find the rules under the heading Enrollment Rules for Company-Owned Devices

Allow Enrollment only from uploaded IMEI/Serial# list

With this setting enabled, the enrollment of those devices is allowed, which are uploaded in the IMEI/Serial# enrollment section. If this setting is enabled, but no IMEI/Serial is uploaded, then enrollment from all devices will be allowed.

Platforms: This rule can be applied to Android, iOS, MacOS and Windows devices

How does it Work?

1. Toggle on the setting Allow Enrollment only from uploaded IMEI/Serial# list
2. This enables the following settings, viz
   1. Use the IMEI/Serial# list for Android Devices: Pick up the IMEI or Serial# of Android devices uploaded under IMEI / Serial # Enrollment and enroll only those devices.
   2. Use the IMEI/Serial# list for iOS/macOS Devices: Pick up the IMEI or Serial# of iOS and Mac devices uploaded under IMEI / Serial # Enrollment and enroll only those devices.
   3. Use the Serial# list for Windows Devices: Pick up the Serial# of Windows devices uploaded under IMEI / Serial # Enrollment and enroll only those devices.
3. Toggle On the platforms for which you want to apply this rule
4. Click Save settings at the bottom

For example,

1. Enable the setting Use the IMEI/Serial# list for Android Devices and Save it.
2. From the Android device, scan the QR code. The setting Apply Enrollment Rule should be applied in that QR Code Configuration for Android Company-Owned Devices
3. Now the IMEI/Serial# uploaded under IMEI/Serial# Enrollment will be checked, and the device will get enrolled accordingly. The verification will be performed irrespective of what enrollment method you are adopting (6-taps etc.)
4. If the IMEI doesn't match, the following message will be displayed on the device

Allow Enrollment from configured Make/Models only

This setting allows enrollments of the specified make and model of devices.

Platforms: This rule can be applied for Android and Windows devices

How does it Work?

1. Toggle on the setting Allow Enrollment from configured Make/Models only
2. Click on the button Add Make/Model
3. This adds a row underneath the table where you need to configure (enter) the following:
   1. OS: Select OS from the drop-down (Android or Windows)
   2. Make: Enter the make of the device like Lenovo, Samsung etc.
   3. Model: Enter the model of the device, For eg. SM-A920F
      Note:

      Ensure that the Make and Model are provided exactly as they are reported by devices, including spaces or hyphens (-).
      If no make/model is specified for an OS, then enrollments from all make/model will be allowed for that OS.
      
4. To add more rows for entering device details, click on the button Add Make/Model again
5. After configuring settings, click Save Settings at the bottom
6. At the time of enrollment, the models specified will be verified, and those devices will be enrolled. The setting Apply Enrollment Rule should be applied in that QR Code configuration.
   If you have enforced the IMEI/Serial# enrollment check (above), then both conditions will be applied.
7. If the make or model doesn't match as per the rule, the following message will be displayed on the device

Application Management Settings

1. To access, navigate to Utilities > Global Settings > General Settings
2. Scroll down. You will find them under Application Management Settings

Auto-Publish the latest version of applications when an app is enabled in the device profile

Enabling this setting will automatically publish the latest version of the application (when enabled in the device profile) available in the Enterprise store or Play for Work app section.

Important:

1. To have the latest version auto-published, please ensure that the app is also enabled under Device Profile > Select Apps
2. This setting works on Android and iOS platforms
3. For users who are on a non-enterprise plan, this setting will be enabled by default. But they can disable it only if they upgrade their plan.

If this setting is disabled, the application will not auto-publish, and you will have to explicitly go and publish the required version from the Application Management section manually.

Enable apps to be published to Groups with a profile

This setting provides the ability to publish/unpublish apps to Groups with and without device profiles.

1. Enable this setting to see all the device groups when publishing an app. That is, once you toggle on this setting and go to publish an app, all the groups with or without a device profile will be displayed.
2. Device Profiles will only show profiles that are not associated with any group. Here, the published version displays the version of the app that is published to that device profile
3. If an app is published to the group and profile, then the version published to the group is given precedence.
4. With this setting, you can publish different versions of the same app on one single profile. Hence, the admin can publish different or the same versions of apps to the profile and group.
5. This setting applies to Enterprise apps, Devices and User Groups for all platforms.
6. They also apply to Scalefusion Apps for Windows, macOS and Android platforms.

Enable Applications to be published to Devices in a Group or profile

Enable this option to directly publish apps to specific devices. With this, IT Admins can easily test Beta apps by initially publishing them on a few devices, and once they are sure of its functionality, they can roll it out to a wider group.

How it works

1. On publishing an app with this flag enabled, the Devices tab will display all the devices with or without device profile or group. From search bar, you can search for a particular device. 
   
2. The device will appear on the left side of window on searching. Click on the arrow next to it to push it to the right panel.
   
3. Once it appears on the right panel, click Publish.

Important Points to note:

1. You should be subscribed to Enterprise Plan.
2. Platforms supported: Android, Windows, iOS, macOS
3. Types of Apps supported: Android Play for Work apps, App configurations, Enterprise Store (APK files, MSI, EXE, UWP, Scripts)
4. You can also publish downgraded version of an app to devices.  

Reconcile app versions on Device

IT admins can also choose to reconcile devices to the app being published to override directly mapped version on the device, as there can be cases where a device may have a different version of the app compared to its profile or group. This can be done with the flag in Publish dialog box Publish/Override this version on Devices with direct mappings. It is enabled when the app is published to Device groups or Device profiles. If this flag is selected while publishing to a group or profile, 

All direct mappings of this App from devices selected in Devices tab (older versions or newer versions), are removed and the currently mapped version is being pushed to the devices.

SMS Service Provider Settings

For BYOD device enrollment, the IT admins also get the option to send OTP over SMS, along with email. For that, you need to configure these settings:

1. Toggle this setting to On. Only then the rest of the settings be enabled.
   1. Configure an SMS Provider that can be used to send OTPs for BYOD enrollments.
   2. Now configure the following:
      1. Choose Provider: Choose a service provider from the drop-down. Currently, we support Twilio.
      2. Account SID
      3. Auth token
      4. Twilio Phone number
         Account SID, Auth Token and Twilio Phone Number can be obtained from Twilio's Developer Portal. You should have an account created on Twilio.

         
         
2. Click Save Settings
3. Once settings are configured, the phone number (with country code) that you enter while adding a user for user enrollment will send the OTP over SMS on that phone number.