Contents

Support this site


Configure MANAGED SETTINGS for Pulsus

MANAGED SETTINGS can be set up quickly and easily through Pulsus.

Prerequisites:

  • Android Enterprise is bound
  • A device group exists, or will be created for this guide
  • Requirements are met
  • A licence key, if desired
Avoid blocking the Settings application

You'll note in the below configuration steps, nowhere is it mentioned to import or attempt to configure the native Settings application. For the Kiosk use case, blocking Settings (com.android.settings) through the install type of Blocked will prevent MANAGED SETTINGS from working.

It is not necessary. Native Settings needs not be present in the application list at all.

Add MANAGED SETTINGS to Pulsus

#

Head to APPLICATIONS on the left-hand navigation.

Click the + icon and select Play Store.

Search for BAYTON MANAGED SETTINGS, or org.bayton.managedsettings if the former returns no results. Click the title to select the app.

Click Select.

A configuration page will now appear, allowing for app install, permissions, and configuration settings. Set these as desired, or leave them default to enforce installation.

Scroll down, and assign MANAGED SETTINGS to the appropriate group

Click SAVE. MANAGED SETTINGS will appear in the apps table.

Configure MANAGED SETTINGS

#

Hover over the MANAGED SETTINGS entry in the app table, and click MCM

Create a config name, set the appropriate configs, and click SAVE.

Configure the launcher

#

On the left-hand navigation, select LAUNCHER.

Select or create a new Launcher configuration, assigned to the appropriate group.

Drag MANAGED SETTINGS amongst the configured applications shown in the Launcher config, and optionally adjust launcher settings to lock down the kiosk environment appropriately.

Click SAVE. Configuration is complete.

Further support or feature requests

Are you in need of further help, or would you like to raise a feature request? You can:

mail Reply by email | edit_note Edit this page.