Set Gooroom Browser Isolation Through Your Organization’s Policy

An internal portal opening in the wrong Gooroom browser, or an external site being blocked, usually points to a browser trust policy rather than a normal browsing preference. Gooroom’s browser protection routes sites through trusted or untrusted browser processes. In Hancom Gooroom deployments, the vendor describes GPMS as a central settings-management platform and says Gooroom Browser applies different policies by destination; see the Hancom Gooroom product page. Ordinary users may need an administrator to change a site’s classification. As of October 9, 2026, the public vendor material does not show a current click-by-click GPMS menu path, so use the manual for your specific deployment instead of guessing.

What does Gooroom browser isolation control?

Gooroom Browser is a Chromium-based browser with separate trusted and untrusted browsing processes and policies that can differ by destination. The distinction is part of the Gooroom security design; it is not the same as choosing a privacy mode or changing a site permission such as camera access. Hancom describes this browser protection as applying policies based on access destination, including different handling for trusted and untrusted browsing. Its product page also describes GPMS as a way to manage device settings centrally.

“Gooroom OS” can refer to different editions or deployments. Hancom Gooroom and an organization’s upstream Gooroom-based image may not expose the same management tools or menus. The public product information confirms the policy model, but does not publish the current GPMS navigation, policy field names, or a universal end-user toggle. The steps below therefore focus on a safe configuration workflow rather than invented button names.

The four interface panels below are explanatory illustrations, not screenshots from a specific Gooroom release. The sample site classifications are not defaults for your organization.

Before changing a browser policy

First identify the installed edition and release, and whether the computer is organization-managed. Record this information from the system’s About or system-information view if available. If GPMS is not present or you do not have an administrator role, ask the device administrator to confirm the supported policy route. Do not try to edit browser policy files or Chromium flags as a substitute; those changes may not control Gooroom’s separate browser protection and could conflict with the managed policy.

Prepare a short list of sites that need different handling. Include each service’s hostname and the business reason it needs to be trusted. A sign-in flow may redirect across several organization-controlled hostnames, so ask the service owner which destinations are required. Do not classify an entire public domain as trusted just because one page is needed.

How do you configure the policy safely?

1. Confirm the policy owner. If your device is managed, send the edition, release, affected site, and the behavior you expected to your IT or security administrator. For a Hancom Gooroom device, ask whether that deployment uses GPMS for Gooroom Browser policies. If you administer a different Gooroom image, use that image’s own management guide.
2. Agree on the site classification. Have the policy owner decide whether the exact host belongs in the trusted or untrusted process. Keep unknown and public sites in the organization’s untrusted handling unless the security owner approves a specific exception. Separate the site’s trust classification from other controls, such as whether downloads are allowed; the publicly available product page does not specify those detailed policy fields.
3. Apply the change using the matching admin guide. An authorized administrator should use the GPMS or management method documented for the installed release, apply the approved host rule to the intended user or device group, and avoid broadening the rule beyond the requested service. Because the public documentation does not show the current console path or policy syntax, stop and request the deployment guide or vendor support if the relevant control is not clearly identified. Do not copy menu names from another Gooroom release.
4. Test on one managed device first. After the administrator reports that the policy has been applied, close and reopen Gooroom Browser if the deployment instructions require it. Test one approved internal site and one approved untrusted test destination. Do not use a live malicious site to test isolation.

What if a site still opens in the wrong browser?

Capture the exact address after redirects, the window or browser that opened, the device edition and release, and the time of the test. Give those details to the policy administrator so they can check the assigned rule and whether it reached the device. A missing redirect host or a rule applied to the wrong device group can explain a mismatch, but the administrator should verify that against the deployment’s policy records.

If the site is blocked, do not add it to the trusted list just to get past the block. First confirm with the service owner that the address is legitimate and required, then ask the security administrator to choose the narrowest approved exception. If the expected browser indicator or management status is not visible, use the verification method in your Gooroom release’s documentation; the public sources do not define one universal status page.

How can you confirm the change worked?

Ask the administrator to confirm that the new rule is assigned to the correct device or user group. Then verify that the approved work site opens in the trusted browser process and the untrusted test destination remains in the untrusted process, using the indicators documented for your deployment. If either destination is handled differently, report the final URL and stop expanding the trusted list until the rule has been checked.