Docs Security
Permissions-Policy
Checks that your homepage sends a Permissions-Policy header, which switches off browser features such as the camera or location for your pages.
What it checks
It passes when the homepage response has a Permissions-Policy header with any value. The value is not judged. The older Feature-Policy header does not count.
- PassA Permissions-Policy header is set.
- WarningNo Permissions-Policy header. This is a warning, not a fail.
Why it matters
The header tells the browser which features your page and any frames inside it may ask for, such as camera, microphone, location or payment. If a third-party script or embed is compromised, it cannot ask for a feature you have switched off.
How to fix it
List the features you do not use and give each an empty allow list, so nothing on the page can use them. Leave out the ones you need, for example location on a store finder or camera on a video call page.
Platform notes
Add it with a Transform Rule that modifies response headers.
Use add_header on Nginx or Header set on Apache.
Set it in next.config.js headers, vercel.json, or a Netlify _headers file.
Add it in server config, through your host, or with a security header plugin.
These platforms control the response headers on their own hosting, so there is usually no setting for this header in the site editor. If you need it, ask the platform's support what your plan allows.
Your report shows what this check found on your site. Pro shows the exact fix for your site. See pricing.
Free, about 30 seconds, with every other check included.