Set up speaker tags for your team (Admin Guide)

Speaker tags show participant names in meeting transcripts. They are available for Google Meet, Zoom, and Microsoft Teams on macOS and Windows. Accessibility supports speaker tags across all three meeting apps: Google Meet in Google Chrome, and the Zoom and Microsoft Teams desktop apps. The Granola Chrome extension also supports Google Meet speaker tags on macOS and Windows.

macOS Accessibility

Grant Granola Accessibility permission for Google Meet in Chrome, Zoom, and Teams. One grant covers all three; employees who have already granted it do not need to repeat setup. Employees can grant access in System Settings > Privacy & Security > Accessibility, or you can pre-grant it on managed Macs via MDM. For speaker tags, Granola uses Accessibility to read participant names and active-speaker information from the meeting app’s interface. See the speaker tags privacy details.

Pre-grant via MDM

macOS 27 changed how Accessibility is granted through MDM, so deploy both configurations below. Each Mac applies the one for its macOS version.

macOS 26 and earlier
macOS 27 and later

Deploy a Privacy Preferences Policy Control (PPPC) profile pre-approving Granola (team ID QZ7DHHLN25, bundle ID com.granola.app) for the Accessibility service. You can use this example or adapt it for your MDM:

allow-granola-accessibility.mobileconfig

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>PayloadContent</key>
    <array>
        <dict>
            <key>PayloadDescription</key>
            <string>Grants Granola the macOS Accessibility permission so it can read speaker information from Google Meet, Zoom, and Microsoft Teams for speaker tags without prompting the user.</string>
            <key>PayloadDisplayName</key>
            <string>Privacy Preferences Policy Control</string>
            <key>PayloadIdentifier</key>
            <string>ai.granola.allow-granola-accessibility.pppc</string>
            <key>PayloadOrganization</key>
            <string>Granola</string>
            <key>PayloadType</key>
            <string>com.apple.TCC.configuration-profile-policy</string>
            <key>PayloadUUID</key>
            <string>78540A61-F502-4D5A-AD6C-7FB1782239D5</string>
            <key>PayloadVersion</key>
            <integer>1</integer>
            <key>Services</key>
            <dict>
                <key>Accessibility</key>
                <array>
                    <dict>
                        <key>Allowed</key>
                        <integer>1</integer>
                        <key>CodeRequirement</key>
                        <string>identifier "com.granola.app" and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = QZ7DHHLN25</string>
                        <key>Comment</key>
                        <string></string>
                        <key>Identifier</key>
                        <string>com.granola.app</string>
                        <key>IdentifierType</key>
                        <string>bundleID</string>
                        <key>StaticCode</key>
                        <integer>0</integer>
                    </dict>
                </array>
            </dict>
        </dict>
    </array>
    <key>PayloadDescription</key>
    <string>Grants Granola the macOS Accessibility permission so it can read speaker information from Google Meet, Zoom, and Microsoft Teams for speaker tags without prompting the user.</string>
    <key>PayloadDisplayName</key>
    <string>Allow Granola Accessibility (Speaker Tags)</string>
    <key>PayloadIdentifier</key>
    <string>ai.granola.allow-granola-accessibility</string>
    <key>PayloadOrganization</key>
    <string>Granola</string>
    <key>PayloadScope</key>
    <string>System</string>
    <key>PayloadType</key>
    <string>Configuration</string>
    <key>PayloadUUID</key>
    <string>914FAE30-385F-4E71-873D-D256A78F333F</string>
    <key>PayloadVersion</key>
    <integer>1</integer>
</dict>
</plist>

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.

On macOS 27+ you must create an app privacy permission defaults declaration. The first time a user opens Granola, macOS will show your organization’s justification and ask them to grant permission.Deploy the declaration below as a custom declaration (Declarative Device Management). In your MDM tool it must be user scoped, and the key must include Granola’s code-signing requirement exactly as shown, or macOS ignores it. Scope it to Macs on macOS 27 or later.

granola-accessibility-permission-defaults.json

{
  "Type": "com.apple.configuration.app.settings",
  "Identifier": "ai.granola.app-settings.privacy",
  "ServerToken": "version-1",
  "Payload": {
    "Privacy": {
      "PermissionDefaults": {
        "com.granola.app {identifier \"com.granola.app\" and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = QZ7DHHLN25}": {
          "OrganizationJustification": "Granola uses Accessibility to identify speakers in your meetings and to enable transparency features.",
          "Accessibility": "Allow"
        }
      }
    }
  }
}

On Jamf, you can build the same declaration in Blueprints > App Settings > App privacy permission defaults with bundle ID com.granola.app. See Jamf’s guide: Deploying App Privacy Permission Defaults in macOS 27.

Windows

Google Meet in Chrome, Zoom, and Teams use Windows accessibility support without a separate permission prompt. No macOS PPPC profile or browser extension is needed for this setup.

Google Meet Chrome extension

The Granola Chrome extension supports Google Meet speaker tags on macOS and Windows. Install it in the browser profile employees use for calls. It supports Chrome and supported Chromium-based browsers such as Edge, Arc, and Brave. To force-install it through Google Admin, follow the extension deployment and scoping instructions. Those installation steps also apply to speaker tags; enabling the automated chat message is a separate choice. Google Admin deployment applies to Chrome. Employees using other supported browsers may need to install the extension manually.

After deployment

Ask employees to update and open the Granola desktop app.
Click your workspace name in the bottom-left corner, then select Settings. Open Settings > Preferences, select Speaker tags, and confirm the row for their meeting app shows Enabled.
Start a call and transcription, then open the transcript panel to check for speaker names.

For setup and troubleshooting, see the Google Meet, Zoom, and Microsoft Teams guides. Speaker tags do not notify meeting participants that Granola is in use. If your team also uses transparency features, the same macOS permission and Chrome extension can satisfy those prerequisites, but transparency features have their own settings and setup steps.

Getting started

Taking notes

Organising and sharing

Granola Chat

Customizing Granola

Managing your account

Subscriptions

Security, Privacy & Transparency

Troubleshooting

Voice typing

Set up speaker tags for your team (Admin Guide)

macOS Accessibility

Pre-grant via MDM

Windows

Google Meet Chrome extension

After deployment

​macOS Accessibility

​Pre-grant via MDM

​Windows

​Google Meet Chrome extension

​After deployment

macOS Accessibility

Pre-grant via MDM

Windows

Google Meet Chrome extension

After deployment