> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/pbi-guides/pbi-private-access-administrators-guide/about-parallels-browser-isolation.md).

# About Parallels Browser Isolation

Parallels Browser Isolation (PBI) Private Access

### **Parallels® Browser Isolation (PBI) Private Access**

PBI Private Access is a Remote Browser Isolation (RBI) solution designed to provide secure, controlled access to internal applications, private web resources and SaaS applications. With Parallels Browser Isolation, organizations can isolate access to sensitive internal apps, enforce granular access policies, and maintain visibility into usage and security activity.

Using this platform, you can:

* Define and manage allowed internal applications and resources
* Apply fine‑grained access controls based on user, group, or app sensitivity
* Monitor usage patterns and security events through built‑in analytics

Parallels Browser Isolation is made up of two core components:

#### **1. Browser Isolation Management Portal**

Used by administrators to configure internal resources, manage user access, and apply security policies.

#### **2. Browser Isolation User Portal**

Used by end users to securely access approved internal applications via an isolated, cloud‑based browser environment.

***

This guide covers how to configure and manage secure private access to internal apps using the **Parallels Browser Isolation Management Portal**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.parallels.com/landing/pbi-guides/pbi-private-access-administrators-guide/about-parallels-browser-isolation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.