Prompted by a customer request the other day to lock down Chrome on iOS to a range of webpages, I thought it was worth sharing my findings and a solution.
So, the request: To Lock down Chrome so that it could only display a range of webpages, and not allow browsing elsewhere
Many apps support the appconfig.org standards that allow for application config management. Meraki Systems Manager also supports this, so, if the app supports it, when creating a managed app config, such as Nine Work for Enterprise...
Systems Manager will offer a list of supported settings when you can then configure, as above.
So, having created one for Chrome, I found nothing...
I then found the following resources:
Thanks for taking the time to write that up @PaulF .
Knowing that it's not (currently) possible to lock Safari down in Kiosk mode, my thoughts turned to Webclips...
Per your quote above, I'm pretty sure it is and has been for some time. We've been using it on our iPad's since at least middle of last year.
Our method was to set Safari in Kiosk mode as per the usual process for setting any app in Kiosk mode.
Then add a managed app config that has some default pages we needed.
Then add content restriction whitelist bookmarks - that only allow the specific pages you need.
Pretty effectively blocked access to any pages that weren't explicitly bookmarked.
The only caveat is that we had some issues with renaming the profiles on-the-fly, so instead removed the profile first, renamed, re-added the profile.
Hi @MCrowther Do you have a link to any Apple documentation that lists the keys and possible values for Safari managed app config?
OMG ive been looking for a way to do this forever!!!!! thank you
Hi @PaulF ,
Nice write up.
It really does surprise me that Apple have not made this easier by now. We used the Chrome config for Android, which works quite well. The steps are the same for the show/hide apps.
Is it still the case that iOS WebClips cannot be removed/updated remotely once added? I think this was the caveat that killed the iOS solution for us in the end when we looked at doing this.
Thank you,
Peter James