How to Allow Channel URLs for Arreya ChromeOS Kiosk Devices (Fixes Geolocation & Weather)

Overview

On auto-launched ChromeOS kiosk devices, browser permissions (including geolocation) are controlled per app, not globally and not per user.

If a channel URL (for example andrew.arreya.com) is not explicitly allowed on the Arreya Device Registration URL app, ChromeOS will return Permission Denied, which can cause features like weather to fail.

This article explains how to correctly add channel URLs so permissions work as expected.

When you need this

You should follow this guide if:

• Weather or location-based features work in a normal browser but fail on ChromeOS kiosks

• Geolocation shows Permission Denied in kiosk mode

• You are using an auto-launched kiosk app

• Customers use custom channel subdomains (e.g. *.arreya.com)

Prerequisites

• Access to Google Admin Console

• Device is enrolled and assigned to the correct Organizational Unit (OU)

• Device uses the Arreya Device Registration URL kiosk app

Step-by-Step Instructions

1. Open Google Admin Console

Go to:

2. Navigate to Apps & Extensions

In the Admin Console sidebar, go to:

3. Select the correct Organizational Unit (OU)

On the left side:

• Click the OU that contains your kiosk devices

• This is critical — settings do not apply across OUs

4. Locate the Arreya Device Registration URL app

In the app list:

• Find Arreya Device Registration URL

• Click the app name to open its configuration

5. Scroll to “Additional URL origins”

Inside the app settings:

• Scroll down until you see Additional URL origins

This section controls which external URLs are allowed to run with the kiosk app’s permissions (including geolocation).

6. Add your channel URLs

In Additional URL origins, add each channel domain on its own line.

Example:

Important notes:

• Use https:// (HTTP will not work)

• Include subdomains explicitly

• Wildcards (*.arreya.com) are recommended if you use many channels

7. Save the configuration

• Click Save in the top-right corner

• Wait for the policy to apply (usually a few minutes)

8. Reboot the kiosk device

On the physical ChromeOS device:

• Reboot the device (power cycle or remote reboot)

• Allow the kiosk app to auto-launch again

Verification

After reboot:

• The kiosk should load the channel normally

• Weather and other location-based features should now render

Why this works

Auto-launched kiosk apps operate at the device level.
ChromeOS requires explicit URL origin approval per kiosk app to grant permissions like geolocation. Global settings alone are not sufficient.