Ignored because the policy is not set by a cloud source.
--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/6e03660c-be88-48f5-94bc-0a2bb57a674cn%40chromium.org.
Hello
I’ve reviewed the issue where the ChromeBrowserEnterprise policy isn’t visible in the Google Admin Console and can’t be configured via MDM. Here’s what I’ve found:
1. This policy only takes effect when devices are fully Enterprise-enrolled (Cloud Policy Provider enabled).
2. In the Admin Console, it’s visible for Enterprise (Plus) and Education editions; lower-tier subscriptions may not display it.
3. MDM won’t apply this policy until Chrome is connected to Cloud Enrollment, hence the “Policy not set by cloud source” error.
4. Neither Registry nor API access works until the policy’s source is the cloud.
Recommendations:
• Confirm all devices are Enterprise-enrolled under Chrome Enterprise (Admin Console > Device Management > Chrome Enterprise > Enrollment).
• Use the Chrome Policy API Explorer to verify if ChromeBrowserEnterprise is supported in your subscription tier.
• Update Chrome to the latest Stable Channel (e.g., v115+).
• If the policy still doesn’t appear, you may need an Enterprise Plus or Education license—please contact Google Workspace Sales or Support.
To explore alternative solutions (e.g., combining other policies or an extension-based workaround), please share:
1. The exact goal of this policy (which settings you need).
2. Your Google Workspace or Chrome Enterprise license type.
3. The specific Chrome Browser version on your clients.
With that info, I can suggest the most effective approach quickly.
Thank you and best regards,
Amir zavelghorba
Yes; im all in for joining this project.
Please let me know how i can be of assistance.
Thank You.
Thank you all for your prompt and generous offers to assist. I’m truly grateful for your willingness to help. A special thanks to Amir Zavelghorba for providing potential solutions.
To ensure we're all on the same page, I'd like to clarify the specific challenge I'm facing.
My objective is to programmatically enable the 'CloudExtensionRequestEnabled' Chrome policy for my client organizations.
Currently, I'm using the Chrome Policy API and the Google Admin API to manage Chrome browsers for our clients. This setup successfully addresses all our required use cases except for one.
The final requirement is to allow end-users to request browser extensions they'd like to use. This is controlled by the CloudExtensionRequestEnabled policy. When this policy is active, users can browse the Chrome Web Store, install pre-approved extensions, and submit a request for any extension that has not yet been approved. The administrator can then review and approve or deny these requests. I'm attaching screenshots from the Chrome Webstore to illustrate the end-user extension approval flow.
While this policy can be manually enabled through the Google Admin console (as shown in the attached screenshot), my goal is to automate this process for our clients via an API. So far, I have not found a way to set the CloudExtensionRequestEnabled policy using the Chrome Policy API or a similar programmatic method.
I hope this clarifies the issue.
Thank you again for your support. I welcome any ideas or suggestions you might have.
Best regards,