Configure Browser for Local Network Access
Enable local streaming in Chrome and Edge for Verkada Command
By default, modern browsers restrict websites from accessing devices on your local network for security reasons. To enable local streaming from Verkada cameras when you use Command through your organization's URL (for example, org-name.command.verkada.com), configure your browser to allow local network access for that site.
Local network access enables faster, lower-latency streaming by connecting directly to cameras on your local network rather than routing through the cloud.
This configuration is required for each browser profile and must be set on every device you plan to use for local streaming.
Before you begin
Chrome version 90 or later, or Microsoft Edge version 90 or later
Administrative access to your computer to modify browser settings
Your organization's Command URL (for example,
org-name.command.verkada.com)
Enterprise deployment (IT admins)
IT administrators can pre-grant local network access across all managed browsers using a Chrome or Edge enterprise policy. This removes the local network access prompt in Verkada Command and allows local streaming to work immediately without requiring any user action. Verkada recommends this approach for deployments with multiple devices.
Admins can add Command URLs to the LocalNetworkAccessAllowedForUrls policy. URLs that match this policy bypass Chrome's Local Network Access checks, allowing Command to connect directly to cameras on the local network without prompting users.
Use one of the following values:
Allow all Command subdomains:
[*.]command.verkada.com
Restrict access to a specific organization:
[*.]org-name.command.verkada.com
Configuration
Google Admin Console
Navigate to Devices > Chrome > Settings > Users & browsers.
Locate Local network access allowed for URLs.
Add the appropriate URL pattern.
Windows Group Policy
Navigate to Computer Configuration or User Configuration > Administrative Templates > Google > Google Chrome.
Open Allow local network access on these sites.
Add the appropriate URL pattern.
Requires the Chrome ADMX templates.
macOS MDM
Add the
LocalNetworkAccessAllowedForUrlskey to thecom.google.Chromeconfiguration profile.Deploy the profile through your MDM solution, such as Jamf or Intune.
Linux
Add LocalNetworkAccessAllowedForUrls to the managed JSON policy file located in /etc/opt/chrome/policies/managed/.
To verify that the policy has been applied, open chrome://policy on a managed device and confirm that LocalNetworkAccessAllowedForUrls includes your Command URL. If LocalNetworkAccessBlockedForUrls is also configured, ensure that it does not contain a matching rule, as block rules take precedence over allow rules. For URL pattern requirements, refer to Chrome's URL pattern documentation.
Microsoft Edge is Chromium-based and supports the same LocalNetworkAccessAllowedForUrls policy. Configure the policy using one of the following methods:
Microsoft Intune
Windows Group Policy (Administrative Templates > Microsoft Edge)
In both cases, add the same URL pattern used for Chrome to allow local network access for Verkada Command.
Configure Google Chrome
Open Chrome and go to your Command URL.
Example: https://org-name.command.verkada.com
In the address bar, click the lock icon or connection status indicator.
In the dropdown, click Site settings.
Scroll to Permissions and find "Access to devices on your local network."
Click the dropdown next to that permission and select Allow.
Refresh the Command page (F5 or the refresh button).
Open Chrome and go to Settings.
Click the three-dot menu (top right) and select Settings, or go to chrome://settings in the address bar.
In the left sidebar, click Privacy and security, then Site Settings.
Under Additional permissions, click Access to devices on your local network.
Under "Allowed to ask for access," click Add and enter your Command URL.
Use your org URL (for example,
[*.]org-name.command.verkada.com).Use
[*.]*.command.verkada.comto allow all Command subdomains.
(Optional) To allow access without prompting:
a. Click Add next to "Allowed to access devices on your local network." b. Enter your Command URL using the same pattern. c. Click Add.
Configure Microsoft Edge
Open Edge and go to your Command URL.
Example: https://your-org.command.verkada.com
In the address bar, click the lock icon or connection status indicator.
In the dropdown, click Permissions for this site.
Scroll to Site permissions and find "Local network access."
Click the dropdown next to that permission and select Allow.
Refresh the Command page (F5 or the refresh button).
Open Edge and go to Settings.
Click the three-dot menu (top right) and select Settings, or go to edge://settings in the address bar.
In the left sidebar, click Cookies and site permissions.
Under All permissions, click Local network access.
Under "Allow," click Add and enter your Command URL.
Use your org URL (for example,
[*.]org-name.command.verkada.com).Use
[*.]*.command.verkada.comto allow all Command subdomains.
Verify local network access is enabled
Go to your Command organization URL.
Open a camera feed.
a. In Verkada Command, go to All Products > Cameras. b. Select any camera to view its live feed.
Check the connection.
If local streaming is working, you see LOCAL on the bottom left of the live stream. The system then pulls the feed directly from the camera on your local network when available.
If you continue to experience connectivity issues, verify that:
Your device is connected to the same network as the cameras
Your network firewall allows direct camera connections
The cameras are online and accessible
See the troubleshooting section in Local streaming on Verkada cameras for more information.
Troubleshooting
If you don't see "Access to devices on your local network":
Verify Chrome is running version 90 or later
Update Chrome to the latest version
Quit and restart Chrome
If you don't see "Local network access":
Verify Microsoft Edge is running version 90 or later
Update Edge to the latest version
Quit and restart Edge
Last updated
Was this helpful?