storage
Required permission
Store data in extension-managed storage areas.
No install warning expected from this entry by itself.
Suggestion
This permission has no install warning and is safe for most extensions.
Build First Tool
Permission Warning Preview
Paste your `manifest.json` and preview the install warnings Chrome may show before a user clicks “Add extension”. This runs locally in the browser and highlights lower-friction alternatives when your permissions are broader than they need to be.
Manifest input
Supports `permissions`, `host_permissions`, `optional_permissions`, and `optional_host_permissions`.
Install warnings
3
Required permissions
5
Optional permissions
2
Install dialog preview
Best-effort preview based on declared required permissions.
Permissions requested
- Read your browsing history.
- Read and change your data on notion.so.
- Read and change your data on github.com.
How to reduce friction
Suggestions are generated from the permissions you requested.
storage
This permission has no install warning and is safe for most extensions.
scripting
Pair this with narrow host permissions instead of `<all_urls>` where possible.
tabs
If you only act on the current tab after a user gesture, use `activeTab` instead.
https://*.notion.so/*
Keep host permissions limited to the exact domains your extension needs.
https://*.github.com/*
Keep host permissions limited to the exact domains your extension needs.
topSites
Move this to `optional_permissions` if it powers a secondary feature.
Permission breakdown
Required permissions affect install warnings. Optional permissions are still listed so you can spot places to defer scary prompts until later.
Manifest v3
low impact
scripting
Required permission
Inject scripts or CSS into pages.
No install warning expected from this entry by itself.
Suggestion
Pair this with narrow host permissions instead of `<all_urls>` where possible.
tabs
Required permission
Read privileged tab fields like URLs and titles across tabs.
Read your browsing history.
Suggestion
If you only act on the current tab after a user gesture, use `activeTab` instead.
https://*.notion.so/*
Required host access
Host access for notion.so.
Read and change your data on notion.so.
Suggestion
Keep host permissions limited to the exact domains your extension needs.
https://*.github.com/*
Required host access
Host access for github.com.
Read and change your data on github.com.
Suggestion
Keep host permissions limited to the exact domains your extension needs.
topSites
Optional permission
Read the user’s most frequently visited websites.
Read a list of your most frequently visited websites.
Suggestion
Move this to `optional_permissions` if it powers a secondary feature.
https://news.ycombinator.com/*
Optional host access
Optional host access for news.ycombinator.com.
No install warning expected from this entry by itself.
Suggestion
Optional host permissions do not show on install and are requested later in-context.
What this catches
- Required API permissions that trigger install-time warnings.
- Broad host access like `<all_urls>` and wildcard domains.
- Optional permissions that can be moved out of the initial install flow.
- Common over-requests where `activeTab` is a better fit.
Next step
Once the permissions look reasonable, you can generate the rest of your listing assets and validate your manifest from the rest of CWS Kit.