Mobile Application Management (MAM) and Mobile Device Management (MDM) 

Before implementing an MDM solution it’s important to identify the scope of management required. For example, a school-owned device will need to be fully managed for insurance, security posture, ease of troubleshooting and to better align with the schools mission and objectives. Whereas a bring your own device (BYOD) may only require partial management through MAM if at all. 

There are many reasons for a BYOD to be managed by the school, including but not limited to ease of app deployment and increased security posture. It is recommended that before a school deploys BYOD management of any kind that staff, students and parents receive adequate communication, including but not limited to, what is and what isn’t in scope of the BYOD management privacy policy pertaining to information collection.

Documents for parents to sign will also need to be distributed and signed prior to enrolment. 

In essence, while MDM provides comprehensive control over mobile devices, MAM offers a more focused approach to managing and securing the applications used on those devices. The choice between MDM and MAM, or a combination of both, depends largely on the specific needs and policies of a school, as well as the balance between security and user privacy. It is your responsibility as a school to make a choice between these options and implementation is at your own cost.