@Diane I did some more investigating with my test devices and realized that what I am proposing is not possible. The only thing I could think of is to set up the whitelist and also create a policy that looks for unauthorized apps that would trigger a config to install. Here is what it would do:
Student device would have a whitelist of apps, have the app store available to update apps and download any whitelisted apps (the ones in your Meraki App/Catalog). Let's say a student installs a "blacklisted" app, it will look like it is about to install and then it will just pop away (as expected with the whitelist profile). The next time the device inventory updates in Meraki they will be considered non-compliant with the whitelist policy. I would have a configuration profile that removes the camera, safari, any anything else you want to remove to force them to have to see you. You would have to exclude them from the configuration and remove the app.
Until Meraki updates and allows you to push mass updates there are only two options. It would be nice if it was something we could set to occur at a specific time (midnight for example).
Jared
Find this helpful? Click the kudos button. Thanks!