Your AI toggles are greyed out, the settings will not stay changed, and the menu says your browser is managed by your organisation. That is Chrome policy at work — here is how it overrules you, what you can legitimately do about it, and why the same system is the strongest off switch on your personal PC.
On a home PC, a settings toggle is the final word. On an office PC it is only a suggestion — and Chrome's AI features are governed by a documented policy system that sits above your settings and wins every argument. If your Help me write toggle is locked on, or a feature you disabled keeps returning on a work machine, this page explains the machinery: how to confirm you are managed, how the policies are structured, and the honest options you actually have.
Before blaming a bug, check whether your toggles are even yours to move:
chrome://policy — any policy listed there is actively controlling your browser right nowIf any of these are true, the behaviour you are fighting is not a glitch. It is a decision someone in IT made, delivered to your browser as policy.
Google documents a full policy system for Chrome's generative AI features. There is one master policy — GenAiDefaultSettings — and a named policy for nearly every feature, including HelpMeWriteSettings, CreateThemesSettings, TabOrganizerSettings, HistorySearchSettings and GeminiSettings.
Each policy takes the same three values in Google's documentation: 0 allows the feature and lets its data improve Google's models, 1 allows the feature but without improving models, and 2 disables the feature completely. One policy line from an admin therefore decides the question for every user on every managed machine.
Chrome applies policy above user settings — deliberately. A policy is re-read at every launch and re-delivered by the organisation's management tools, so even if a setting could be changed, the policy value wins on the next start. That is why the toggles are greyed out: Chrome is not broken, it is being honest that the decision is not yours on this machine.
The same machinery explains a default worth knowing from Google's own documentation: managed browsers start from "allow features, but do not improve models", while consumer Chrome starts from "allow features and improve models". Your office browser is, by default, the more private of the two.
chrome://policy shows exactly what is applied to youHere is the twist most guides miss: the policy system also works for you on a personal Windows PC. Applying the policies yourself makes your choices update-proof, because Chrome treats them as administrator decisions. Advanced users do it like this:
reg add "HKLM\SOFTWARE\Policies\Google\Chrome" /v GenAiDefaultSettings /t REG_DWORD /d 2 /fchrome://policyValue 2 on the master policy switches off the generative AI features it governs, as documented in Google's Chrome policy list. To undo it, delete the value and restart Chrome. Treat this as a power-user route: it is your machine and your decision — but type the command exactly as written.
On your own machine the toggles are all yours — the video shows the complete switch-off, settings page by settings page.
▶️ Watch Full VideoBecause a Chrome policy controls it. Open chrome://policy to see which policies your organisation has applied — if HelpMeWriteSettings or GenAiDefaultSettings is listed, an administrator has set the feature's state, and the settings page locks the toggle to match.
No — not legitimately, and not durably. Policies are re-applied by your organisation's management tools at every launch, and tampering with a managed work PC can breach your employer's IT rules. The working route is a specific request to IT naming the policy and the value you want changed.
In Google's documentation for these policies, 0 allows the feature and lets its data improve Google's AI models, 1 allows the feature but without improving models, and 2 disables the feature entirely. The master policy is GenAiDefaultSettings, with a separate policy available for almost every individual feature.