Skip to main content
in-meeting-copy-consent-message.png

​
Overview

In-meeting notice helps you let people know that Granola is being used by automatically posting a notice message in meeting chat when transcription starts. This provides real-time notice to all participants. Automatic in-meeting notice works in most situations but isn’t 100% reliable due to varying browser settings, focus states, and platform configurations. Here are some scenarios where automatic in-meeting notice may fail:
  • Meeting chat is not enabled by your organization.
  • You are not using Google Meet or Zoom (Google Meet requires Chrome, Safari, or Arc browser).
  • Other applications, such as Loom, are interrupting Granola. (see “Troubleshooting” below)
  • You have not enabled macOS accessibility permissions. (see “Enabling In-Meeting Notice” below)
  • You are on Windows.

​
How it works

When automatic in-meeting notice is enabled:
  1. You join a meeting on Google Meet or Zoom.
  2. Granola attempts to auto-post your notice message into the meeting chat.
  3. If auto-post succeeds, all participants see the message immediately.

​
Enabling in-meeting notice

To enable in-meeting notice either as an individual user or on behalf of all users in your enterprise workspace, you need to switch on the setting and enable accessibility permissions.

​
As an individual user

Individual users on any plan can enable automatic in-meeting notice. To do so, go to Settings > Labs > Let others know you’re using Granola. For automatic in-meeting notice to work, you will also need to enable accessibility permissions (see below). Screenshot 2025-12-22 at 11.28.22.png

​
For all users in a workspace

This feature is only available to Enterprise plans. Workspace admins can enable automatic in-meeting notice for all users in the workspace. Once enabled by an admin, individual users cannot turn this feature off. To do so, go to Settings > Workspace > General > Notify participants via meeting chat and turn on Notify in Google Meet and/or Notify in Zoom Chat. Admins can also customize the notice message text to match your organization’s requirements (see “Customizing your message” below). For automatic in-meeting notice to work, workspace members will also need to enable accessibility permissions (see below).

​
Enabling accessibility permissions

Automatic in-meeting notice requires macOS accessibility permissions, hence does not work on Windows. Auto-paste requires accessibility permissions to interact with your meeting chat window.
  1. When you (or your admin) enables this feature, you will see a persistent notification to complete setup of automatic in-meeting notice. Screenshot 2025-12-22 at 11.31.34.png
  2. Click “Complete setup” to open the MacOS System Settings > Privacy & Security > Accessibility panel.
  3. Enable permissions for Granola.
Screenshot 2025-12-22 at 11.23.56.png Once enabled, the persistent notification will disappear.

​
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. 
<?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 post automatic consent messages in meeting chats 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 post automatic consent messages in meeting chats without prompting the user.</string>
    <key>PayloadDisplayName</key>
    <string>Allow Granola Accessibility (Automatic Consent Messaging)</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.

​
Customizing your message

For workspace admins:
  1. Go to Settings > Workspace > General > Notify participants via meeting chat
  2. Edit your notice message text in the provided field. Changes save automatically.
Your customized message will be posted in meeting chat at the start of your calls.

​
Troubleshooting

​
I see confetti when entering meetings

If you have Loom running when you’re on Granola, you need to disable the keyboard shortcut for confetti. To do so, open up the Loom widget and click on the three dots to open the settings. In preferences, disable the keyboard shortcut for confetti.

​
Message isn’t sending right at the start of a meeting

Automatic in-meeting notice is sent when:
  • Transcription has already started and recorded some transcription (i.e. another person is definitely present in the meeting).
  • The video call window is ‘in focus’ (i.e. you’ve clicked on it).
Therefore, the message may appear slightly later into the call, if not much is said at the start or if you’re focussed on another window.

​
Need help?

If you have questions about automatic in-chat entrance messaging or accessibility permissions, reach out to our support team at support@granola.so.