Parallels Browser Isolation: Policies

Parallels
74 followers
Feb 24, 2026
This video covers how Parallels Browser Isolation policies enhance security by restricting applications through user groups, time, location, and actions like printing or downloading. Learn to customize user experience with visual indicators and domain restrictions. Practical examples demonstrate disabling applications and enabling UX features for secure browsing.
Learn more and start your free trial today via https://www.parallels.com/products/browser-isolation/
AI Generated·May contain errors
If we now take a look at policies in PBI.
So this is where you deliver restrictions to applications
or particular parameters or visual effects
that you want a particular application to use.
So I can view and edit and delete policy from here.
I can add a new policy.
So I give it a name,
I can optionally give it a description as well.
Now policies get applied to applications inside PBI,
but optionally you can also apply a policy
only to a specific group of users
if that's what you wanna do.
So the policy would be applied to the application,
but also whatever settings you're saying here
can be applied to a specific group, for example.
I can also determine what hours this policy becomes active.
So for example, I could have,
let's say three sets of users
all intending to work at a different time of day.
I can ensure that this policy only applies
during the time they either are at work or not at work.
And I can then perhaps disable the application
for those groups of users
that shouldn't be using the application
at that time of day.
For example, from a security point of view.
I can also only apply policies to a particular location
if that's what I wanna do.
And then I've got additional security controls.
So I can either allow or deny access to the application.
I can allow keyboard to be used or not.
I can allow the user to print from that application or not.
Can they copy to and paste from the application?
Also, do I allow downloads?
Now here I can actually deny the downloads by file type.
Again, there might be one particular file type
or a selection of file types
that I need to allow the user to download to their client,
but I can perhaps restrict all other file types.
So for example, I could deny everything
apart from a PDF in this example.
So that really depends on the application
that I'm administering,
but it's nice and easy.
I can configure that from here.
I can also stop a user uploading anything
into the application as well.
Then I've got some visual settings.
So I can give a blue border
or I can indicate this is a secure browser
by a tab or a little pop-up toast notification.
Watermarking puts the user's username
diagonally across the screen the entire time
to kind of discourage the whole screenshotting process
and that kind of stuff.
And I can also add domains specifically
that I'm going to block with policy here as well.
We're having a look at a policy
that's already been configured.
You can see I've denied a whole load of things.
I've denied keyboard, clipboard,
downloads, those kinds of things.
And I've also blocked access to Microsoft.com
for the sake of the demo,
because I want it to actually instigate
that blocked policy
so you can see the effect of the policy in action.
Now, we go and have a look at applications.
You can see where those policies are applied.
In this case, if I edit the application
and scroll all the way to the bottom,
I can see that the policy we've just seen has been applied.
I can add multiple policies to this application if I wish.
So I'm now going to go and see what the kind of impact
of that policy is on the application.
So we get the user to open the application in question.
That application then launches.
You can see it's a secure browser
because I've got that URL bar,
but I've restricted pretty much everything.
So I'm trying to, for example, type my username in here
and it's saying I can't use the keyboard.
I can copy that text,
or at least attempt to copy that text,
and it says I'm not allowed to do that either.
I'm like, right, okay, well, let's try a different location.
So now I'm accessing a Microsoft.com link
that is going to be blocked
because of my organization's policy as well.
So you can start to see how some of this stuff builds up.
Now, why would you disable keyboard, for example?
Well, a user might be logging in
using a different authentication method.
So they could log in through the IDP.
They don't actually perhaps need access to their keyboard
for that specific application.
And that concludes this video section on policies.
