...
Fig. 2 - Select “Download Enrollment template”
3. Fill out the downloaded template
| Info |
|---|
When the user clicks on “Download enrolment template”, The template downloads on their computer and can be accessed from the “downoads” “download” folder. Every other column apart from Device ID & Mac address, are drop-down selections. But for these two, the user is expected to type in the data by the data. |
...
Fig. 5 - Bulk enrolment result.
Exceptions
| Info |
|---|
There are a number of reasons why the bulk enrolment process could fail
|
Device Tagging
For a user to be able to access the SmartMDM app on their device whether, on Windows or Android, they have to first tag thier device. This is like giving this device it’s own unique identity so that the admin is able to identify as well as manage them properly.
Basically, the tagging process enables the admin to recognise nd onboard the new device using their Device ID or IMEI. The tagging process can be done in two ways:Devices can be tagged automatically (admin enrolment) or manually.
For Admin enrolment, Tag requests are approved once an admin successfully enrols a device (process explained in the portal onboarding section above). The manual device tagging approval option is explained below.
Self Enrolment
In this processcase, the tagging process starts with the agent who user first installs the SmartMDM application on the device before his device is enrolled on the portal. In this scenario, the SmartMDM application automatically sends a tag request to our system. This request is displayed on the portal; Device Enrolment>Tag Requests, The admin would be required to approve this request before the device can be successfully tagged. Also important to note is the fact thatwhile attempting to tag requests from “Self Enrolments”, the admin will be required to create a user-device-relationship. This means that for an admin to be able to approve a tag request, they have to create an agent for which the device is to be mapped to.
There is also an option to approve bulk tag requests. If the user has a lot fo tag requests to approve, they can download the “bulk tag approval template”. This would allow them to enter all the required details at once.
Once this is done, the device would be considered tagged & then the agent can go ahead and login to their device. Find below the step by step process of achieving this.
<<Insert screenshot of tag approval view>>
Exceptions
...
app on their device. When this happens, the device sends a tagging request to the backend. These tagging requests are displayed on the portal and can be approved from the “Tag Request Approval” page.
There are two methods to approving a tag request.
Single tagging request approval - For this, the admin clicks on their preferred device, assign it to a user and then approve the tag request.
Bulk tagging request approval - For this, the admin downloads the bulk tagging approval template, fill out the required columns and upload to approve tagging request.
Follow the steps below to approve a tag request.
Navigate to the “Tagging Request” module
| Info |
|---|
This page contains all the devices that have sent tagging requests to the portal. Ths status “unassigned” clearly shows that these devices have not been assigned to any agent yet. N.B: If a device is “untagged”, it means it has not been assigned to any agent and if a device has not been assigned, the SmartMDM app cannot be accessed on the device because you need a valid login details to be able to access the app. |
...
Fig. 1 - View Tagging Requests
2. Approve Tagging Request
| Info |
|---|
To approve a tagging request, click on the actions icon, select “assign” and fill out the form to assign the device to an agent. |
...
Fig. 2 - Approve Tagging Requests
| Info |
|---|
When a device is successfully assigned to a user, then the tag requests have successfully been approved. |
Bulk Tagging Request Approval
Download the Bulk tagging approval template
...
Fig.1 - Select Bulk Upload
2. Select Download Template
...
Fig. 2 - Download bulk tagging request approval template
3. Fill out the template
| Info |
|---|
On this template, the devices that have sent tagging requests, are prefilled on the template. (As you can see the Device ID column is a drop-down selection) The drop-down selection allows user to select the device they wish to map to a user. |
...
| Info |
|---|
After filling out the sheet, the user can upload the sheet just like was done with the admin enrollment option and then the result for devices that were successful will be displayed on the “Bulk Tagging Approval Result” template. |
Exceptions
| Info |
|---|
|
...
|
Kiosk Mode
To enable the kiosk mode on a device, you have to first run the ADB command.
The first step to remotely controlling a device is enabling kiosk mode (See Android Onboarding page) on the device. Kiosk Mode is a lockdown mechanism accessible on Android devices to run just a solitary application or a predefined set of applications. After enabling Android Kiosk Mode, all different applications and device functionalities like status bar, notifications bar are disabled and clients will likewise be restricted from making any changes to the device settings.
...