Review browser camera and microphone access at both permission layers
Check the site’s grant and the operating system’s browser access, then test the intended device without opening permissions everywhere.
In brief
A video call can need permission from both the operating system and the browser site setting. A failure at one layer is not fixed by granting every website access at the other.
Reviewing the selected device and origin keeps troubleshooting limited to the service you intend to use.
Check the site you intended
Read the origin and grant permission only to the trusted call service. Use Chrome Settings → Privacy and security → Site settings → Camera or Microphone to review grants. Remove forgotten origins while keeping the service you actively need.
Check the OS and hardware
If the browser is blocked by Windows privacy settings, adjust its appropriate access rather than broad site grants. Inspect hardware mute switches and selected input. If another application records successfully, that is a useful comparison but does not prove this browser’s permission is correct.
Finish with a private test
Reload the page after a permission change and use its test or preview before joining. Review unexpected use indicators through the OS controls. Keep a microphone denied to a site that only needs reading; do not grant camera access to satisfy a fake security or CAPTCHA prompt.
Before you act
Work administrators can control these settings. Removing browser access does not delete recordings a site already made or change another app’s OS permission.
What to do next
- Check the call’s chosen camera/microphone and close an app using the device if relevant.
- Inspect the specific site’s permission in Chrome’s site controls or Site settings.
- Inspect OS privacy access for the browser, then reload the trusted site and test.
