User Tools

Site Tools


mobile_devices

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
mobile_devices [2018/05/27 13:19]
devreach
mobile_devices [2018/07/20 15:10] (current)
devreach
Line 9: Line 9:
 {{:​mobiledevicescreen.png|}} {{:​mobiledevicescreen.png|}}
  
 +
 +__**Settings**__
 +
 +The Settings link on each employee'​s row will take the system user into the main system for that particular mobile device. This is where the EMM functionality can be applied to the device. [[settings_main_screen|Settings]]
  
 **__Refresh List__** **__Refresh List__**
Line 44: Line 48:
 A number can be entered in the Top box to limit how many rows are shown in the list. A number can be entered in the Top box to limit how many rows are shown in the list.
  
-__**Edit ​Account and Add Account**__+__**EditAdd and Remove ​Account**__
  
 This screen is used to primarily edit mobile user information. For example, name and mobile number. It also holds other data too. This screen is used to primarily edit mobile user information. For example, name and mobile number. It also holds other data too.
Line 61: Line 65:
 Once any edits have been made, they must be saved via the Save Changes button. Once any edits have been made, they must be saved via the Save Changes button.
  
-The account can be removed by clicking the Remove ​Account button.+__**Remove ​an account**__
  
 +The account can be removed by clicking the Remove Account button. This will remove the current user on the device, E.g. delete the user and messages particular to that employee. (once the user is deleted from the device, the main system will update and you will no longer see the account.) The EMM functionality is still however intact on the device. __Clicking Remove Account will only work if the mobile user is still enrolled on the device. If the mobile user deletes the app off the device first, then the account could be orphaned in the main system.__
 +
 +Once a mobile user has been successfully removed, the system user can add a new account for a new employee with the existing device'​s mobile number and send the Authorization code to the device.
 +
 +NB. __**If the device is not linked to the main system after removing an account and enrolling a new user, then go to the settings screen on the device and click Register for Push Notifications. This will create and send a new Firebase token to the server. From that point on the device will be contactable.**__
 +
 + 
 +
 +
 +
 +
 +
 +__**Send Auth Codes**__
  
-**__Send Auth Codes**__ 
  
 {{:​sendauthcodes.png|}} {{:​sendauthcodes.png|}}
 +This screen show all the employees prior to enrolment. In order to enrol a device into Devreach, an authorization code must be sent to the device. The code is sent via SMS. once received by the device, the employee can enter the code and username (which is also sent in the SMS), into the login screen in the Devreach android app. This will link the device into the main system.
 +
 +Authorization codes can be sent singularly or as multiples by selecting the corresponding check tick on each row. The top most check tick will select/​deselect all rows.
 +
 +
 +Once all relevant employees have been selected, Send Auth Code(s) now button can be clicked. This will send the SMS to all selected devices.
 +
 +
 +Each customer has a set amount of text messages based on the number of employees stated when signing up for Devreach. This allowance is usually 20% greater than the total number of employees. The limit can be raised by contacting Devreach.
 +
 +The current number of used SMS is displayed in the SMS Allowance box.
 +
mobile_devices.1527423560.txt.gz ยท Last modified: 2018/05/27 13:19 by devreach