When a Chrome extension update adds a permission that carries a warning, Chrome disables the extension until you accept the new permission. That prompt is one of the few moments you get to review a change. Do not click through on reflex. Ask why the permission is needed.
What Chrome does
Google's permission warnings page says an extension that adds a warning permission "will be disabled until the user accepts the new permission," and describes a dialog asking the user to approve it. Google's publishing guide says the same from the developer side: if an update needs more permissions, users are prompted to accept them or disable the extension.
One wrinkle: the documentation uses both "will be disabled" and "may temporarily disable" in different places. The safest reading is that you should expect a prompt and treat it as important either way.
Why this moment matters
A popular extension can change hands or change direction. A tool that began with narrow access can ask for all sites later. Permissions that already carried warnings are not asked again, so the prompt is a rare signal. Notice that only permissions with warnings trigger it. Not every new capability does, so a clean update is not proof nothing changed.
How to decide
Ask three questions:
- Does the new permission match a new feature? A new "read and change data on all sites" request for a feature that obviously does not need it is a bad sign.
- Could it use a narrower option? Many features work with activeTab or specific sites. See what activeTab means.
- Did the listing change too? Check the developer name, the description and the reviews for mentions of recent changes.
If the answers are unclear, decline, leave the extension disabled, and look for the developer's explanation. Removing a disabled extension costs you little.
For teams
If you manage browsers with policy, you can block extensions that request certain permissions, which gives the decision to the administrator and not each user. The admin policy options cover this.
For developers
Fewer warnings means fewer interrupted users and a smaller blast radius. Request extra access at runtime when a user turns on a feature, using optional permissions.
Common mistakes
People approve the prompt because the extension is already installed and they want it back. Treat the prompt like a fresh install. Another mistake is ignoring a disabled extension, since an unmanaged one lingers and may be re-enabled later by someone who does not know why it was off.
Quick check
Do I get a prompt for every new capability an update adds?
No. Google's page describes the prompt for permissions that carry a warning. Other changes can arrive without one.
Is it safe to approve if the extension is popular?
Popularity does not tell you the reason for the new access. Check the new permission against the new feature first.
Sources
Last reviewed: 19 October 2026.
