Unknown macro: {next_previous_link3}
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

WSO2 EMM enables you to register mobile devices via the BYOD or COPE device enrollment scenario. Data containerization allows you to have a separation between data. Therefore, if you are registering your device via the BYOD scenario you are able to have a clear separation between your personal data and the enterprise data. To understand the underlying concept clearly, take a look at the example given below.

Example:

MobX uses WSO2 EMM to manage and monitor the employees mobile devices and applications. Kim joins as the new marketing Manager and needs to register her personal mobile device with WSO2 EMM, but she is concerned because she doesn't want to expose the personal data on the device to the Organization. On the other hand, MobX is concerned about not letting the other applications installed in Kim's device to access the confidential enterprise data. For example Kim has installed an application for enterprise docs on her device. This application has access to all the enterprise docs and the personal docs as they are all stored in the same location. Therefore, it is important to clearly separate the enterprise and personal data in a BYOD device enrollment scenario. Follow the steps given below to enable data containerization on your device.

 Click here for more information on registering an Android device with data containerization, see End-user Registering an Android Device via the Managed Profile.
Error rendering macro 'panel' : com.atlassian.renderer.v2.macro.basic.validator.MacroParameterValidationException: Color value is invalid

How it works

Data containerization for Android devices was implemented using the Managed Profile feature that is available on the Android devices that supports the Android Lollipop OS or upwards. Let's take a look at the how data containerization works on WSO2 EMM.

 

 

  • No labels