ChromeOS and ChromeOS Flex provide a secure, stable, and highly manageable platform for deploying digital signage at scale. By using the Google Workspace Admin Console, you can remotely install and configure the OnSign app across multiple devices, through an easy and centrally managed setup.
For added security, ChromeOS supports Kiosk Mode, which allows OnSign to run in full-screen mode while preventing users from exiting the application or accessing other parts of the operating system.
This makes it an ideal solution for unattended or public-facing displays.
OnSign is implemented as a PWA app, meaning it is compatible and can be fully managed by all recent ChromeOS devices.
In this tutorial, we’ll guide you through the steps to install and run OnSign on ChromeOS and ChromeOS Flex devices using the Admin Console.
Requirements -
Here are a few things you will need to install OnSign on your ChromeOS devices:
- A Google Workspace Account(workspace.google.com) is required as all settings are executed in the Google Admin Console(admin.google.com). In case you don’t have an account yet, you can
set a free trial account directly at Google. - You will need a ChromeOS or ChromeOS Flex device.
- You will need to purchase from Google a Kiosk & Signage Upgrade license for each ChromeOS device that gets connected to your Google Workspace. More info at https://support.google.com/chrome/a/answer/1360534?hl=en
Organizational Units
Now that you're logged into your Google Admin Console, the first step is to configure what’s called an Organizational Unit (OU). An OU is essentially a group that lets you apply policy settings to all devices assigned to it.
If all your devices will use the same installation and configuration settings, a single Organizational Unit is likely sufficient. However, if different sets of devices require different policies, you can create multiple hierarchical Organizational Units to better organize and manage your network.
Setting Up OnSign in the Google Admin Console
Now let’s configure the rules required for OnSign to be automatically installed and run in Kiosk Mode. Note this setup only needs to be done once, as any new device added to the Organizational Unit will automatically follow the same configuration.
- Sign in using an administrator account to Google Admin (https://admin.google.com/).
- Go to Menu Devices → Chrome → Apps & extensions → Kiosks
- Go to Add and select Add by URL.
- Enter https://chromeos.onsign.com and then Save.
- Click the newly added “OnSign Chrome OS Player” from the list. This will open a panel on the right side of the screen.
- Make sure the following settings are correctly set:
- Installation Policy: Installed
- Allow App to Manage Power: Enabled
- Web app can run offline: Enabled
- Click “Add Extension” → “Add from a custom URL” under the Extensions section
- Click “From the Chrome Web Store” dropdown menu, and select “From a custom URL”
- Enter “nhfheignagcldfgfjbcmkhidblkjpnfo” (without quotes) in the Extension ID field
- Enter https://chromeos.onsign.com/extension/updates.xml in the URL field
- Close the side panel
- At the top of the list beside “Auto-launch app”, select “OnSign Chrome OS Player”
Additional Settings
While OnSign installation policies are already in place, additional settings are required to ensure OnSign has access to all ChromeOS recourses and settings:
- Go to Devices → Chrome → Click the “Device Settings” tab
- Scroll down and set the
- “Enterprise Hardware Platform API” to : Allow managed extensions to use the Enterprise Hardware Platform API
- Scroll down once again and search for “AC Kiosk power settings” and set:
- "Action on idle" to → Do nothing
- "Screen dim timeout (in minutes)" to → 0
- "Screen off timeout (in minutes)" to → 0
Device sleep mode (Optional)
This works analogous to OnSign Working Hours feature and can be used instead of the "Turn Screen Black" option. It will define a recurring weekly schedule for managed ChromeOS devices to automatically enter sleep mode and wake up at specific times.
The device will go to sleep at the start of the scheduled interval and wake up at the end of the interval. It is only supported on devices running ChromeOS version 125 or higher.
Before you set this policy, the "Action on idle" setting for "Battery Kiosk power settings" and "AC Kiosk power settings" must be set to "Do nothing".
Important
- Do not overlap intervals - Overlapping sleep intervals are not supported. If any two intervals overlap, the entire schedule will be ignored.
- Time zone behavior- Sleep and wake times follow the device’s local time zone.
- Delayed actions - If the device is asleep when a scheduled action (like a reboot) is supposed to occur, the action will run after the device wakes up.
More info on ChromeOS
How to Enroll Devices |
Zero-touch Enrollment |