CSP and Permissions-Policy
What your page's own Content-Security-Policy and Permissions-Policy must allow for the player, and why.
Content-Security-Policy
If your page sends a Content-Security-Policy, add these sources to it. Nothing of the player runs in your page's own origin except the SDK itself (a bundled jami3d, or the CDN build) and its facade.
| Directive | Add |
|---|---|
script-src | https://cdn.jami.live |
style-src | 'unsafe-inline' |
img-src | https://cdn.jami.live |
connect-src | https://embed.jami.live |
frame-src | https://embed.jami.live |
A page that only embeds the player, with the CDN build, could send:
Content-Security-Policy: default-src 'self'; script-src 'self' https://cdn.jami.live; style-src 'self' 'unsafe-inline'; img-src 'self' https://cdn.jami.live; connect-src 'self' https://embed.jami.live; frame-src 'self' https://embed.jami.live
Permissions-Policy: microphone=(self "https://embed.jami.live"), autoplay=(self "https://embed.jami.live"), fullscreen=(self "https://embed.jami.live"), clipboard-write=(self "https://embed.jami.live"), xr-spatial-tracking=(self "https://embed.jami.live")frame-src— the Live Room's iframe, on the embed host.connect-src— the facade reads the project's card from the embed host before anything mounts.img-src— the poster the facade shows comes from the CDN.script-src— only when the page loads the CDN build; a bundledjami3dis your own script. The script that callscreatePlayeris yours too: allow it as your policy allows your other scripts — from a file under'self', as the example assumes, or inline with its hash or a nonce.style-src 'unsafe-inline'— the facade draws itself in a shadow root with its own<style>element, so your page's styles never reach it.
Which pages may frame the player
Your page's own frame-ancestors is about who may frame your page. Who may frame the player is your publishable key's list of origins: the embed host turns it into the player's frame-ancestors, and every ancestor must be on it — an LMS that frames your page that frames the player means both origins on the key. A keyless embed may be framed anywhere only when the project's owner allows keyless embeds.
Permissions-Policy
The SDK gives the iframe what it may use through its allow attribute — microphone (voice), autoplay, fullscreen, clipboard-write and xr-spatial-tracking — and never a sandbox. If your page sends a Permissions-Policy, it must let the embed host have the same features, or Chromium blocks them inside the iframe whatever the attribute says: microphone=(self) alone, for one, turns voice off.
To keep a feature from the player instead, say so to the SDK: allow: { voice: false, fullscreen: false } leaves it out of the iframe's allow, and the player hides what needs it.