Skip to main content

Browser Media Device Permissions (Microphone & Camera) – Group Policy Configuration

IT Administrator guide for configuring centralized browser policies to automatically grant microphone and camera permissions for Ambient Scribe, eliminating user-facing prompts in enterprise environments.

Written by Wesley Combs
Updated over 2 weeks ago

Article Type: IT Administrator Guide
​Target Audience: IT Administrators, Network Engineers
​Last Updated: February 2026

Overview

Ambient Scribe by Phiniti AI uses the enterprise-grade WebRTC infrastructure from Daily.co to deliver real-time audio and video capabilities directly in the browser. This includes microphone access for ambient clinical listening and documentation, as well as optional camera features during virtual encounters.

Because media device access occurs within secure iframes served from Daily.co domains (in addition to Phiniti application domains), centralized browser policies are required to automatically grant these permissions and eliminate user-facing prompts across your organization.

Related: For network firewall, port, and domain allowlisting requirements, see Network Configuration Requirements for Ambient Scribe.

Recommended Group Policy Settings (Chrome & Microsoft Edge)

Configure the following two browser policies via Group Policy:

  • AudioCaptureAllowedUrls — Automatically allows microphone access for specified domains

  • VideoCaptureAllowedUrls — Automatically allows camera access for specified domains

URL Patterns to Add

Add each URL pattern on its own line in both policies:

https://[*.]daily.co/
https://[*.]daily.co/*
https://[*.]ambient-scribe.com/
https://[*.]ambient-scribe.com/*
https://[*.]phiniti.ai/
https://[*.]phiniti.ai/*

Deployment Steps

  1. Ensure the latest Chrome or Edge ADMX templates are imported into your Group Policy Central Store.

  2. Open the Group Policy Management Editor.

  3. Navigate to: Computer Configuration → Administrative Templates → Google Chrome (or Microsoft Edge) → Content Settings.

  4. Locate AudioCaptureAllowedUrls and set it to Enabled.

  5. Click Show and enter the URL patterns listed above.

  6. Repeat for VideoCaptureAllowedUrls.

  7. Link the GPO to the appropriate Organizational Unit (OU) containing clinician workstations or users.

  8. On target machines, run gpupdate /force and restart Chrome or Edge.

Registry Equivalent (for Testing or Scripted Rollout)

For environments where GPO is not available, or for scripted deployments, apply the following registry keys:

Google Chrome

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\AudioCaptureAllowedUrls]
"1"="https://[*.]daily.co/"
"2"="https://[*.]daily.co/*"
"3"="https://[*.]ambient-scribe.com/"
"4"="https://[*.]ambient-scribe.com/*"
"5"="https://[*.]phiniti.ai/"
"6"="https://[*.]phiniti.ai/*"[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\VideoCaptureAllowedUrls]
"1"="https://[*.]daily.co/"
"2"="https://[*.]daily.co/*"
"3"="https://[*.]ambient-scribe.com/"
"4"="https://[*.]ambient-scribe.com/*"
"5"="https://[*.]phiniti.ai/"
"6"="https://[*.]phiniti.ai/*"

Microsoft Edge

Replace Google\Chrome with Microsoft\Edge in the registry paths above.

Additional Recommended Settings (Optional)

Setting

Purpose

Notes

ScreenCaptureAllowedUrls

Screen sharing permissions

Use same URL patterns if screen sharing is part of your workflow

AudioCaptureAllowed / VideoCaptureAllowed

Global device access safety net

Set to Enabled as a fallback

Windows App Privacy: Microphone

OS-level microphone access

Computer Config → Admin Templates → Windows Components → App Privacy → Force Allow

Windows App Privacy: Camera

OS-level camera access

Same path as above → Force Allow

Important Notes

  • All sessions must use HTTPS — WebRTC media access is blocked on HTTP (except localhost).

  • Ambient Scribe automatically includes the required allow="camera; microphone;" attributes on Daily.co iframes.

  • Deploy to a small pilot group first and verify in Chrome/Edge → Settings → Privacy and security → Site Settings that the listed domains show as "Allowed" with no permission prompts.

Verification Checklist

  1. After applying GPO, run gpupdate /force on a test workstation.

  2. Open Chrome or Edge and navigate to chrome://policy (or edge://policy).

  3. Confirm AudioCaptureAllowedUrls and VideoCaptureAllowedUrls appear with the correct URL patterns.

  4. Navigate to Ambient Scribe and start an encounter — microphone should activate without a permission prompt.

  5. If using telehealth, verify camera also activates without a prompt.

Support

For assistance with custom domains, pilot testing, or your specific EHR-integrated deployment, contact Phiniti AI Support at [email protected] or visit the full network requirements article: Network Configuration Requirements for Ambient Scribe.

Did this answer your question?