Build a Permissions-Policy header to decide which browser features — camera, microphone, location, payments, USB, fullscreen and more — your site and any embedded iframes may use. Start from a recommended lockdown, adjust each feature, and copy the header with ready-to-paste Nginx and Apache lines.
| Value | Meaning |
|---|---|
| camera=() | Disabled everywhere |
| camera=(self) | Your origin only |
| camera=(self "https://a.com") | Your origin and a.com |
| camera=* | Any origin |
The feature is disabled for your page and every iframe.
It replaced Feature-Policy and uses a different syntax.
To let a cross-origin iframe use a feature, the header must allow its origin and the iframe needs allow.
No. Browsers ignore names they don't recognize.
It includes the 30 most relevant; you can untick ones you don't want in the header.
Each feature gets an allowlist written in the structured-header syntax the specification uses: feature=() disables it for the page and all embedded frames, feature=(self) allows only your own origin, feature=* allows any origin, and feature=(self "https://maps.example.com") adds specific origins, which are normalized to scheme://host[:port] and quoted while self is not. Directives are joined with commas. A matching iframe allow attribute is produced (in its own syntax, 'self' and bare origins separated by semicolons) for delegating features to embeds. The recommended preset disables powerful features such as camera, microphone, location, USB and the Topics API while keeping fullscreen, autoplay, clipboard-write and passkeys for your own origin.