---
title: Accessing a Device Through Both the Browser and the Container
slug: kronpam-reference-guide-3-9-0/accessing-a-device-through-both-the-browser-and-the-container
docTags: 
createdAt: 2026-10-07T11:53:32.239Z
---

Kron PAM lets you publish an HTTP or HTTPS device so that users reach it through the container, through the Firefox or Chrome browser, or through both at the same time. You control this behaviour with the **accessOverContainer** parameter on the device. This section explains each option and describes how to enable access through both methods for the same portal.

Every HTTP or HTTPS device that you publish through HTTP Proxy has a **Custom Properties** panel. The **accessOverContainer** parameter in this panel decides where the device opens. The parameter accepts three values:

| ***Value***                | ***Access behavior***                                                                                                        |
| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| **true**                   | The device opens only through the container. It does not appear in the Firefox or Chrome device list.                        |
| **false** (or not defined) | The device appears in the device list and opens through the Firefox or Chrome browser only.                                  |
| **both**                   | The device opens through the container and also appears in the Firefox or Chrome device list. Users can reach it either way. |

When you set **accessOverContainer** to **both**, the same portal stays available through the container and the browser. Users who open the device from the container reach it through Kron PAM, and users who open it from Firefox or Chrome continue to reach it from the browser.



**Enabling Access Through Both the Browser and the Container:**

To let users reach the same HTTP or HTTPS device through both the container and the browser, follow these steps:

1.         **Navigate** to **DeviceManagement** > **Devices**.

2.         **Select** the **HTTP** or **HTTPS** device that you want to publish through both methods.

3.         Open the **CustomProperties** panel of the device.

4.         **Set** the **accessOverContainer** parameter to **both**.

5.         **Save** the **device**.

After you save the device, users can reach it through the container and can also find it in the Firefox or Chrome device list.

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/ZuxM0avf9hmY4ZRTdmbbV_image.png" size="70" caption="Figure – Definition of accessOverContainer parameter in Device -> Custom Properties " isUploading="false" width="725" height="1081" darkWidth="725" darkHeight="1081" showCaption="true"}

When **accessOverContainer** is set to **both**, the device appears in the device list in Firefox or Chrome, and users open it the same way they open any other browser-based device.



When **accessOverContainer** is set to **both**, the device also opens through the container. Kron PAM starts the container session and connects the user to the device.