Skip to main content
Speaker tags label who said what in meeting transcripts using each participant’s display name. This guide is for workspace admins who want to deploy speaker tags for everyone in their company.

​
What you need per platform

After you deploy the prerequisites, each employee should open Granola and confirm Settings > Preferences > Speaker tags shows Connected for each platform they use. See After deployment below.
The same Chrome extension and macOS Accessibility permission are also used by Granola’s transparency features. If you are already deploying those, you may not need separate steps.

​
Google Meet

macOS Windows Google Meet speaker tags work through the Granola browser extension. Each employee needs the extension installed in the same Chrome or Chromium-based browser profile they use for Google Meet. You can deploy it automatically via Google Admin to your entire organization, or scope it to specific teams using Organizational Units (OUs) or Google Groups.

​
Install the Granola Chrome extension

  1. Sign in to your Google Admin console.
  2. Go to Devices > Chrome > Apps & extensions > Users & browsers.
  3. Click the + (plus) button in the lower right corner and choose Add from Chrome Web Store.
Google Admin console showing the Apps & extensions page with the Add from Chrome Web Store button highlighted
  1. Click Search by ID in the upper right and paste the extension ID: opaadbjlebbbnmjjgdmdllingedoleml
  2. Click Select to add the Granola extension.
Chrome Web Store picker with the Granola extension ID entered in the Search by ID field and the Select button highlighted
  1. Set the installation policy to Force install or Force install + pin to browser toolbar to ensure consistent deployment across your organization.
Installation policy dropdown with "Force install + pin to browser toolbar" selected

​
Scope installation to specific users

By default, the extension applies to your entire organization. To limit it to specific teams, departments, or locations:
Organizational Units let you group users by department, location, or any other criteria and apply policies to each group independently.
  1. In the Google Admin console, go to Directory > Organizational units.
  2. If you don’t already have an OU for the target group, create one.
  3. Move the relevant users into that OU.
  4. Go to Devices > Chrome > Apps & extensions > Users & browsers.
  5. In the left sidebar, select the OU you want to target (instead of the top-level organization).
  6. Add or configure the Granola extension for that OU. Only users in the selected OU will receive the installation.
For more details, see Google’s documentation on viewing and configuring apps & extensions.
If restructuring your OUs isn’t practical, you can target installation via a Google Group instead. This is useful when users span multiple OUs (e.g., a cross-location team).
  1. In the Google Admin console, go to Directory > Groups.
  2. Create a new group (or use an existing one) containing the users who should receive the extension. For example, granola-users@yourcompany.com.
  3. Go to Devices > Chrome > Apps & extensions > Users & browsers.
  4. In the left sidebar, search for and select the group you want to target.
  5. Add or configure the Granola extension for that group. Only members of the group will receive the installation.
For more details, see Google’s documentation on managing group-based policies.
You can combine both approaches — for example, force-install the extension for an OU representing a specific office, and also allow installation for members of a cross-functional Google Group.
The extension requires Google Chrome or another supported Chromium browser (Edge, Arc, Brave). Automated force-install through Google Admin applies to Google Chrome; users on other supported browsers may need to install the extension manually from the Chrome Web Store.
For step-by-step user setup after the extension is deployed, see Speaker tags in Google Meet.

​
Zoom (macOS)

macOS Zoom speaker tags use the Zoom Workplace desktop app and require macOS Accessibility permission so Granola can read participant display names and the active-speaker indicator from Zoom. They do not use the Granola browser extension. Each user must grant Accessibility permission to Granola. On managed Macs, you can pre-grant this via MDM so users never see the permission prompt.

​
About Accessibility access

Accessibility is a macOS system permission that allows apps to read interface elements in other apps. For Zoom speaker tags, Granola uses it to read participant names and the active-speaker indicator shown in the Zoom desktop app. Speaker tags do not use Accessibility access to record your screen, capture audio, or access your camera or microphone.

​
Auto-grant via MDM

Accessibility for Granola can be pre-granted on managed devices so end users never see the macOS permission prompt. The grant is delivered as a Privacy Preferences Policy Control (PPPC) profile pre-approving Granola (team ID QZ7DHHLN25, bundle ID com.granola.app) for the Accessibility service. Below is an example .mobileconfig you can use directly, or adapt as a starting point.
PPPC profiles must be delivered by an enrolled MDM (Jamf, Intune, Kandji, Mosyle, Meraki, etc.) — manual installs appear in System Settings > Profiles but don’t apply the grant. For step-by-step user setup after Accessibility is granted, see Speaker tags in Zoom.

​
Zoom (Windows)

Windows
Zoom speaker tags are not currently available on Windows. Employees on Windows will see Me and Them in Zoom transcripts until Windows support is released.
Google Meet speaker tags work on Windows through the Chrome extension deployment steps above.

​
After deployment

Once you have deployed the extension and/or Accessibility permission, ask employees to:
  1. Open the Granola desktop app (updated to the latest version).
  2. Go to Settings > Preferences > Speaker tags.
  3. Confirm each platform they use shows Connected:
    • Google Meet — connects automatically once the extension is installed in their browser profile.
    • Zoom — may require clicking Set up next to Zoom the first time, even if Accessibility was pre-granted via MDM.
If a row stays disconnected, see the troubleshooting sections in the Google Meet and Zoom user guides.

​
FAQs

For speaker tags, the extension reads active-speaker and participant-name data from Google Meet. It does not access meeting audio, video, or transcripts. (If your workspace also uses Google Meet transparency features, the same extension can send the automated chat notice.)
The browser extension requires Google Chrome or another supported Chromium-based browser (Edge, Arc, Brave).
Not yet. Zoom speaker tags currently require the Zoom Workplace desktop app on macOS with Accessibility permission granted to Granola. Windows support is in development.
The Chrome extension and macOS Accessibility permission are shared with Granola’s transparency features. Deploying them for speaker tags also satisfies those prerequisites. Transparency features have additional workspace settings and, for Google Meet, a pinning configuration — see the admin transparency guides.