Documentation

How MeetingBrand connects to each platform, what your employees see, and how to remove it. Written for the admin who connects the platform and for IT.

Getting started

  1. Create MeetingBrand — open the builder, enter your company domain; review the logo, colors, scenes and sign treatments; set the name bar fields (name, title, department, company). The builder runs in your browser; nothing is stored on our servers during early access.
  2. Connect a platform — Integrations → choose Zoom, Microsoft Teams, Google Meet or Zoho Meeting → sign in as an administrator and approve the permissions listed below. MeetingBrand then imports your people (name, email, title, department). Integrations are rolling out to early-access customers platform by platform; write to support@meetingbrand.com to be scheduled.
  3. Assign and deploy — mark people or departments as active, choose their looks, and deploy. The People panel shows each person's status: delivered, waiting for a restart, needs the employee's one click, or blocked (with the reason).

Zoom

Permissions requested (admin-managed app): list users; upload and delete virtual background files for users; read and update account settings related to virtual backgrounds. A Zoom account owner or admin authorizes once for the whole account; employees see no prompt.

What happens: each active employee's branded background is uploaded into their own Zoom virtual-background library (Zoom allows up to 10 files per user; we manage ours). After the upload the employee signs out and back in to Zoom, opens Settings → Video & effects → Virtual backgrounds and picks the branded image once — Zoom remembers it. Admins can additionally turn on "Require users to always use virtual background" and disable personal uploads so the branded image is the only non-stock choice.

Removing MeetingBrand: Zoom App Marketplace → Manage → Added Apps → MeetingBrand → Remove. MeetingBrand deletes the background files it uploaded and the directory data it synced for that account within 30 days (immediately on request to support@meetingbrand.com).

Microsoft Teams

Permissions requested (Microsoft Entra ID, multitenant): User.Read.All (application) to read your directory — names, emails, job titles, departments — plus sign-in for the admin. A tenant administrator grants consent once; employees see no prompt.

What happens: Teams has no API for meeting backgrounds, so delivery goes to the employee's device. Choose one: (a) IT scripts — MeetingBrand generates an Intune platform script (Windows) and a shell script (macOS/Jamf) that place the person's background in the new-Teams gallery folder; (b) the MeetingBrand agent, a small signed helper installed from the employee's personal link. After Teams restarts, the branded image appears under Effects and avatars → Backgrounds; the employee selects it once and Teams keeps it. Tenants with Teams Premium can instead upload our images in the Teams admin center and set them as required per department — we generate the images and the policy assignment script.

Removing MeetingBrand: Entra admin center → Enterprise applications → MeetingBrand → Delete (revokes our access). Delete the gallery files with the uninstall script we provide, or remove the agent from Add/Remove programs (Windows) or the Applications folder (macOS).

Google Meet

Permissions requested: View users on your domain (Admin SDK Directory, read-only) to import names, emails, titles and departments. A Google Workspace administrator with the Users › Read privilege authorizes once.

What happens: Meet has no API for backgrounds. MeetingBrand produces the JPEG images (Meet's required format, 1920×1080) and a step-by-step runbook for the Admin console (Apps → Google Workspace → Google Meet → Meet video settings → Visual effects → custom images per organizational unit, up to 15). Employees then find the images in their Backgrounds panel. For managed Chrome browsers, the MeetingBrand Chrome extension (force-installed from the Admin console) applies the person's background automatically.

Removing MeetingBrand: Google Admin → Security → API controls → Manage third-party app access → MeetingBrand → Remove; remove the custom images from Meet video settings; remove the extension from the Chrome force-install list.

Zoho Meeting

Permissions requested: ZohoMeeting.manageOrg.READ, ZohoMeeting.user.READ, ZohoMeeting.department.READ — to identify the organization and import its members. A Zoho Meeting organization admin authorizes once.

What happens: Zoho Meeting has no API or admin control for virtual backgrounds, so each employee receives a personal link and email with their background and four steps: turn on Virtual Background under Settings → My Settings, open the join page, choose "Select your background", upload the image and pick it. Zoho then uses it for all future meetings. Custom backgrounds are available on Zoho Meeting Standard and Professional editions.

Removing MeetingBrand: Zoho Accounts → Security → Connected apps → MeetingBrand → Revoke. Employees can delete the image from their own background list.

Data and security

  • We store: admin account details, the directory fields above, the OAuth tokens needed to keep your connection alive (encrypted at rest), your brand assets and the rendered background images.
  • We never read meeting content, recordings, chats or calendars.
  • Disconnecting a platform deletes its synced data; you can request full deletion at any time at support@meetingbrand.com.
  • Full details: Privacy policy · Terms of service.