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.
Properties that can be set at both room and meeting token level
These UI-related properties can be specified at the room level:
UI-related room properties
And these UI-related properties can be configured using meeting tokens:
UI-related meeting token properties
Two properties control what happens when a user leaves a meeting from a standalone browser tab:
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.
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.
There are currently two different "flavors" of UX defaults for Daily rooms: with Daily branding (Free and Launch plan), and without Daily 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 the
- The room's
autojoinproperty is set
To remove Daily branding, upgrade to the Scale plan. The free and Launch plans include Daily branding. (See API pricing plans.)
Here's a table listing the differences between the two different UX variants:
Free and Launch Plan
default: not enabled
top action/branding bar
Powered by Daily
browser warnings displayed
menu bar meeting invite info displayed
help menu/icon displayed
more-menu "shh" mode button
more-menu top branding
Updated about a month ago