# Console

Click on Below Links to read about various sections of the Esper Dashboard

# Manage Home

This page explains the functionality of the Esper Home Dashboard.

There are four tile sections on the Home Dashboard page:

# 1. Deployment Status

This tile shows the current deployment status of the devices for the current customer environment and includes a clickable link to number of Active, Inactive, Under Provisioning and Recently Added devices. Clicking on each takes the user to the Device Dashboard showing the corresponding category of devices.

# 2. Security Summary

The Security Summary tile shows a summary of security status of the deployed devices. It shows how many of them are at High Risk, Medium Risk, Low Risk and No Risk. Clicking on each takes the user to the Device Dashboard showing the corresponding category of devices.

# 3. Where are your Devices?

This section gives an overview of the location where all the devices are deployed. You can see a world map showing locations of all the devices in Map and Satellite View. It can be made full screen and user has options to zoom in and zoom out. There is also a summary of cities worldwide containing the highest number of devices.

# 4. Alerts Status

The Alerts Status tile gives a summary of Alerts you've created and Alerts that have been fired for each of the created Alerts. The Alert name can be selected from the dropdown and the number of Alerts fired will then be shown.

# Dev Home

Read about the Developer Tools and Documentation here -

Esper API Keys - Get API Key and Enterprise ID to be able to access Esper APIs to integrate in your app development code. See here - https://foo.esper.cloud/developer-console/

Esper API Reference - Checkout all APIs that you can use to manage your dedicated devices at https://api.esper.io using HTTP/REST framework.

Esper SDK For Python - Install SDK for python using instructions here - https://docs.esper.io/home/pythonsdk.html

Esper CLI - Quickly execute CLI commands to install/uninstall/manage deployment on your provisioned devices

Esper Plugin For Android Studio - Use Esper Plugin to easily deploy new versions of your app onto Esper dashboard and to your dedicated devices. This plugin enables you to remotely view/control your devices on Android studio as well.

Esper Docs With Quick Starts - This is one stop for all documentation regarding API, CLI, SDK, Plugin and Console.

# Provision Device

Provisioning is the initial step to configuring and managing your Android device using the Esper Management Console and associated developer tools.

Esper provides multiple methods of provisioning a device, which involves downloading the Esper Agent onto the device and configuring it according to the provisioning settings used for a Device Template. The supported provisioning methods are:

1. AFW provisioning - AFW (Android for Work) method is best used for:

   • Devices that have GMS (Google Mobile Services) enabled
   • Devices with a camera for QR code scanning

2. ADB provisioning - ADB (Android Debug Bridge) method is best used for:

   • Devices with No Google Services
   • Devices with No camera
   • Devices running Android 6.0, 5.1 or 4.4

3. IMEI (or Serial Number) based provisioning

   • IMEI/Serial Number method is use for Bulk provisioning of devices
   • Enables zero touch provisioning

4. QR Code Provisioning

   • QR Method like AFW is used for devices that have both GMS (Google Mobile Services) and Camera enabled

# Device Template

# How to use Esper's Device Template.

Device Template is a one stop means for you to quickly provision your device. It lets you create a profile for the device where you may choose the policy, apps, device settings, Device Group, and the wallpapers that you want to be provisioned on the device. Device Templates can be created, saved, and used to provision at a later point.

# Steps to create a Device Template.

1. Click on 'Device Template'.
2. Click on 'Create Template'.
3. Enter a name for the Device Template. Click Next.

# In the Policy section

Policy is a standard set of rules or permissions that are related to security of the devices and apps that admin can apply on the devices to be provisioned via template. Admin may set default app permissions, Android setting app, system updates, password rules, and turn on the toggle buttons for the settings he/she wishes to enable on the devices.

Below is a list of features you can turn on or off in the policy section. These are part of our standard Compliance policy that can be configured and reapplied as per requirements of the customer after provisioning.

Dropdown menus-

1. Device Password Rules - If you choose alphabetic or alphanumeric, a minimum password length can be entered. The default minimum password length is 4.
   The Password rule is a policy that specifies the rules for the device unlock password that users can set.

   Alphabetic: Restricts acceptable password to contain only alphabetic characters (A to Z) in both upper and lower case.

   Alphanumeric: Expands from Alphabetic to also include numbers and special characters.

   None: There is no password required to lock the device.

   The password for a device is setup during the initial setup of the device by the user.
   

2. Default App Permission
   Default app permissions determines enforcement of the runtime-permission rule across all the apps on a device (e.g. Gallery, Camera).

   Allow automatically: This rule will grant all the permissions any app requests without showing a prompt to the user.

   Ask user: This keeps the default behavior intact with regards to permission management. All apps on the device will show a prompt to the user to request permission. For example, by choosing this option then every app will ask the user each time before accessing a device module with a message such as “Allow app X to access Gallery? Allow/Deny”

   Deny automatically: This rule will deny any permission request from any app on the device.
   

3. System Updates
   The System updates option allows you to enforce a system update policy on the device when a system update/OTA update is available.

   Update automatically: Enforcing this rule will install any OTA update automatically and reboot the device without requesting the user.

   Postpone installation: This option postpones installation of an OTA update for 30 days.

   Windowed installation: This option allows you to define a time window during a full day period inside which the OTA update will be installed.
   

4. Android Settings App
   Android settings app determines how users can access the Android device settings.

   Default setting app: Selecting this will show the icon for the default Android settings app. Clicking this icon will take the user to the default Android settings.

   No settings app: No icon for any settings app will be available for the user to choose from the device’s dashboard.

   Esper settings app: Esper offers a custom Settings’ app that limits the user to only a subset of the available Android settings. Settings provided via this app are limited to:

   1. Changing the Wi-Fi AP

   2. Enabling the “flashlight” if there’s a camera flash LED on the device

   3. Control the display orientation of the device.

   Contact Esper to setup a password for the Esper Settings app.
   

Factory Reset Protection - New
FRP Toggle Button - FRP or Factory Reset Protection enables you to lock your device if a user tries to factory reset it via soft/hard keys. In case of a factory reset, the device will get locked and will only be reusable by a pre-authorized google account ID. See Policy section in docs to know how to get your google account id. Note that this feature is only available on android versions 5 and above.

On turning on the FRP button, user needs to enter the Google ID of the account they wish to authorize to enable usage of the device post factory reset.

See here to know how to get the Google account ID of your account and how FRP protects your device.

Other Template Compliance Policy Toggle Buttons-

1. Lock Screen
   If Locked screen is switched ON, it enables the default “lock screen” to be displayed upon a screen timeout as specified in the Settings section. If it is enabled, the user has an option to set the password rule in the dropdown above.
   
2. Safe-Mode Login
   Turn Safe mode login On to allow users to boot to safe mode on their device. Leave Off to prevent Safe mode login.
   
3. Factory Reset
   Factory reset dictates whether or not the user can perform a factory reset on the device. Turning it Off prevents a factory reset by the user. This is not inclusive of the hard key factory reset.
   
4. Notification bar
   Notification bar dictates whether or not a user can swipe down to display the notification bar. Turn On to enable access to the Notification bar.
   
5. Screenshot
   Screenshot allows or prevents a user from taking screenshots on the device using available screenshot actions. Turn On to allow screenshots.
   
6. USB connectivity
   USB connectivity allows or prevents the user to be able to communicate via USB on-the-go. Turn On to allow.
   
7. SMS
   SMS controls the ability of the device to send or receive SMS. If it is turned Off it prevents the device from using SMS regardless of which SMS app is used. Turn On if you wish to enable the device to send and receive SMS.
   
8. Outgoing calls
   Outgoing calls determines whether a user can make outgoing calls from the device. Turn On to allow outgoing calls, turn Off to prevent.
   
9. Camera Access
   Camera access allows or prevents a user to access the device’s camera. Turn On to allow.
   
10. NFC
    NFC controls the device’s ability to use NFC if it is supported by the device. Turning Off prevents the device or any app from using NFC. Turn On if any of your apps require NFC.
    
11. Google PlayStore
    Google PlayStore determines if the Google PlayStore app is available to the user on the device. Turn On to allow the user access to the Google Playstore of admin approved Google Play Apps.
    
12. USB tethering
    USB tethering specifies if the user is able to use their device to share a mobile connection to another device such as a laptop
    
13. Edit date and time
    Edit date and time determines if the user can change the date and time on device. Turn On to allow changes by the user.
    
14. Application uninstall
    For devices running Android 4.4 or 5.1, turning this setting On will block app uninstallation, especially important for private apps. This setting is not needed if you are running Android 6.0 or above.
    
15. USB File transfer
    Turning off USB file transfer will prevent the user from transferring files from the device to a computer and vice versa using a USB cable
    
16. Google Assistant New
    Enables/disables voice command via Google Assistant. Available only for Android devices supporting Google Assistant. For example - If you wish to have Google Play Store show up on the device, you may turn on the toggle button.
    
    

Checkbox-
Restrict outgoing/incoming calls using customised dialer.

If clicked, this opens up two more checkboxes-

1. Restrict incoming calls to uploaded contacts only <upload a csv file of allowed contacts>
   
2. Restrict outgoing calls to uploaded contacts only <upload a csv file of allowed contacts>
   In order to restrict phone numbers that can make or receive calls to the device, upload a .csv file with the allowed phone numbers.
   

You may reset these values to default at any time by clicking Reset to Default button at the bottom.

Click Next.

# In the Apps section

Select 'Kiosk mode' to pin an app during startup or 'Multi application mode' to give users access to the Home screen. Choose the apps that you would like to have installed on your device during provisioning. You may choose from install apps you uploaded via App Management or install apps from Google Play Store that you approved via Play For Work.

• As seen in image below, the first step is for user to choose whether they want to provision their device in kiosk or multi app mode by clicking on the radio button.

1. Kiosk mode - This mode pins the selected private app as the default app that stays pinned on the device screen permanently unless user exits the kiosk mode. This mode is useful for cases where device is single purpose and only app needs to run on it and admin does not wish device users to be able to interact with the device in any other manner. For example airport kiosks.

2. Multi-app mode - In multi app mode, user is free to use any private app, google play app or preloaded (in-ROM) app which are approved and installed by the admin. It is closely similar to BYOD but admin retains the control of the apps that are usable by the device user. For example a grocery delivery company wants their delivery person using the device to be able to use company app as well as the google maps.

• Default Android Launcher New - The next section is a simple checkbox labeled "Default Android Launcher" - This feature, if checked will provision devices with default android screen with no restrictions on the apps that can be installed and used. It will also disable various Esper Agent features and is best used when device usage is desired in loosely controlled environment.
  

  Here is a list of Esper features that will be unavailable in this mode as it applies the launcherless version of the Esper Device agent -

  • Capture Screenshot
  • Remote View and Remote Control
  • Install an app via dashboard
  • Uninstall an app via dashboard
  • Over the Air OS updates for Esper Enhanced Android OS
  • Latest Device Agent updates for Devices with Android version less than 6.0

  

  The device screen will look similar to a regular android device with Esper Device Agent showing up as an app that can be opened and closed.

  

  Even when user has exited the Esper Device Agent they will be able to see it running in the background in the notification bar as follows -

  

  If the Default Android launcher is unchecked, Esper Device agent will take admin control of the device and only approved apps can be installed or used. All features of Esper Device agents will be functional in this case.

• Preloaded Apps - The next section is of Preloaded (IN-ROM) apps where user may enter package names of apps that are already existing in the device to approve them to show up on the device after provisioning. The package names must be entered seperated by commas.

• Private (uploaded) Apps - The next section is for Private(uploaded) apps. User needs to upload APK files on App Management previously. Once uploaded, in template, user may click on the app from the dropdown, select the version and click on Add to add the private app to the template.

  

• To add app from Play Store list - click on the apps to add from the list of available apps. This section is a little tricky because user needs to approve the Google apps from Play Store or Play for Work section before they are able to choose them in this section.

Click Next.

# In the Branding section

Upload landscape and/or portrait wallpaper.

There is an option to Preview the uploaded wallpapers:

Click Next.

# In the Settings section

Change Device settings from Esper Dashboard. Following are features available -

• Turn on/off bluetooth
  
• Select screen timeout duration
  
• Select screen orientation
  
• Select GPS accuracy
  
• Increase/decrease Brightness, Volume (alarm, notification, ring and music)
  
• Timezone New - With our supervisor plugin, we have enabled you to change timezone of device remotely via dashboard.

Here is a complete screenshot of Template Settings page -

Click Next

# In the Group section

Select an existing Group or create a Group. The devices provisioned using this device profile will be a part of the selected Group. Click Next:

Click Next

# On the Preview screen

You will see a preview of the entire device template. If you wish to edit your settings, use the 'Back' button to go back to the appropriate screen:

Click 'Save'. You will see a pop-up to confirm your settings. Click Okay:

The Device Template you just created will now be visible on the Device Template page. You can search for it in the search bar. Click on it to view the Device Template. Click on 'View QR code' to provision a device using this template directly from your Device Template.

On clicking the View QR code, there is also an option to download the config.json Download Config file that can be used during ADB and IMEI provisioning:

You can also Preview, Edit, Duplicate & Delete the template:

Click on the ellipsis (...) on the template tile to preview, edit, duplicate or delete a template.

• Preview Template

Click on the Preview option to preview the device template. Click on the + sign to expand and then check selected individual components.

• Edit Template

To edit any template, click on the Edit Template option. Policy, Apps, Branding, Settings, Group and Add devices options can be updated as required. To save the changes, click on the Update button on the Preview page.

• Add Devices (IMEI Provisioning)

While editing a template, you also have the option to add IMEI/Serial numbers of devices you want to provision with this template. There is a section Add devices that appears if you click on Edit Template. Using this section, user can upload IMEI and Serial numbers. See details on IMEI Provisioning via Template here.

• Delete Template

Click on the Delete Template option on top right to delete a selected template.

# Devices

Manage your provisioned devices here.

You may view all your device details on the Devices dashboard.

# Categories

There are checkboxes on the top of the page with categories such as Active, Inactive, Under provisioning, Devices with low battery, etc. that can be checked to view devices in each particular state.

# Search

Search is provided on the top right where you can search for devices in Devices using the Esper assigned device code which is displayed on the device's home page wallpaper.

# Device Tile

The default view is Grid, but the user can click on Maps to access the map view. Under the Grid view each device will be represented as tiles in the ‘Device management’ tab with a summary of all device information such as location, network, health, and risk status of the device. Click on View More on the tile for any individual device to see further actions and changes that can be made for this device:

Devices listed 'Under Provisioning' refer to devices where Google Play apps are getting updated:

Devices under 'Applying Policy' refer to devices on which device templates are being implemented:

Devices which have been enrolled on to your Esper Cloud are provisioned devices:

# Map View

Under the Map view, the types of devices can be chosen from the dropdown. Once selected, the device locations are show:.

Once you click on the cluster icon, devices in the cluster will appear. Upon clicking on the individual devices, device information will be displayed:

# Groups

Learn about Esper's Group Management.

Using Groups devices can be sectioned into groups and mass actions can be performed on a group of devices. You can create a Group by entering a unique name. Once you create a Group, you have the option to add from all existing provisioned devices which exist in the "All devices" group. Users can also create a Group during template creation.

You can delete a Group by selecting one or many Groups using the top right button Delete group. There is also an option to refresh. Additionally, a search capability for search via group name has been provided. The Group tile will show the name and number of devices in the Group:

On clicking View more, you can take actions such as reboot, lock, ping, and wipe for the devices in the Group:

You can change a policy for all the devices in a Group:

You can install apps to all the devices in a Group:

You can also schedule app installation for the Group:

You can click on View Results to see the number of successful and unsuccessful device installations:

If your devices are using Esper Enhanced Android, you will also see a tab for OS updates.

Here you can see a list of the Esper Enhanced Android updates that have been made on the current group with details such as build number, device type, number of devices, and date deployed along with an option to view the details:

By clicking on the Deploy OS Updates button you may choose any available Build number by then clicking on Select Build.

The Number of devices will populate with the devices in the group on which this update is applicable; this pertains to those that have an OS build version lower than the selected version for the deployment:

You may add the installation name, any pertinent notes, and after that click Save:

In a future update we will give users the option to choose the time window for their OS update installation.

# Apps

Learn about Esper's App Management.

This section enables you to manage your applications. You may add the following type of apps to your device:

1. Upload Private Apps (APK files) to the Esper Cloud.
2. Install Google Play Apps after approving them.

See FAQ

# Upload Private Apps (APK files) to Esper Cloud:

• You can upload your own mobile app through an APK file using the upload button on the top right hand corner.

• There are some rules that the uploaded app must adhere to inorder to succeed upload and provisioning -

  1. The APK has to have a version name and number.
  2. Max size - 500 MB
  3. Extension - .apk [only]
  4. APK Signature verification
  5. Latest Android APK standards (currently we allow apks without icons)

• You can upload your own android app APK file using the upload button on the top right hand corner

• The uploaded apps will be shown under the 'Uploaded apps' section:

When you click on any private app, it will open the details of the same. For example in the below screen, you may see details of the Zomato (uploaded) app. It shows the following details -

1. Name of the app
2. Package name
3. App icon (if parsable)
4. Version number (for each version). Note that the same app can have various versions.
5. Number of devices the app is installed on
6. The date the app was uploaded on
7. Size of the app
8. Compatibility with SDK version
9. App description New - We now have a new field for you to add your app version specific description or release notes.

In the above image, you can see ellipsis (3 dots) under Actions.

Here is another example of an app with description -

On clicking the ellipsis under Ation, user has options to:

1. Delete the app version

2. Edit description New - You can now add and edit description or release notes per version of the app.

   A description can also be added during app upload.

3. Download the app version

# Install Google Play Apps after approving them:

• You can also allow a user to download apps from Google Play Store.
• This requires approving a specific app from the Play Store to allow a user to download the app on their device:

• You also have the option to handle new 'App Permission Requests' for the approved apps. You can:

1. Approve the requests for new app permissions so that users can update the installed app.
2. Revoke the requests for new app permissions so that users cannot update the installed apps.

3. You can set the option to receive email notification whenever an app requests new permissions by adding the appropriate email address or addresses in the notification settings:

• You can then select the device you want the app to be installed on by clicking on the 'Select option' and then 'Select the Device':

• Once the app is installed on the device, a notification shows up indicating the app was successfully installed:

• You also have the option to update or uninstall the app from a specific device:

• You can unapprove the app from all the installed devices by clicking the 'UNAPPROVE' button.
  
  Note: Unapproving an app does NOT mean uninstalling it. If the app was approved earlier, it will continue to stay installed in your device until it is explicitly uninstalled. Post uninstallation, if it has been unapproved, user/admin will not be able to uninstall it on the device.

• You can also see all the approved Google Play Store apps under Play Store section:

# Play for Work

Learn about setting up Play for Work apps using Esper.

• Play for Work gives you access to the Enterprise version of Google Play.
• Here you can either APPROVE or UNAPPROVE applications that can be downloaded onto your dedicated devices. After an app is approved it be visible on Google Play for device installation:

# Approve an app

• Approve an app by clicking APPROVE button.

• Upon clicking APPROVE a pop-up will appear:

• Via the pop-up you can set app permission requests:

• Upon clicking SAVE, your settings will be applied to the app. The dedicated device user can then access it from the Play Store within the given app permission requests:

# Unapprove an app

• Once you click UNAPPROVE, the access to the application is removed from user’s Google Play account:

• Click the OK button to remove the application from user’s Google Play account:

• After clicking OK you will get a message indicating that it was successfully UNAPPROVED:

# Approval settings

Upon clicking OK you will see a pop-up showing the APPROVAL SETTINGS tab and NOTIFICATIONS tab. Choose the desired APPROVAL SETTINGS:

# Notifications

sets up email notifications for anyone requesting new permissions to the specified email address or addresses:

# Alerts

Learn about available Alerts.

User Alerts to monitor the performance of your devices. You can create a device alert that watches a single metric:

• The alert performs one or more actions based on the value of the metric relative to a threshold over a selected time period.
• Choose an alert, the set condition, the name for the alert and then click on 'Create alert':

Delete icon

• Use this to delete an alert:

# Compliance Policy

Policy is a standard set of rules or permissions that are related to security of the devices and apps that admin can apply on the devices to be provisioned via template. Admin may set default app permissions, Android setting app, system updates, password rules, and turn on the toggle buttons for the settings he/she wishes to enable on the devices.

• A new policy is created and can be deployed on any device.
• The new policy gets listed on the 'Compliance Policy' page which can be edited or deleted as required:

Below is a list of features you can turn on or off in the policy section. These are part of our standard Compliance policy that can be configured and reapplied as per requirements of the customer after provisioning.

Dropdown menus-

1. Device Password Rules - If you choose alphabetic or alphanumeric, a minimum passowrd length can be entered. The default minimum password length is 4.
   The Password rule is a policy that specifies the rules for the device unlock password that users can set.

   Alphabetic: Restricts acceptable password to contain only alphabetic characters (A to Z) in both upper and lower case.

   Alphanumeric: Expands from Alphabetic to also include numbers and special characters.

   None: There is no password required to lock the device.

   The password for a device is setup during the initial setup of the device by the user.
   

2. Default App Permission
   Default app permissions determines enforcement of the runtime-permission rule across all the apps on a device (e.g. Gallery, Camera).

   Allow automatically: This rule will grant all the permissions any app requests without showing a prompt to the user.

   Ask user: This keeps the default behavior intact with regards to permission management. All apps on the device will show a prompt to the user to request permission. For example, by choosing this option then every app will ask the user each time before accessing a device module with a message such as “Allow app X to access Gallery? Allow/Deny”

   Deny automatically: This rule will deny any permission request from any app on the device.
   

3. System Updates
   The System updates option allows you to enforce a system update policy on the device when a system update/OTA update is available.

   Update automatically: Enforcing this rule will install any OTA update automatically and reboot the device without requesting the user.

   Postpone installation: This option postpones installation of an OTA update for 30 days.

   Windowed installation: This option allows you to define a time window during a full day period inside which the OTA update will be installed.
   

4. Android Settings App
   Android settings app determines how users can access the Android device settings.

   Default setting app: Selecting this will show the icon for the default Android settings app. Clicking this icon will take the user to the default Android settings.

   No settings app: No icon for any settings app will be available for the user to choose from the device’s dashboard.

   Esper settings app: Esper offers a custom Settings’ app that limits the user to only a subset of the available Android settings. Settings provided via this app are limited to:

   1. Changing the Wi-Fi AP

   2. Enabling the “flashlight” if there’s a camera flash LED on the device

   3. Control the display orientation of the device.

   Contact Esper to setup a password for the Esper Settings app.
   

Factory Reset Protection - New
FRP Toggle Button - FRP or Factory Reset Protection enables you to lock your device if a user tries to factory reset it via soft/hard keys. In case of a factory reset, the device will get locked and will only be reusable by a pre-authorized google account ID. See Policy section in docs to know how to get your google account id. Note that this feature is only available on android versions 5 and above.

On turning on the FRP button, user needs to enter the Google ID of the account they wish to authorize to enable usage of the device post factory reset.
See here to know how to get the Google account ID of your account and how FRP protects your device.

Other Compliance Policy Toggle Buttons-

1. Lock Screen
   If Locked screen is switched ON, it enables the default “lock screen” to be displayed upon a screen timeout as specified in the Settings section. If it is enabled, the user has an option to set the password rule in the dropdown above.
   
2. Safe-Mode Login
   Turn Safe mode login On to allow users to boot to safe mode on their device. Leave Off to prevent Safe mode login.
   
3. Factory Reset
   Factory reset dictates whether or not the user can perform a factory reset on the device. Turning it Off prevents a factory reset by the user. This is not inclusive of the hard key factory reset.
   
4. Notification bar
   Notification bar dictates whether or not a user can swipe down to display the notification bar. Turn On to enable access to the Notification bar.
   
5. Screenshot
   Screenshot allows or prevents a user from taking screenshots on the device using available screenshot actions. Turn On to allow screenshots.
   
6. USB connectivity
   USB connectivity allows or prevents the user to be able to communicate via USB on-the-go. Turn On to allow.
   
7. SMS
   SMS controls the ability of the device to send or receive SMS. If it is turned Off it prevents the device from using SMS regardless of which SMS app is used. Turn On if you wish to enable the device to send and receive SMS.
   
8. Outgoing calls
   Outgoing calls determines whether a user can make outgoing calls from the device. Turn On to allow outgoing calls, turn Off to prevent.
   
9. Camera Access
   Camera access allows or prevents a user to access the device’s camera. Turn On to allow.
   
10. NFC
    NFC controls the device’s ability to use NFC if it is supported by the device. Turning Off prevents the device or any app from using NFC. Turn On if any of your apps require NFC.
    
11. Google PlayStore
    Google PlayStore determines if the Google PlayStore app is available to the user on the device. Turn On to allow the user access to the Google Playstore of admin approved Google Play Apps.
    
12. USB tethering
    USB tethering specifies if the user is able to use their device to share a mobile connection to another device such as a laptop
    
13. Edit date and time
    Edit date and time determines if the user can change the date and time on device. Turn On to allow changes by the user.
    
14. Application uninstall
    For devices running Android 4.4 or 5.1, turning this setting On will block app uninstallation, especially important for private apps. This setting is not needed if you are running Android 6.0 or above.
    
15. USB File transfer
    Turning off USB file transfer will prevent the user from transferring files from the device to a computer and vice versa using a USB cable
    
16. Google Assistant New
    Enables/disables voice command via Google Assistant. Available only for Android devices supporting Google Assistant.

For example - If you wish to have Google Play Store show up on the device, you may turn on the toggle button.

Checkbox-
Restrict outgoing/incoming calls using customised dialer.

If clicked, this opens up two more checkboxes-

1. Restrict incoming calls to uploaded contacts only <upload a csv file of allowed contacts>
   
2. Restrict outgoing calls to uploaded contacts only <upload a csv file of allowed contacts>
   

In order to restrict phone numbers that can make or receive calls to the device, upload a .csv file with the allowed phone numbers.

You may reset these values to default at any time by clicking Reset to Default button at the bottom.

# Users

Learn about Esper's User Management.

Under the Users tab you are able to view all registered users in your enterprise. Here you can add, delete, and edit users:

New User

• To add a new user, click on New User and fill in details of the user in the form:

• Upon creating a new user, you will get a confirmation pop-up:

Edit icon

• Here you can edit the details of a user.
• You will be able to change the username, email, full name, password, and role assigned to the user:

Delete icon

• Click on the Delete icon to delete a user from the enterprise. That user will no longer be able to access their account:

# Geofence New

Now in Esper - Geofences! Geofencing is a useful feature for some dedicated device deployment scenarios. With geofencing you use the device’s location typically generated by GPS to trigger an alert when the device enters or leaves a defined area. Common scenarios include making sure a fleet of delivery devices stay in their delivery zone, warehousing devices don’t stray far from the warehouse, and restaurant ordering devices don’t leave the restaurant.

In order for geofencing to work, the mobile device needs Internet connectivity and location services enabled. Thus this is typically for cellular connected devices with high accuracy location services enabled - whether smartphones or tablets.

Setting up a geofence for a device is easy - it starts by selecting Geofence in Esper Console left navigation pane - this brings you up to a wizard for quickly defining the geofence. Click on New Geofence:

In the first screen you define the size of your geofence (meaning where you expect any devices to be for this geofence) - it is a circle that can be as small as 100m radius up to 10km. Note that GPS can drift and jump, thus a geofence smaller than 100m can cause false positives. To set it up at a location simply type the address for the center of the circle, or drag it in the map view to set it up. Give it a name and description, and then click Next:

Now you assign devices to this geofence - you can do as many as you need that fit the criteria for the geofence. In this case we are just doing one:

Now you define the action to be taken when any of the assigned devices leave the geofence - you can either lock them, have them beep, or both. In this case I went with beep!

If you chose to Lockdown the device, you will see the following screen if the device is taken outside the geofence boundary -

You can see for Geofence applied Devices if they have left or entered the Geofence in the Event Feed section:

That’s it! It looks even easier in our video: https://youtu.be/UkTwhFRTwgQ

Give it a try and let us know what you think, andi@esper.io.

# Company Settings

Learn about Esper's Company Settings.

• Company Settings enables you to set your company details by clicking on the 'Edit profile' button on the top right hand corner:

• You are required to fill in your company information including:

1. Registered name
2. Location
3. Name
4. Zip code
5. Email
6. Address
7. Phone number

• If you will be using apps from Google you will also need to enroll your company's Google Play account:

# OS Updates

# Over-the-air updates for Esper Enhanced Android.

You can update the Esper Enhanced Android version using our OTA functionality. Currently, we are only showing the number of devices the build version has been applied to; this also includes the publish date and size. To deploy a new available build on a group, the user can go to Group->OS Update. See the Group section for more details.

# Developer Options

Turn App and Device Management into Code

Esper is focused on helping Android app developers build, deliver, and maintain Dedicated Device applications - whether a restaurant kiosk, retail POS, or logistics hub. We have made our APIs available to Android developers worldwide so they can move rote app and device management actions into reusable code. Anyone can use our APIs to build, orchestrate, and integrate elegant solutions based on their business requirements. We do the heavy lifting by taking care of the infrastructure, so app developers can focus on building great solutions rather than being bogged down in app and device management. We help you procure efficient hardware along with the optional secure, optimized Esper Enhanced Android and our open source APIs and SDKs. We also offer the Esper Plugin for the Android Studio with tools improving the challenging task of app diagnostics - including working with deployed apps running on dedicated devices in the field. Check out esper.io for more information about our rich feature set.

To kick things off, you need to generate an API key that you can tie to a specific application - it is your choice on how you want to manage your API keys. Do this by clicking the "Register App" button. You can also easily copy the Enterprise ID, necessary for API calls, by clicking on the copy icon next to Enterprise ID on top right of this section.

Next, you need to enter a unique app name and description(optional) and click register application.

Click Generate Token. This will generate a unique OAuth-based API key.

You can then copy (or renew if needed) your API key.

The API key and Enterprise ID can be copied from the dashboard as shown above and can be used to access our CLI platform (https://github.com/esper-io/esper-cli) as well as to use the SDK/API (api.esper.io) in your development and management systems.

Checkout the relevant documentation on the top right of this page by clicking on Developer Hub and API Documentation.

# Secure Remote ADB

Developer should be able to debug their devices remotely without even physical association with the device. ADB is android tool that help you to get take actions on the device, get the device or application logs and help you in resolving customer or in-field issues right by sitting remotely in your office.

This document tells you how you can remotely connect to device via secure adb channel. We will be using esper-cli command line tool which internally uses esperSDK APIs to provide the secure access between your host machine and device.

Remote access to the device can be done from anywhere in the world using espercli and doesn't have to be in the same network.

# Steps to connect to secure remote adb:

1. On to Esper Dashboard https://foo.esper.cloud, Go to Devices tab, then to your device and to Actions.

2. At the bottom of the page, Click enable adb.

3. On to your android device, connect via usb cable and enable adb over tcpip by following command:

   adb tcpip 5555
   

4. Disconnect usb cable from the device. You should be able to connect adb via port 5555 over tcp

5. Setup esper-cli and configure for your environment on to the host machine.

   • Check your espercli version: espercli -v

   #espercli -v
   Esper CLI is Command line tool for the Esper APIs:  0.0.5
   Cement Framework 3.0.2
   Python 3.7.3
   Platform Darwin-18.0.0-x86_64-i386-64bit
   

   • Make sure it is >= 0.0.5 to use secure-adb feature.
   • Upgrade to the latest version of espercli using the following command:

   pip install -U espercli 
   

6. Copy your device id from esper dashboard information tab or from your device bottom left most. It looks like SNA-SNL-1234.

7. Use espercli to connect to Device:

   #espercli secureadb connect -d SNA-SNL-1234
    Initiating Remote ADB Session. This may take a few seconds...
    Secure ADB Client
    Please connect ADB client to the following endpoint: 127.0.0.1 : 62945
    If adb-tools is installed, please run the command below:
    adb connect 127.0.0.1:62945
   

8. Now connect your device via port number obtained above on localhost.

   adb connect 127.0.0.1:62945
   

9. You are connected to adb.