The biggest win for us is giving third-party contractors secure access to internal apps from laptops we don't own or manage. Their users get a familiar Chromium-based browser, and Island Private Access gets them to our private web apps without us having to hand out VPN clients or stand up VDI. Because the controls live in the browser rather than on the device, we can decide what users can copy, download, print or screenshot per app without needing an agent on someone else's hardware.
It also scales well across suppliers. Adding another contractor to the same tenant is mostly a policy exercise rather than a new infrastructure project.
The management API deserves a mention too. I pulled our full configuration through it to build an architecture document, which saved a lot of clicking around the console and gives us something we can keep current. Review collected by and hosted on G2.com.
As our deployment has grown, the policy rules have become harder to follow. Once you have layers of rules covering different user groups, apps and suppliers, it isn't always obvious which rule will apply to a given user in a given situation, or why. Tracking down an unexpected block, or something that was allowed when it shouldn't have been, can mean working back through the rule list by hand.
A way to test a scenario (this user, this app, this action) and see exactly which rule matched would make this much easier, along with a clearer view of how rules interact and override each other. Review collected by and hosted on G2.com.



