Enrolment
5 TopicsUpdate: Device Enrollment Limits - OU Level
Hi everyone, Back in November, we introduced the Device Enrollment Limits TT, designed to help admins better manage ChromeOS license consumption by setting enrollment caps at the Organizational Unit (OU) level. Since then, the feature has continued to evolve, so I wanted to share a quick update with what’s changed. A quick recap LimitOU (Device Enrollment Limits) allows IT Admins to set specific device enrollment caps at the Organizational Unit (OU) level. This prevents a single OU from exhausting the organization's total license pool. What’s new? Delegated admin support - Originally a Superadmin-only tool during the Q3 2025 Trusted Tester (TT) phase, the feature now supports delegated permissions. The Help Center for the TT has been updated accordingly. Granular control - Admins can now manage enrollment limits without requiring full system-wide administrative privileges. Allowlist Requirement: Due to the complexity of the Admin Console integration, the feature requires manual enablement for specific customer domains so members can just respond to the post and request to be added to this trusted tester if they wish. How to Apply Once more, if you are an administrator and would like to be included in this Trusted Tester program to try out Device Enrollment Limits and provide valuable feedback, please simply post a comment below to express your interest!34Views1like0CommentsFrom setup to scale: your experiences with ChromeOS automatic enrollment
Hi everyone, Automatic enrollment can be a real game changer when you’re deploying at scale — whether that’s ChromeOS zero-touch enrollment for new devices or ChromeOS Flex remote enrollment for existing fleets. I’d love to hear how it’s been working for you in the real world: What did your rollout look like (drop-ship to users, office-based, hybrid, global)? What’s one tip or best practice you’d share with someone setting up their next automatic enrollment deployment? If you’ve used both ChromeOS zero-touch and ChromeOS Flex, what factors usually influence your decision in practice? If useful, we’ve got a great community guide on ChromeOS enrollment essentials and an informative ChromeOS Flex case study that’s worth a read too! Looking forward to learning from your experiences 👀 Speak soon, Rafa42Views1like0CommentsCustom Protocol Handler for Isolated Web App Not Working After ChromeOS Update (May be).
Hello, After my ChromeOS device updated on September 25, 2025 (though not certain this is the direct cause), custom protocol handlers (web+collab:// and collab://) for my Isolated Web App (IWA) stopped working. Triggering these links in Chrome no longer launches the app—they simply do nothing. This was functional until two days ago. App Type: Isolated Web App (IWA) Manifest excerpt: { "name": "someapp", "id": "/", "short_name": "some-app", "version": "0.1.0", "update_manifest_url": "https://github.com/--some-repo--/iwa-release/releases/latest/download/update.json", "icons": [ { "src": "/192x192.png", "sizes": "192x192", "type": "image/png", "purpose": "any maskable" }, { "src": "/144x144.png", "sizes": "144x144", "type": "image/png", "purpose": "any maskable" } ], "start_url": "/", "scope": "/", "display": "standalone", "display_override": ["borderless"], "background_color": "#ffffff", "theme_color": "#3B82F6", "isolated_storage": true, "permissions_policy": { "cross-origin-isolated": ["self"], "direct-sockets": ["self"], "controlled-frame": ["self"], "window-management": ["self"], "display-capture": ["self"], "all-screens-capture": ["self"] }, "protocol_handlers": [ { "protocol": "web+collab", "url": "/?data=%s" }, { "protocol": "collab", "url": "/?data=%s" } ], "launch_handler": { "client_mode": "navigate-existing" }, "window_controls_overlay": { "enabled": true } } Recent Changes Enrolled new users in Google enterprise Updated the app manifest (see above) ChromeOS device updated on 2025-09-25 Observed Behavior Protocol links for both my IWA (web+collab://) and the official ChromeOS IWA SINK app (web+cf://) no longer launch the installed apps No errors, warnings, or manifest validation issues Clicking protocol links does nothing (both in managed and unmanaged device states) What I've Tried Checked manifest and protocol handler registration Tested after app reinstall and in different device policy states Reviewed enterprise Admin Console for new/relevant policy changes Searched for protocol handler or IWA-related changelogs/updates Compared behavior with different protocol URLs and schemes Questions Is anyone else experiencing protocol handler breakages for IWAs since a recent Chrome/ChromeOS update? Have there been changes in policy, manifest format, or handler registration that could affect this? Any ideas or diagnostics for discovering if Chrome or policy is blocking/ignoring the protocol? Any leads, recent experiences, or possible workarounds would be greatly appreciatedSolved263Views1like5Comments