Google Meet Configuration

1. Run the MuteMe app

   Install the current MuteMe desktop app, connect your device, and leave the app running. The original extension integration required 0.15.2 or later; use a current release rather than treating that old minimum as a recommendation.

2. Install the Chrome extension

   Install the MuteMe Chrome extension in the profile you use for meetings. Open its popup to check its connection to the MuteMe app. If your organization manages extensions, ask your administrator to approve it.

3. Enable Google Meet

   In MuteMe, open App Sync Settings. Choose Modify if needed and enable Google Meet under web integrations. Return, expand Google Meet, and select Level 3.

4. Choose and allow your microphone

   Open Meet in that Chrome profile. In Meet’s Settings → Audio, select the same microphone or headset controlled by MuteMe. Allow microphone access for Meet in Chrome; on Mac, allow Chrome microphone access if macOS requests it. MuteMe is a controller, not an audio input to select.

The existing integration is intended for one active Chrome profile. If connection or sync fails with several profiles open, test a single profile and meeting tab first. Chrome-based browsers other than Google Chrome have not been verified by these instructions.

1. Start a private test meeting

   After installing the extension, reload an already-open Meet tab and join a test meeting. Confirm the extension can connect to the running MuteMe app.

2. Try each mute control

   Toggle your MuteMe device and check Meet’s microphone button. Then click Meet’s microphone button and check MuteMe. Both directions should follow when the extension is connected and Level 3 is selected.

3. If the button and light disagree

   Check the Chrome profile, extension connection, Level 3 setting, and selected microphone. Close extra Meet tabs while diagnosing the problem. If a host has restricted microphone use, MuteMe cannot bypass that restriction.

You can use MuteMe to mute a selected system microphone without the Chrome extension. Make sure MuteMe controls the same microphone Meet uses. This is not equivalent to the extension’s two-way app integration: Meet’s button may not change, and clicking it may not update MuteMe.

Older Meet versions sometimes displayed a warning that another source had muted the microphone. Do not rely on a particular warning icon or assume other participants see a specific mute indicator; confirm the actual audio behavior in a private test call.

• Meet cannot hear you: check Chrome’s permission for meet.google.com, the selected microphone in Meet, operating-system microphone access for Chrome, and any headset mute switch.
• Echo or distortion: start with the correct microphone and headphones. If needed, compare Meet’s Settings → Audio → Noise cancellation with the option on and off, when available. Availability depends on the account and device; disabling it is not a required MuteMe setup step.
• macOS Accessibility: the web extension integration does not itself require MuteMe Accessibility or Automation permissions. Other MuteMe features you enable may ask for their own permissions.
• Managed computer: have your administrator review extension or browser restrictions instead of disabling security software.