How to fix missing permissions policy on Webflow

Steps for Webflow

1. Webflow does not expose HTTP header configuration natively in its hosting dashboard for standard plans.
2. For Webflow Enterprise, contact support or use the site settings to configure custom headers if available in your plan.
3. For all other plans, use Cloudflare as a proxy: add your Webflow site's domain to Cloudflare → Rules → Transform Rules → Modify Response Headers → Add header 'Permissions-Policy' with value 'camera=(), microphone=(), geolocation=(), payment=(), usb=()'.
4. Alternatively, in Webflow Designer → Project Settings → Custom Code → Head Code, add: <meta http-equiv='Permissions-Policy' content='camera=(), microphone=(), geolocation=()'> as a partial browser hint.
5. Verify with Chrome DevTools → Network → Response Headers.

Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=(), fullscreen=(self)

What is missing permissions policy?

The Permissions-Policy header (formerly called Feature-Policy) is a security instruction your web server sends to every visitor's browser. It acts like a bouncer's list for powerful browser features — it tells the browser exactly which features your site is allowed to use, and blocks everything else. For example, you can declare that your store never needs access to a visitor's camera, microphone, or precise location, so even if malicious code was somehow injected into your page, the browser would refuse to grant that access. Without this header, browsers apply loose default rules, leaving those features potentially available to any script running on your pages.

Missing this header is flagged under OWASP A05:2021 (Security Misconfiguration) — one of the most common vulnerability categories found on real sites. If third-party scripts (ad networks, chat widgets, analytics) or injected malicious code try to silently access a shopper's camera, microphone, or location, nothing at the browser level stops them without this header. For an ecommerce store, that is a direct privacy and trust risk: a single reported incident of covert data capture can destroy customer confidence and trigger GDPR/CCPA regulatory scrutiny. Adding this header is a low-effort, high-signal security hardening step that security auditors and increasingly Google's ranking systems look for as a mark of a trustworthy site.

See the complete Missing permissions policy guide for every platform and the full background.