For Daily Prebuilt,
customIntegrations() returns all currently configured integrations.
There are several options for who can start and stop integrations in a Prebuilt session. See the configuration options below.
You can return active integrations by calling
customIntegrations() on your Daily Prebuilt frame.
Specifies the feature policy for the iframe.
|Specifies who in the call is able to start and stop this integration. |
|Specifies the Content Security Policy for the iframe. |
Please check browser support before using this property - here & here.
|Specifies a publicly available URL to an icon image file associated with the integration.|
|Used to render the integration's name in Prebuilt.|
By default integrations will be loaded lazily.
|Daily supports two different types of custom integrations: |
1. Main call area integrations
2. Sidebar integrations
Indicates which referrer to send when fetching the frame's resource.
A unique policy for the iframe. Applies extra restrictions to the content in the frame.
For more info see https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe#sandbox.
|When configured, it shares the integration's state with other participants in the call: |
- When the integration is started, it will also be started for other participants with whom it is shared.
- When it's stopped, it will stop for all participants with whom it is shared.
The iframe's source URL.
For more info see https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe#src.
Allows you to integrate inline HTML in an iframe.
For more info see https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe#srcdoc
To see if your browser supports this, read here https://caniuse.com/iframe-srcdoc.
Here is an example if you wanted to read the current configuration for a Miro integration: