> 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/getting-started/configuring-parallels-browser-isolation.md).

# Configuring Parallels Browser Isolation

Parallels Browser Isolation (PBI) Private Access

To configure Parallels Browser Isolation for the first time:

1. Read the Cloud Solution Agreement, and if you agree to it, click **Accept** to navigate to mthe ain page.

<figure><img src="https://4174765165-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyUid64pHy4oj360ExGWO%2Fuploads%2FjzAMo2vZjJxUR9uizfYa%2Fimage.png?alt=media&amp;token=d2d19557-fddc-43dd-b3bb-82aac6db4e25" alt=""><figcaption></figcaption></figure>

2. On the **Configure Domain & IdP** card, click **IdP Configuration**. The **Configuration** category will open.
3. In the **Domain Configuration** section, enter your organization's unique environment prefix `https://<Domain>.pbi.parallels.com`.
4. In the **IdP Configuration** section, do the following:
   * In the **OpenID configuration URL** field, specify the URL of the discovery document of your OpenID Connect provider.
   * In the **Client ID** field, specify your client ID for connecting to the identity provider. For Auth0, the format of the Client ID is `https://<Domain_Name>/.well-known/openid-configuration`.
   * In the **Client secret** field, specify the secret for connecting to the identity provider.
   * In the **Username claim name** field, specify the ID token that holds the username claim name:
     * For Entra ID, specify **preferred\_username**
     * For Auth0, specify **name**
   * In the **Group claim name** field, specify the ID token that holds the group claim name.
   * Click the **Test Configuration** button to make sure that the specified settings are correct.
5. Click **Save**. The **Overview** category will open.
6. In the **Set Admin,** field, specify the email (UPN) of the user you want to add as an administrator and click **Add**. The email must be exactly the same as that used in your IdP. Do this multiple times if you want to add several users.

<figure><img src="https://content.gitbook.com/content/yUid64pHy4oj360ExGWO/blobs/KW0JZiaIHr3z26eOVqKx/users%20pbi.png" alt="Users field"><figcaption></figcaption></figure>

9. In the **Groups** field, specify the group you want to add as an administrator group and click **Add**. The group name must be exactly the same as that used in your IdP. Do this multiple times if you want to add several groups.

<figure><img src="https://content.gitbook.com/content/yUid64pHy4oj360ExGWO/blobs/V44z4JmQot0CnKtMRgBD/groups%20field.png" alt="groups field"><figcaption></figcaption></figure>

10. Click **Save**. The **Overview** category will open.
11. On the **Access Admin Portal** card, click **Admin Sign In**. You will be redirected to Parallels Browser Isolation Management Portal.

Next, you need to [add users and groups that will access you applications](/landing/pbi-guides/pbi-private-access-administrators-guide/parallels-browser-isolation-interface/user-management.md).


---

# 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/getting-started/configuring-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.