Skip to main content
By default a PAL joins Google Meet under a shared Tavus identity, so the Meet tile, lobby, and participant list show that shared name rather than your PAL’s. With whitelabel meeting identity, each PAL you opt in joins from a conferencing subdomain reserved for your organization, and Meet shows the PAL as itself: pal_name as the display name and the PAL’s face thumbnail as the profile picture.
This page is shared with customers under direct enablement. Whitelabel conferencing requires an Enterprise plan, and your Tavus account team may set the subdomain up for you. Reach out to them before enabling it broadly.

What changes

Everything else about meeting attendance works the same way: invite the PAL’s address to a calendar event with a Meet link, or dispatch it to a running meeting with meeting_url. Renaming the PAL or changing its default face updates the Meet profile automatically within a few seconds.

Step 1: Claim your conferencing subdomain in the portal

Your organization needs one conferencing subdomain, claimed once per account. Go to Settings → Organization and SSO → Meeting invites, type the subdomain, and claim it. Only admins can change it, and the section shows an upgrade note on plans other than Enterprise. If your Tavus account team has already set it up, the section shows the domain instead of the claim form.
  • 2+ lowercase alphanumeric characters, dots or hyphens allowed in between. The name is first-come, first-served across all Tavus customers.
  • Claiming sets the domain up and verifies it, which usually takes under a minute. The badge reads Pending verification until then and the page checks every few seconds; if it stays pending, press Verify again.
  • Wait a short moment after verification before creating your first whitelabel PAL. If that first PAL create fails with a provisioning error, retry it after 30 seconds.
  • Release hands the subdomain back. It is refused while any PAL still uses it.

Step 2: Opt a PAL in

The quickest way is the PAL’s Deploy → Google Meet / Zoom / Teams page. Once the subdomain is verified, the Use your custom domain switch is on by default for new invite addresses. For a PAL that already has an address, flipping the switch and saving moves it: the old address is released and calendar invites already sent to it stop working, which the confirmation dialog spells out. From the API, set whitelabel: true on the PAL’s conferencing layer together with its username:
Conferencing layer
On Create PAL this goes under layers; on an existing PAL use Patch PAL:
The response’s conferencing_email (and layers.conferencing.email) is the PAL’s new address, for example anna@acme.cal-invite.com. That is the address to invite, and the account Meet displays.
whitelabel cannot be flipped on a PAL that already has a username. For an existing PAL, first clear the username ("username": null), then set username and whitelabel: true in one update. The PAL’s address changes when you do this, so re-send any calendar invites that were sent to the old @tavusinvite.com address. meeting_url joins are unaffected.

What to expect in Google Meet

  • The tile and participant list show pal_name. A one-word name shows as-is.
  • The profile picture is the PAL’s default face thumbnail. If the face has no thumbnail, Meet shows a default avatar until one is available.
  • Renaming the PAL, changing default_face_id, or publishing a draft with either change updates the Meet profile automatically.
  • The PAL is an external participant from your meeting’s point of view, the same as today: with an Open meeting it joins directly, otherwise a host admits it.

Removing whitelabel

  • Clearing the PAL’s username (or deleting the PAL) retires its meeting identity. It is kept for about ten minutes after removal so that a meeting already in progress can finish.
  • Renaming the username gives the PAL a new address on the same subdomain; the old address stops working, so re-invite it.
  • whitelabel cannot be turned off in place for the same reason it cannot be turned on in place: clear the username first.

Limits and cost

  • Enable whitelabel on the PALs that face your users rather than on every PAL by default.
  • Usernames are unique within your subdomain; PALs that are not whitelabel keep sharing the global tavusinvite.com namespace.
  • The per-plan limit on PALs with a conferencing username applies to whitelabel and standard PALs alike.