For a fully custom UI, please see createCallObject() or our blog post about React.

Room and meeting token properties

Many parts of the in-call experience can be customized by changing room or meeting token properties.

The following UI-related properties can be set at the room level, or using a meeting token. If a property is set for the room and also set in the meeting token, the meeting token setting takes precedence.

These UI-related properties can be specified at the room level:

And these UI-related properties can be configured using meeting tokens:

UI flows when a user leaves a meeting

Two properties control what happens when a user leaves a meeting from a standalone browser tab: close_tab_on_meeting_exit and redirect_on_meeting_exit.

If close_tab_on_meeting_exit is set to true, the browser tab closes when the user clicks the leave meeting button in the in-call menu bar.

If the redirect_on_meeting_exit property is set, the property value will be interpreted as a URL that the browser should redirect to when the user clicks the leave meeting button. A query string that includes the parameter recent_call=<domain>/<room> is appended to the URL.

📘

By default, there is no leave meeting button in the iframe embedded UI; you control that meeting flow with your own UI code outside the iframe. Or you can add a leave call button to the embedded UI with our Javascript API.

API plan level, and Daily.co branding

There are currently two different "flavors" of UX defaults for Daily.co rooms: with Daily.co branding (Free and Launch plan), and without Daily.co branding (Scale plan).

This applies to all of the following cases:

• The room was created by an API call,
• The call UI is embedded in an iframe,
• The call was joined via a URL that includes a meeting token
• The call was joined via a URL that includes theautojoin query parameter.
• The room's autojoin property is set

To remove Daily.co branding, upgrade to the Scale plan. The free and Launch plans include Daily.co branding. (See API pricing plans.)

Here's a table listing the differences between the two different UX variants: