optional_permissions
Type | Array |
---|---|
Mandatory | No |
Manifest version | 2 or higher |
Example |
json
|
Use the optional_permissions
key to list permissions you want to ask for at runtime, after your extension has been installed.
The permissions
key lists permissions that your extension needs before it can be installed. In contrast, optional_permissions
lists permissions that your extension doesn't need at install time but can ask for after installation. To ask for a permission, use the permissions.request()
API. Asking for a permission presents the user with a dialog requesting them to grant the permission to your extension, unless all the permissions requested are granted silently.
For advice on designing your request for runtime permissions, to maximize the likelihood that users grant them, see Request permissions at runtime.
Starting with Firefox 84, users can manage optional permissions from the Firefox Add-ons Manager. Extensions that use optional permissions can check for the permissions granted by the user with permissions.getAll()
and listen for permissions.onAdded
and permissions.onRemoved
to know when a user grants or revokes permissions.
The key can contain host permissions and API permissions.
Host permissions
These are the same as the host permissions you can specify in the permissions
key.
Note:
When using Manifest V3 or higher, optional host permissions should be specified using the optional_host_permissions
manifest key. Firefox introduced optional_host_permissions
in release 128, see bug 1766026, and allows the continued use of optional_permissions
to specify optional hosts. Use of optional_host_permissions
, however, is recommended.
API permissions
The optional API permissions are:
activeTab
background
bookmarks
browserSettings
browsingData
clipboardRead
clipboardWrite
contentSettings
contextMenus
cookies
debugger
declarativeNetRequest
declarativeNetRequestFeedback
declarativeNetRequestWithHostAccess
devtools
downloads
downloads.open
find
geolocation
history
idle
management
nativeMessaging
notifications
pageCapture
pkcs11
privacy
proxy
scripting
search
sessions
tabHide
tabs
topSites
webNavigation
webRequest
webRequestBlocking
webRequestFilterResponse
webRequestFilterResponse.serviceWorkerScript
Check the compatibility table for browser-specific support details.
These optional permissions are granted silently, without a user prompt:
activeTab
cookies
idle
webRequest
webRequestBlocking
webRequestFilterResponse
webRequestFilterResponse.serviceWorkerScript
Optional-only permissions
Optional permissions are generally available for use in the permissions
key so they can be requested at install time. However, some browsers support the concept of optional-only permissions, permissions that can only be requested at runtime using the permissions.request()
API. In addition, optional-only permissions must be requested individually and alone through the permissions.request()
API.
Note: No optional-only permissions were generally available at the time of writing, December 2024.
Examples
"optional_permissions": ["*://developer.mozilla.org/*"]
In Manifest V2 only, enable the extension to ask for privileged access to pages under developer.mozilla.org.
"optional_permissions": ["tabs"]
Enable the extension to ask for access to the privileged pieces of the tabs
API.
"optional_permissions": ["*://developer.mozilla.org/*", "tabs"]
In Manifest V2 only, enable the extension to ask for both of the above permissions.
Browser compatibility
BCD tables only load in the browser