# Table of Contents - [Home Page | Verkada Help](#home-page-verkada-help) - [Government Solutions | Verkada Help](#government-solutions-verkada-help) - [Air Quality Sensors | Air Quality | Verkada Help](#air-quality-sensors-air-quality-verkada-help) - [Security Trailer | Verkada Help](#security-trailer-verkada-help) - [Connectivity | Verkada Help](#connectivity-verkada-help) - [Classic Alarms | Verkada Help](#classic-alarms-verkada-help) - [Viewing Station | Verkada Help](#viewing-station-verkada-help) - [Command Connector | Verkada Help](#command-connector-verkada-help) - [Mailroom | Verkada Help](#mailroom-verkada-help) - [Incident Response | Verkada Help](#incident-response-verkada-help) - [Access Control | Verkada Help](#access-control-verkada-help) - [Intercom | Verkada Help](#intercom-verkada-help) - [New Alarms | Verkada Help](#new-alarms-verkada-help) - [Guest | Verkada Help](#guest-verkada-help) - [Command | Verkada Help](#command-verkada-help) - [Video Security | Verkada Cameras | Verkada Help](#video-security-verkada-cameras-verkada-help) - [Contact Verkada Support - Government Solutions | Government Solutions | Verkada Help](#contact-verkada-support-government-solutions-government-solutions-verkada-help) - [Configuration and Setup | Government Solutions | Verkada Help](#configuration-and-setup-government-solutions-verkada-help) - [Get Started with Government Solutions | Government Solutions | Verkada Help](#get-started-with-government-solutions-government-solutions-verkada-help) - [Events and Alerts | Government Solutions | Verkada Help](#events-and-alerts-government-solutions-verkada-help) - [Compliance | Government Solutions | Verkada Help](#compliance-government-solutions-verkada-help) - [Required Network Settings | Government Solutions | Verkada Help](#required-network-settings-government-solutions-verkada-help) - [Single Sign-On (SSO) | Government Solutions | Verkada Help](#single-sign-on-sso-government-solutions-verkada-help) - [Why Government Solutions/FIPS Devices? | Government Solutions | Verkada Help](#why-government-solutions-fips-devices-government-solutions-verkada-help) - [End-of-Sale Product Updates | Air Quality | Verkada Help](#end-of-sale-product-updates-air-quality-verkada-help) - [Hardware Installation | Air Quality | Verkada Help](#hardware-installation-air-quality-verkada-help) - [Troubleshooting | Air Quality | Verkada Help](#troubleshooting-air-quality-verkada-help) - [Air Quality Sensor Network Settings | Air Quality | Verkada Help](#air-quality-sensor-network-settings-air-quality-verkada-help) - [Events and Alerts | Air Quality | Verkada Help](#events-and-alerts-air-quality-verkada-help) - [Get Started with Verkada Air Quality Sensors | Air Quality | Verkada Help](#get-started-with-verkada-air-quality-sensors-air-quality-verkada-help) - [Sensor Data | Air Quality | Verkada Help](#sensor-data-air-quality-verkada-help) - [Quick Reference Guide for Verkada Air Quality Sensors | Air Quality | Verkada Help](#quick-reference-guide-for-verkada-air-quality-sensors-air-quality-verkada-help) - [MT81 Cloud-Managed Security Trailer FAQ | Security Trailer | Verkada Help](#mt81-cloud-managed-security-trailer-faq-security-trailer-verkada-help) - [Configuration and Setup | Air Quality | Verkada Help](#configuration-and-setup-air-quality-verkada-help) - [Roles and Permissions for Gateway | Connectivity | Verkada Help](#roles-and-permissions-for-gateway-connectivity-verkada-help) - [Classic Alarms Network Settings | Classic Alarms | Verkada Help](#classic-alarms-network-settings-classic-alarms-verkada-help) - [Get Started with the Cellular Gateway | Connectivity | Verkada Help](#get-started-with-the-cellular-gateway-connectivity-verkada-help) - [Roles and Permissions for Classic Alarms | Classic Alarms | Verkada Help](#roles-and-permissions-for-classic-alarms-classic-alarms-verkada-help) - [Quick Reference Guide for Verkada Alarms | Classic Alarms | Verkada Help](#quick-reference-guide-for-verkada-alarms-classic-alarms-verkada-help) - [Gateways Network Settings | Connectivity | Verkada Help](#gateways-network-settings-connectivity-verkada-help) - [Required Camera Network Settings - Government Solutions | Government Solutions | Verkada Help](#required-camera-network-settings-government-solutions-government-solutions-verkada-help) - [Hardware Installation | Command Connector | Verkada Help](#hardware-installation-command-connector-verkada-help) - [Cellular Data Options | Connectivity | Verkada Help](#cellular-data-options-connectivity-verkada-help) - [Troubleshooting | Classic Alarms | Verkada Help](#troubleshooting-classic-alarms-verkada-help) - [Mailroom Network Settings | Mailroom | Verkada Help](#mailroom-network-settings-mailroom-verkada-help) - [Smart Tiles | Viewing Station | Verkada Help](#smart-tiles-viewing-station-verkada-help) - [Create Guardian Forms for Reunification | Incident Response | Verkada Help](#create-guardian-forms-for-reunification-incident-response-verkada-help) - [Compliance, Licensing, Trials | Classic Alarms | Verkada Help](#compliance-licensing-trials-classic-alarms-verkada-help) - [Viewing Station Network Settings | Viewing Station | Verkada Help](#viewing-station-network-settings-viewing-station-verkada-help) - [Incident Response Portal | Incident Response | Verkada Help](#incident-response-portal-incident-response-verkada-help) - [Events and Alerts | Connectivity | Verkada Help](#events-and-alerts-connectivity-verkada-help) - [Events and Alerts | Mailroom | Verkada Help](#events-and-alerts-mailroom-verkada-help) - [Get started with Command Connector | Command Connector | Verkada Help](#get-started-with-command-connector-command-connector-verkada-help) - [Create Response Templates | Incident Response | Verkada Help](#create-response-templates-incident-response-verkada-help) - [Networking and Reports | Classic Alarms | Verkada Help](#networking-and-reports-classic-alarms-verkada-help) - [Troubleshooting | Command Connector | Verkada Help](#troubleshooting-command-connector-verkada-help) - [Events and Alerts | Classic Alarms | Verkada Help](#events-and-alerts-classic-alarms-verkada-help) - [Prepare for a Command Connector Deployment | Command Connector | Verkada Help](#prepare-for-a-command-connector-deployment-command-connector-verkada-help) - [Configuration and Setup | Mailroom | Verkada Help](#configuration-and-setup-mailroom-verkada-help) - [Get Started with Verkada Mailroom | Mailroom | Verkada Help](#get-started-with-verkada-mailroom-mailroom-verkada-help) - [Roles and Permissions for Mailroom | Mailroom | Verkada Help](#roles-and-permissions-for-mailroom-mailroom-verkada-help) - [Set Up Your Viewing Station | Viewing Station | Verkada Help](#set-up-your-viewing-station-viewing-station-verkada-help) - [Review Responses from Command | Incident Response | Verkada Help](#review-responses-from-command-incident-response-verkada-help) - [Roles and Permissions for Air Quality Sensors | Air Quality | Verkada Help](#roles-and-permissions-for-air-quality-sensors-air-quality-verkada-help) - [Customize Your Mailroom Dashboard | Mailroom | Verkada Help](#customize-your-mailroom-dashboard-mailroom-verkada-help) - [Command Connector Network Settings | Command Connector | Verkada Help](#command-connector-network-settings-command-connector-verkada-help) - [Get Started with Incident Response | Incident Response | Verkada Help](#get-started-with-incident-response-incident-response-verkada-help) - [Hardware Installation | Classic Alarms | Verkada Help](#hardware-installation-classic-alarms-verkada-help) - [Get Started with Verkada Classic Alarms | Classic Alarms | Verkada Help](#get-started-with-verkada-classic-alarms-classic-alarms-verkada-help) - [Configuration and Setup | Command Connector | Verkada Help](#configuration-and-setup-command-connector-verkada-help) - [Troubleshooting | Intercom | Verkada Help](#troubleshooting-intercom-verkada-help) - [Alerts and Events | Access Control | Verkada Help](#alerts-and-events-access-control-verkada-help) - [Configuration and Setup | Classic Alarms | Verkada Help](#configuration-and-setup-classic-alarms-verkada-help) - [Hardware and Installation | Intercom | Verkada Help](#hardware-and-installation-intercom-verkada-help) - [Roles and Permissions for Intercom | Intercom | Verkada Help](#roles-and-permissions-for-intercom-intercom-verkada-help) - [Getting Started with Verkada Alarms | New Alarms | Verkada Help](#getting-started-with-verkada-alarms-new-alarms-verkada-help) - [Notifications | Guest | Verkada Help](#notifications-guest-verkada-help) - [Access Control Network Settings | Access Control | Verkada Help](#access-control-network-settings-access-control-verkada-help) - [Events and Alerts | New Alarms | Verkada Help](#events-and-alerts-new-alarms-verkada-help) - [Troubleshooting | New Alarms | Verkada Help](#troubleshooting-new-alarms-verkada-help) - [Get Started with Verkada Intercom | Intercom | Verkada Help](#get-started-with-verkada-intercom-intercom-verkada-help) - [Troubleshooting | Access Control | Verkada Help](#troubleshooting-access-control-verkada-help) - [Get Started with Verkada Guest | Guest | Verkada Help](#get-started-with-verkada-guest-guest-verkada-help) - [Healthcare | Guest | Verkada Help](#healthcare-guest-verkada-help) - [Roles and Permissions for New Alarms | New Alarms | Verkada Help](#roles-and-permissions-for-new-alarms-new-alarms-verkada-help) - [Create a Command Organization | Command | Verkada Help](#create-a-command-organization-command-verkada-help) - [Verkada Command System Requirements | Command | Verkada Help](#verkada-command-system-requirements-command-verkada-help) - [Quick Reference Guide for Verkada Intercom | Intercom | Verkada Help](#quick-reference-guide-for-verkada-intercom-intercom-verkada-help) - [Configuration and Setup | Connectivity | Verkada Help](#configuration-and-setup-connectivity-verkada-help) - [Alarms Specifications | New Alarms | Verkada Help](#alarms-specifications-new-alarms-verkada-help) - [Hardware Installation | New Alarms | Verkada Help](#hardware-installation-new-alarms-verkada-help) - [Get Started with Verkada Access Control | Access Control | Verkada Help](#get-started-with-verkada-access-control-access-control-verkada-help) - [Get Started with Verkada Command | Command | Verkada Help](#get-started-with-verkada-command-command-verkada-help) - [Third-Party User Provisioning | Command | Verkada Help](#third-party-user-provisioning-command-verkada-help) - [Organization-Wide Settings | Command | Verkada Help](#organization-wide-settings-command-verkada-help) - [Roles and Permissions for Guest | Guest | Verkada Help](#roles-and-permissions-for-guest-guest-verkada-help) - [Quick Reference Guide for Verkada Access Control | Access Control | Verkada Help](#quick-reference-guide-for-verkada-access-control-access-control-verkada-help) - [Sharing Video | Verkada Cameras | Verkada Help](#sharing-video-verkada-cameras-verkada-help) - [Data Protection and Security | Command | Verkada Help](#data-protection-and-security-command-verkada-help) - [Guest Network Settings | Guest | Verkada Help](#guest-network-settings-guest-verkada-help) - [Hardware Installation | Verkada Cameras | Verkada Help](#hardware-installation-verkada-cameras-verkada-help) - [Historical Playback | Verkada Cameras | Verkada Help](#historical-playback-verkada-cameras-verkada-help) - [Licensing and Warranty | Command | Verkada Help](#licensing-and-warranty-command-verkada-help) - [Intercom Network Settings | Intercom | Verkada Help](#intercom-network-settings-intercom-verkada-help) - [Camera Specifications | Verkada Cameras | Verkada Help](#camera-specifications-verkada-cameras-verkada-help) - [Live Streaming | Verkada Cameras | Verkada Help](#live-streaming-verkada-cameras-verkada-help) - [Required Network Settings | Command | Verkada Help](#required-network-settings-command-verkada-help) - [Integrations | Command | Verkada Help](#integrations-command-verkada-help) - [Need Help? | Command | Verkada Help](#need-help-command-verkada-help) - [Maintenance for Your Camera | Verkada Cameras | Verkada Help](#maintenance-for-your-camera-verkada-cameras-verkada-help) - [Configuration and Setup | Intercom | Verkada Help](#configuration-and-setup-intercom-verkada-help) - [Users and Permissions | Command | Verkada Help](#users-and-permissions-command-verkada-help) - [Get Started with Verkada Security Cameras | Verkada Cameras | Verkada Help](#get-started-with-verkada-security-cameras-verkada-cameras-verkada-help) - [Analytics and Detection | Verkada Cameras | Verkada Help](#analytics-and-detection-verkada-cameras-verkada-help) - [Quick Reference Guide for Verkada Command | Command | Verkada Help](#quick-reference-guide-for-verkada-command-command-verkada-help) - [Hardware Installation | Access Control | Verkada Help](#hardware-installation-access-control-verkada-help) - [Configuration and Setup | New Alarms | Verkada Help](#configuration-and-setup-new-alarms-verkada-help) - [Events and Alerts | Verkada Cameras | Verkada Help](#events-and-alerts-verkada-cameras-verkada-help) - [Troubleshooting | Verkada Cameras | Verkada Help](#troubleshooting-verkada-cameras-verkada-help) - [Single Sign-On (SSO) | Command | Verkada Help](#single-sign-on-sso-command-verkada-help) - [Roles and Permissions for Access Control | Access Control | Verkada Help](#roles-and-permissions-for-access-control-access-control-verkada-help) - [Alarms Network Settings | New Alarms | Verkada Help](#alarms-network-settings-new-alarms-verkada-help) - [New Alarms vs. Classic Alarms | New Alarms | Verkada Help](#new-alarms-vs-classic-alarms-new-alarms-verkada-help) - [Quick Reference Guide for Verkada Cameras | Verkada Cameras | Verkada Help](#quick-reference-guide-for-verkada-cameras-verkada-cameras-verkada-help) - [Site Planner & Partner Tools | Command | Verkada Help](#site-planner-partner-tools-command-verkada-help) - [Configuration and Setup | Guest | Verkada Help](#configuration-and-setup-guest-verkada-help) - [Camera Network Settings | Verkada Cameras | Verkada Help](#camera-network-settings-verkada-cameras-verkada-help) - [Configuration and Setup | Verkada Cameras | Verkada Help](#configuration-and-setup-verkada-cameras-verkada-help) - [End-of-Sale Product Updates | Command | Verkada Help](#end-of-sale-product-updates-command-verkada-help) - [Configuration and Setup | Access Control | Verkada Help](#configuration-and-setup-access-control-verkada-help) - [Contact Verkada Support | Command | Verkada Help](#contact-verkada-support-command-verkada-help) - [Enable Support Access | Command | Verkada Help](#enable-support-access-command-verkada-help) - [Add Cellular Gateway to Command - Government Solutions | Government Solutions | Verkada Help](#add-cellular-gateway-to-command-government-solutions-government-solutions-verkada-help) - [CJIS Support Status | Government Solutions | Verkada Help](#cjis-support-status-government-solutions-verkada-help) - [Enable NCIC Alerts | Government Solutions | Verkada Help](#enable-ncic-alerts-government-solutions-verkada-help) - [Required Access Control Network Settings - Government Solutions | Government Solutions | Verkada Help](#required-access-control-network-settings-government-solutions-government-solutions-verkada-help) - [Government Solutions Licensing | Government Solutions | Verkada Help](#government-solutions-licensing-government-solutions-verkada-help) - [Required Air Quality Sensor Network Settings - Government Solutions | Government Solutions | Verkada Help](#required-air-quality-sensor-network-settings-government-solutions-government-solutions-verkada-help) - [Required Command Connector Network Settings - Government Solutions | Government Solutions | Verkada Help](#required-command-connector-network-settings-government-solutions-government-solutions-verkada-help) - [Required Cellular Gateway Network Settings - Government Solutions | Government Solutions | Verkada Help](#required-cellular-gateway-network-settings-government-solutions-government-solutions-verkada-help) - [Email Protection | Cloudflare](#email-protection-cloudflare) - [Air Quality Sensor Status LED | Air Quality | Verkada Help](#air-quality-sensor-status-led-air-quality-verkada-help) - [Installation Guidelines for Sensors | Air Quality | Verkada Help](#installation-guidelines-for-sensors-air-quality-verkada-help) - [Security Screening Settings | Guest | Verkada Help](#security-screening-settings-guest-verkada-help) - [Microsoft Entra ID SAML Integration - Government Solutions | Government Solutions | Verkada Help](#microsoft-entra-id-saml-integration-government-solutions-government-solutions-verkada-help) - [Okta SAML Integration - Government Solutions | Government Solutions | Verkada Help](#okta-saml-integration-government-solutions-government-solutions-verkada-help) - [Loss of Network Connection for Air Quality Sensors | Air Quality | Verkada Help](#loss-of-network-connection-for-air-quality-sensors-air-quality-verkada-help) - [Bulk Edit Air Quality Sensor Settings | Air Quality | Verkada Help](#bulk-edit-air-quality-sensor-settings-air-quality-verkada-help) - [Create a Person of Interest for Air Quality sensors | Air Quality | Verkada Help](#create-a-person-of-interest-for-air-quality-sensors-air-quality-verkada-help) - [Air Quality Sensor Calibration | Air Quality | Verkada Help](#air-quality-sensor-calibration-air-quality-verkada-help) - [Integrate Verkada Cameras with Air Quality Sensors | Air Quality | Verkada Help](#integrate-verkada-cameras-with-air-quality-sensors-air-quality-verkada-help) - [Air Quality Event Analytics | Air Quality | Verkada Help](#air-quality-event-analytics-air-quality-verkada-help) - [Audio Recording with the SV25 | Air Quality | Verkada Help](#audio-recording-with-the-sv25-air-quality-verkada-help) - [Air Quality Alerts Migration | Air Quality | Verkada Help](#air-quality-alerts-migration-air-quality-verkada-help) - [Roles and Permissions for Command | Command | Verkada Help](#roles-and-permissions-for-command-command-verkada-help) - [Third-Party VMS Integrations for Air Quality Sensor Events | Air Quality | Verkada Help](#third-party-vms-integrations-for-air-quality-sensor-events-air-quality-verkada-help) - [Air Quality Sensor Zones | Air Quality | Verkada Help](#air-quality-sensor-zones-air-quality-verkada-help) - [Detect and Understand Carbon Monoxide | Air Quality | Verkada Help](#detect-and-understand-carbon-monoxide-air-quality-verkada-help) - [Air Quality Sensor Power Requirements | Air Quality | Verkada Help](#air-quality-sensor-power-requirements-air-quality-verkada-help) - [Configure Static IP Addresses for Air Quality Sensors (SV20 Series Only) | Air Quality | Verkada Help](#configure-static-ip-addresses-for-air-quality-sensors-sv20-series-only-air-quality-verkada-help) - [Configure Air Quality Event Alerts | Air Quality | Verkada Help](#configure-air-quality-event-alerts-air-quality-verkada-help) - [Add a Device to Your Command Organization | Verkada Cameras | Verkada Help](#add-a-device-to-your-command-organization-verkada-cameras-verkada-help) - [Manage Your Sensor Dashboard | Air Quality | Verkada Help](#manage-your-sensor-dashboard-air-quality-verkada-help) - [Best Practices for Vape Detection | Air Quality | Verkada Help](#best-practices-for-vape-detection-air-quality-verkada-help) - [Air Quality Sensor Readings | Air Quality | Verkada Help](#air-quality-sensor-readings-air-quality-verkada-help) - [Air Quality Sensor Settings | Air Quality | Verkada Help](#air-quality-sensor-settings-air-quality-verkada-help) - [Manage Your Licenses | Command | Verkada Help](#manage-your-licenses-command-verkada-help) - [Manage Sites and Subsites | Verkada Cameras | Verkada Help](#manage-sites-and-subsites-verkada-cameras-verkada-help) - [BACnet for Verkada Air Quality Sensors | Air Quality | Verkada Help](#bacnet-for-verkada-air-quality-sensors-air-quality-verkada-help) - [Classic Alarms Sites | Classic Alarms | Verkada Help](#classic-alarms-sites-classic-alarms-verkada-help) - [How to Arm/Disarm Your Alarm Site | Classic Alarms | Verkada Help](#how-to-arm-disarm-your-alarm-site-classic-alarms-verkada-help) - [Delete Air Quality Sensors from Command | Air Quality | Verkada Help](#delete-air-quality-sensors-from-command-air-quality-verkada-help) - [Manage Alerts Across Verkada Products | Verkada Cameras | Verkada Help](#manage-alerts-across-verkada-products-verkada-cameras-verkada-help) - [Alarm Setup and Install Best Practices | Classic Alarms | Verkada Help](#alarm-setup-and-install-best-practices-classic-alarms-verkada-help) - [Configure BACnet on Air Quality Sensors | Air Quality | Verkada Help](#configure-bacnet-on-air-quality-sensors-air-quality-verkada-help) - [View Air Quality Sensor Data | Air Quality | Verkada Help](#view-air-quality-sensor-data-air-quality-verkada-help) - [Set Up the BC82 Alarm Console | Classic Alarms | Verkada Help](#set-up-the-bc82-alarm-console-classic-alarms-verkada-help) - [Set Up and Install Wireless Sensors | Classic Alarms | Verkada Help](#set-up-and-install-wireless-sensors-classic-alarms-verkada-help) - [Configure Camera Alarm Trigger Events | Classic Alarms | Verkada Help](#configure-camera-alarm-trigger-events-classic-alarms-verkada-help) - [Configure Alarms Event Alerts | Classic Alarms | Verkada Help](#configure-alarms-event-alerts-classic-alarms-verkada-help) - [Troubleshoot Inrush Current Issues | Classic Alarms | Verkada Help](#troubleshoot-inrush-current-issues-classic-alarms-verkada-help) - [Configure Classic Alarms Site Settings | Classic Alarms | Verkada Help](#configure-classic-alarms-site-settings-classic-alarms-verkada-help) - [Cellular Gateway Status LEDs | Connectivity | Verkada Help](#cellular-gateway-status-leds-connectivity-verkada-help) - [Use Cellular Gateways for WAN Failover | Connectivity | Verkada Help](#use-cellular-gateways-for-wan-failover-connectivity-verkada-help) - [Set Up Your Wireless Alarm Devices | Classic Alarms | Verkada Help](#set-up-your-wireless-alarm-devices-classic-alarms-verkada-help) - [Set Up Universal Transmitter Mode on a BR31 with Classic Alarms | Classic Alarms | Verkada Help](#set-up-universal-transmitter-mode-on-a-br31-with-classic-alarms-classic-alarms-verkada-help) - [Smart Data Usage | Connectivity | Verkada Help](#smart-data-usage-connectivity-verkada-help) - [Determine Relevant Alarm Permits | Classic Alarms | Verkada Help](#determine-relevant-alarm-permits-classic-alarms-verkada-help) - [Set Up the BK11/BK21 Alarm Keypad | Classic Alarms | Verkada Help](#set-up-the-bk11-bk21-alarm-keypad-classic-alarms-verkada-help) - [Verkada Monitoring Phone Numbers for Classic Alarms | Classic Alarms | Verkada Help](#verkada-monitoring-phone-numbers-for-classic-alarms-classic-alarms-verkada-help) - [Configure Static IP Addresses for Cameras | Verkada Cameras | Verkada Help](#configure-static-ip-addresses-for-cameras-verkada-cameras-verkada-help) - [Bring Your Own Data Plan | Connectivity | Verkada Help](#bring-your-own-data-plan-connectivity-verkada-help) - [Gateway Monthly Data Usage Alerts | Connectivity | Verkada Help](#gateway-monthly-data-usage-alerts-connectivity-verkada-help) - [Enable Historical GPS Data on GC31-E Gateways | Connectivity | Verkada Help](#enable-historical-gps-data-on-gc31-e-gateways-connectivity-verkada-help) - [Configure a BX21 Wireless Relay | Classic Alarms | Verkada Help](#configure-a-bx21-wireless-relay-classic-alarms-verkada-help) - [Configure Static IP Addresses for Command Connector | Command Connector | Verkada Help](#configure-static-ip-addresses-for-command-connector-command-connector-verkada-help) - [Use a PoE Switch with Outdoor Gateways | Connectivity | Verkada Help](#use-a-poe-switch-with-outdoor-gateways-connectivity-verkada-help) - [Set Up the BZ11 Horn Speaker with Classic Alarms | Classic Alarms | Verkada Help](#set-up-the-bz11-horn-speaker-with-classic-alarms-classic-alarms-verkada-help) - [Verkada Alarms Monitoring Certificate | New Alarms | Verkada Help](#verkada-alarms-monitoring-certificate-new-alarms-verkada-help) - [Change a non-Verkada Channel Orientation | Command Connector | Verkada Help](#change-a-non-verkada-channel-orientation-command-connector-verkada-help) --- # Home Page | Verkada Help [](https://help.verkada.com/command/) ![Cover](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F246171046-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FzfrVPow912E2LqKLhtak%252Fuploads%252F0LNVXf4pwQApUO6k4NTV%252FCommand.png%3Falt%3Dmedia%26token%3Da481e900-a6c6-4432-8b72-bae95c7a140a&width=490&dpr=4&quality=100&sign=a4cc2c39&sv=2) **Command** Securely access and manage your Verkada devices through our web-based platform [](https://help.verkada.com/government-solutions/) ![Cover](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F246171046-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FzfrVPow912E2LqKLhtak%252Fuploads%252FfrlIfwBttzPUgx3uD7ih%252FGovernment%2520Solutions.png%3Falt%3Dmedia%26token%3D15711c22-d812-4516-8024-4ae78a13d6d9&width=490&dpr=4&quality=100&sign=7307a583&sv=2) **Government Solutions** Proactive, streamlined, and scalable approach to physical security, with key enhancements for high-security government use [](https://help.verkada.com/verkada-cameras/) ![Cover](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F246171046-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FzfrVPow912E2LqKLhtak%252Fuploads%252FOhjxxhn1OoY0aBrlX97P%252FVideo%2520Security.png%3Falt%3Dmedia%26token%3Dbe854420-fc57-4678-9faf-059e52fded3b&width=490&dpr=4&quality=100&sign=3ef88a63&sv=2) **Video Security** Manage your enterprise security with our infinitely scalable hybrid cloud video surveillance solution [](https://help.verkada.com/access-control/) ![Cover](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F246171046-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FzfrVPow912E2LqKLhtak%252Fuploads%252Fso8VbqfdMgiA10GZp6JI%252FAccess%2520Control.png%3Falt%3Dmedia%26token%3D3e9a4511-74cb-428d-9707-6c3ac82448c4&width=490&dpr=4&quality=100&sign=6f892ccc&sv=2) **Access Control** Manage building access with our plug-and-play hybrid cloud system [](https://help.verkada.com/intercom/) ![Cover](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F246171046-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FzfrVPow912E2LqKLhtak%252Fuploads%252FOmov9DpzweKghwNQhPF8%252FIntercom.png%3Falt%3Dmedia%26token%3D1331cbf6-bad1-4415-998b-407d4676ca89&width=490&dpr=4&quality=100&sign=4e156fe6&sv=2) **Intercom** Effortlessly manage, speak to, and view visitors before they enter your building [](https://help.verkada.com/air-quality/) ![Cover](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F246171046-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FzfrVPow912E2LqKLhtak%252Fuploads%252F2OkYCHOvAiF7sM8FUzSY%252FAQ.png%3Falt%3Dmedia%26token%3D3153ab21-b471-4340-a4f3-d92caf479dd6&width=490&dpr=4&quality=100&sign=93ea9d6&sv=2) **Air Quality Sensors** Get a detailed real-time view of what is happening in your facility [](https://help.verkada.com/new-alarms/) ![Cover](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F246171046-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FzfrVPow912E2LqKLhtak%252Fuploads%252Fe9dEEV5V99OmUy8gZr0p%252FNew%2520Alarms.png%3Falt%3Dmedia%26token%3D75d9150e-a6a5-4d46-9576-6b78915531e3&width=490&dpr=4&quality=100&sign=2128946d&sv=2) **New Alarms** Detect and respond to intruders using our software, devices, and services [](https://help.verkada.com/classic-alarms/) ![Cover](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F246171046-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FzfrVPow912E2LqKLhtak%252Fuploads%252FAgKZNw8c523XItPREIbg%252FClassic%2520Alarms.png%3Falt%3Dmedia%26token%3D0bd63a59-3e72-4a38-96f4-4980a5e617bf&width=490&dpr=4&quality=100&sign=bbed5f03&sv=2) **Classic Alarms** Detect and respond to intruders using our software, devices, and services [](https://help.verkada.com/guest/) ![Cover](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F246171046-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FzfrVPow912E2LqKLhtak%252Fuploads%252FAAnB7Yl61zfit5PEWQuN%252FGuest.png%3Falt%3Dmedia%26token%3D3db74b5f-cfbb-49be-8afd-adaa56835fe5&width=490&dpr=4&quality=100&sign=71636fd1&sv=2) **Guest** Our visitor management system that integrates seamlessly with video security and access control [](https://help.verkada.com/connectivity/) ![Cover](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F246171046-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FzfrVPow912E2LqKLhtak%252Fuploads%252Fhg6VJzibcsaJiw7Z0lz6%252FConnectivity.png%3Falt%3Dmedia%26token%3D07eb91ed-4e6c-4648-a981-6392ab2127a2&width=490&dpr=4&quality=100&sign=8f207bb2&sv=2) **Connectivity** Deploy Verkada products anywhere with cell signal or Wi-Fi [](https://help.verkada.com/command-connector/) ![Cover](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F246171046-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FzfrVPow912E2LqKLhtak%252Fuploads%252FHdNlVcIel8UJXqSVESj0%252FConnector.png%3Falt%3Dmedia%26token%3D647c78f4-baf6-45e0-a654-56395980cb63&width=490&dpr=4&quality=100&sign=722c12d9&sv=2) **Command Connector** Add non-Verkada cameras to your Command organization quickly, easily, and reliably [](https://help.verkada.com/viewing-station/) ![Cover](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F246171046-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FzfrVPow912E2LqKLhtak%252Fuploads%252FdjtudkXMvVGQIUi0nPBu%252FViewing%2520Station.png%3Falt%3Dmedia%26token%3Dafcffe1e-0ed4-42bb-a695-8f07bd472634&width=490&dpr=4&quality=100&sign=e17550a2&sv=2) **Viewing Station** Stream 36 camera feeds simultaneously to any display with user-customizable layouts [](https://help.verkada.com/mailroom/) ![Cover](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F246171046-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FzfrVPow912E2LqKLhtak%252Fuploads%252F7teU5B1kg8mWCdhomHAi%252FMailroom.png%3Falt%3Dmedia%26token%3D42e6040c-8ed3-4d62-b9c2-e2d9a3d8b93c&width=490&dpr=4&quality=100&sign=dcc8ac82&sv=2) **Mailroom** Streamline deliveries with an app to scan packages, notify recipients, and manage deliveries [](https://help.verkada.com/incident-response/) ![Cover](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F246171046-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FzfrVPow912E2LqKLhtak%252Fuploads%252FhzfA0VvzvbZBcGMvS48Q%252FIncident%2520Response.png%3Falt%3Dmedia%26token%3D4223c66d-2ddd-4555-b2d8-3ed64d08d408&width=490&dpr=4&quality=100&sign=ff65c05e&sv=2) **Incident Response** Locate and check in on people's well-being during an emergency [](https://help.verkada.com/security-trailer/) ![Cover](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F246171046-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FzfrVPow912E2LqKLhtak%252Fuploads%252Fg3bK6piWMlDyEP1YCkhi%252FTrailer.png%3Falt%3Dmedia%26token%3D58ebe5f6-caaf-4773-a6bb-9099f68c11cc&width=490&dpr=4&quality=100&sign=3dbb75c0&sv=2) **Security Trailer** Our solar-powered, cloud-managed trailer gives you instant security anywhere Last updated 3 days ago Was this helpful? This site uses cookies to deliver its service and to analyze traffic. By browsing this site, you accept the [privacy policy](https://www.verkada.com/privacy/privacy-policy/) . AcceptReject --- # Government Solutions | Verkada Help **Overview** Verkada Government Solutions is a cloud-managed security platform designed to meet the needs of federal, state, and local agencies. It provides centralized management of cameras, access control, alarms, sensors, and intercoms while ensuring compliance with government security standards, including FIPS 140-2 and TAA. The platform supports secure cloud hosting, SSO, and third-party provisioning to help agencies manage users and maintain consistent access policies. This collection provides detailed guidance on deploying devices, configuring settings, monitoring activity, and maintaining secure, compliant operations in government environments. Check out these links to get started: [Get Started with Government Solutions](https://help.verkada.com/government-solutions/get-started-with-government-solutions) [Why Government Solutions/FIPS Devices?](https://help.verkada.com/government-solutions/compliance/why-government-solutionsfips-devices) [Required Camera Network Settings - Government Solutions](https://help.verkada.com/government-solutions/required-network-settings/required-camera-network-settings-government-solutions) Last updated 1 day ago Was this helpful? --- # Air Quality Sensors | Air Quality | Verkada Help **Overview** Verkada Air Quality Sensors are cloud-managed devices that let you monitor air quality and environmental conditions across your facilities from a single interface. They measure CO₂, temperature, humidity, particulate matter (PM), VOCs, and other indicators, providing real-time insights to help maintain a healthy and safe environment. This collection provides detailed guidance on installing and configuring sensors, monitoring readings, setting up alerts, and maintaining reliable operation. It helps you set up sensors efficiently and keep your environmental monitoring accurate and dependable. Check out these links to get started: [Get Started with Verkada Air Quality Sensors](https://help.verkada.com/air-quality/get-started-with-verkada-air-quality-sensors) [Quick Reference Guide for Verkada Air Quality Sensors](https://help.verkada.com/air-quality/quick-reference-guide-for-verkada-air-quality-sensors) [Air Quality Sensor Network Settings](https://help.verkada.com/air-quality/air-quality-sensor-network-settings) Last updated 1 day ago Was this helpful? --- # Security Trailer | Verkada Help **Overview** The Verkada Security Trailer is a solar-powered, cloud-managed mobile security platform that brings enterprise-grade surveillance to sites without existing infrastructure. It can be deployed to parking lots, construction sites, events, remote areas, or any location where wired power or network connection is unavailable. The trailer supports up to six cameras (or other Verkada devices), includes a built-in PoE switch, and provides power and network via solar panels and an Verkada gateway. This collection provides guidance on selecting the right trailer configuration, installing and commissioning the trailer, adding devices, and managing the setup through Verkada Command. Last updated 1 day ago Was this helpful? --- # Connectivity | Verkada Help **Overview** Verkada Connectivity uses gateways to provide network and power to Verkada devices in locations where traditional wiring is difficult. Gateways support cellular or WiFi connections and can deliver PoE to connected devices, which makes it possible to place cameras and other Verkada hardware in remote or outdoor areas. This collection provides guidance on choosing a gateway, installing it, configuring connectivity, and maintaining reliable operation. It helps you extend your Verkada deployment to sites that need flexible power and network options. Check out these links to get started: [Get Started with the Cellular Gateway](https://help.verkada.com/connectivity/get-started-with-the-cellular-gateway) [Roles and Permissions for Gateway](https://help.verkada.com/connectivity/roles-and-permissions-for-gateway) [Gateways Network Settings](https://help.verkada.com/connectivity/gateways-network-settings) Last updated 1 day ago Was this helpful? --- # Classic Alarms | Verkada Help **Overview** Verkada Classic Alarms is a cloud-managed intrusion detection system designed to secure your facilities with a combination of sensors, door contacts, and sirens. It provides real-time alerts and centralized management, allowing you to monitor alarm activity and respond quickly from a single interface. This collection provides detailed guidance on installing and configuring Classic Alarms, managing notifications and events, and maintaining reliable operation. It helps you deploy alarms efficiently and ensure your security monitoring remains consistent and effective. Check out these links to get started: [Get Started with Verkada Classic Alarms](https://help.verkada.com/classic-alarms/get-started-with-verkada-classic-alarms) [Quick Reference Guide for Verkada Alarms](https://help.verkada.com/classic-alarms/quick-reference-guide-for-verkada-alarms) [Classic Alarms Network Settings](https://help.verkada.com/classic-alarms/classic-alarms-network-settings) Last updated 1 day ago Was this helpful? --- # Viewing Station | Verkada Help The Verkada Viewing Station is a plug-and-play device that streams live video feeds from your Verkada cameras to a display. It lets you monitor multiple camera feeds at once with low latency and smooth playback. This collection walks you through how to set up, claim, and configure a Viewing Station in your organization. You can use your Viewing Station to bring real-time visibility across sites. This is ideal for control rooms, security desks, or anywhere you need a stable, always-on video wall. It supports multiple camera streams, flexible layout configuration, and integrates with other Verkada systems for unified monitoring. Check out these links to get started: [Viewing Station Network Settings](https://help.verkada.com/viewing-station/viewing-station-network-settings) [Smart Tiles](https://help.verkada.com/viewing-station/smart-tiles) [Set Up Your Viewing Station](https://help.verkada.com/viewing-station/set-up-your-viewing-station) Last updated 1 day ago Was this helpful? --- # Command Connector | Verkada Help **Overview** Command Connector lets you integrate non-Verkada cameras into the cloud-based Verkada Command platform, giving you a unified management interface. It provides a cost-effective way to migrate to cloud-based video security while preserving current investments in hardware. This collection guides you through how to add a Command Connector, connect compatible non-Verkada cameras (ONVIF-Profile S), and bring them under Command for centralized viewing and management. Command Connector supports core platform features such as live video monitoring, video retention, and basic analytics such as people and vehicle search. Check out these links to get started: [Get started with Command Connector](https://help.verkada.com/command-connector/get-started-with-command-connector) [Command Connector Network Settings](https://help.verkada.com/command-connector/command-connector-network-settings) [Prepare for a Command Connector Deployment](https://help.verkada.com/command-connector/hardware-installation/prepare-for-a-command-connector-deployment) Last updated 1 day ago Was this helpful? --- # Mailroom | Verkada Help **Overview** Verkada Mailroom is a cloud-managed mail and package management solution that helps organizations track deliveries, notify recipients, and manage inventory from a single interface. The mobile app scans shipping labels and automatically captures recipient names, carriers, tracking numbers, and other key details. After a package is scanned, Mailroom sends notifications by email, SMS, Slack, or Microsoft Teams. When paired with security cameras, Mailroom links scans and pickups to video so you can see when items arrive and when they are collected. This adds clear context and helps prevent lost or misplaced packages. This collection explains how to configure Mailroom sites in Command, add employees, set up pickup locations, enable notifications, and use context cameras. Check out these links to get started: [Roles and Permissions for Mailroom](https://help.verkada.com/mailroom/roles-and-permissions-for-mailroom) [Mailroom Network Settings](https://help.verkada.com/mailroom/mailroom-network-settings) [Customize Your Mailroom Dashboard](https://help.verkada.com/mailroom/configuration-and-setup/customize-your-mailroom-dashboard) Last updated 1 day ago Was this helpful? --- # Incident Response | Verkada Help **Overview** Verkada Incident Response helps organizations track the well-being and location of people during an emergency or incident. It allows you to account for employees, visitors, or students quickly and can be used to reunify students with their guardians in school settings. This collection explains how to set up Incident Response in Verkada Command, including importing sites, managing personnel lists, and building Response Templates that define who must be accounted for, which statuses can be used, and how locations are tracked. [Incident Response Portal](https://help.verkada.com/incident-response/incident-response-portal) [Create Response Templates](https://help.verkada.com/incident-response/create-response-templates) [Review Responses from Command](https://help.verkada.com/incident-response/review-responses-from-command) Last updated 1 day ago Was this helpful? --- # Access Control | Verkada Help **Overview** Verkada Access Control is a cloud-managed door security system that gives you centralized control over who can enter your buildings. The platform combines door controllers, readers, and credential management with a single interface in Command. You can manage users, monitor door activity, and review access events from any location without relying on local servers or fragmented hardware systems. This collection covers how to install and wire door controllers and readers, configure access permissions, manage credentials, review activity logs, and respond to access-related events. It also explains how Access Control works alongside other Verkada products so you can create a unified approach to building security. Check out these links to get started: [Get Started with Verkada Access Control](https://help.verkada.com/access-control/get-started-with-verkada-access-control) [Quick Reference Guide for Verkada Access Control](https://help.verkada.com/access-control/quick-reference-guide-for-verkada-access-control) [Access Control Network Settings](https://help.verkada.com/access-control/access-control-network-settings) * * * You can also check out this video and others on our [video training center.](https://www.youtube.com/@Verkada) Last updated 1 day ago Was this helpful? --- # Intercom | Verkada Help **Overview** Verkada Intercom is a cloud-managed video and audio entry system that lets you manage building access from a single interface. It combines live video, two-way audio, and door control so you can see visitors, communicate with them, and grant access securely. The platform integrates with cameras, access control, and other Verkada products, providing a unified approach to building security. This collection provides detailed guidance on installing and configuring Intercom devices, managing user access and permissions, monitoring activity, and maintaining reliable system performance. Check out these links to get started: [Get Started with Verkada Intercom](https://help.verkada.com/intercom/get-started-with-verkada-intercom) [Quick Reference Guide for Verkada Intercom](https://help.verkada.com/intercom/quick-reference-guide-for-verkada-intercom) [Intercom Network Settings](https://help.verkada.com/intercom/intercom-network-settings) * * * You can also check out this video and others on our [video training center.](https://www.youtube.com/@Verkada) Last updated 1 day ago Was this helpful? --- # New Alarms | Verkada Help **Overview** Verkada Alarms is a cloud-managed intrusion detection system that lets you monitor and protect your facilities from a single interface. It combines sensors, door contacts, and sirens with cloud-based management to provide real-time alerts and centralized control for all your alarm devices. This collection provides detailed guidance on installing and configuring alarms, managing notifications and events, and maintaining reliable operation. It helps you set up alarms efficiently and keep your security monitoring consistent and effective. Check out these links to get started: [Getting Started with Verkada Alarms](https://help.verkada.com/new-alarms/getting-started-with-verkada-alarms) [Roles and Permissions for New Alarms](https://help.verkada.com/new-alarms/roles-and-permissions-for-new-alarms) [Alarms Network Settings](https://help.verkada.com/new-alarms/alarms-specifications/alarms-network-settings) * * * You can also check out this video and others on our [video training center.](https://www.youtube.com/@Verkada) Last updated 1 day ago Was this helpful? --- # Guest | Verkada Help **Overview** Verkada Guest is a cloud-managed visitor management system that lets you streamline check-ins and access for visitors across your facilities. It combines self-service kiosks, badge printing, and digital sign-in with centralized management in Command, giving you real-time visibility into who is on site. The platform integrates with other Verkada products, including cameras and access control, to provide a unified approach to security and visitor management. This collection provides guidance on setting up kiosks, configuring visitor workflows, managing notifications, and maintaining smooth operation. It helps you deploy visitor management efficiently and ensure a safe, organized experience for all guests. Check out these links to get started: [Get Started with Verkada Guest](https://help.verkada.com/guest/get-started-with-verkada-guest) [Roles and Permissions for Guest](https://help.verkada.com/guest/roles-and-permissions-for-guest) [Guest Network Settings](https://help.verkada.com/guest/guest-network-settings) * * * You can also check out this video and others on our [video training center.](https://www.youtube.com/@Verkada) Last updated 1 day ago Was this helpful? --- # Command | Verkada Help **Overview** Verkada Command is a cloud-based platform that lets you manage all Verkada products from a single, secure interface. You can monitor devices and system health, adjust settings, review events, and manage users across all sites in your organization. Command supports SSO and third-party provisioning to centralize authentication and automate user management through your identity provider. The platform unifies cameras, access control, alarms, sensors, intercom, and other products in one place to keep your security operations efficient and organized. This collection guides you through using Command to manage your organization and sites, configure user roles and permissions, monitor device health, track activity across all products, and leverage tools that simplify day-to-day security operations. Check out these links to get started: [Get Started with Verkada Command](https://help.verkada.com/command/get-started-with-verkada-command) [Quick Reference Guide for Verkada Command](https://help.verkada.com/command/quick-reference-guide-for-verkada-command) [Required Network Settings](https://help.verkada.com/command/required-network-settings) * * * You can also check out this video and others on our [video training center.](https://www.youtube.com/@Verkada) Last updated 0 minutes ago Was this helpful? --- # Video Security | Verkada Cameras | Verkada Help **Overview** Verkada Video Security is a cloud-managed camera platform that brings together reliable onboard storage, secure remote access, and centralized administration in Command. The system records and stores video on each device, uploads metadata to the cloud for quick search, and gives you a single interface to view footage, manage settings, and monitor health across all sites. With Verkada, you can deploy cameras on standard PoE networks, manage them without local servers or NVRs, and apply consistent configurations at scale. The platform includes tools for live monitoring, historical video review, people and vehicle analytics, alerts, sharing, and retention management. It also provides built-in security features like automatic firmware updates, encrypted data handling, and role-based user management. This collection helps you understand how the system works, how to install and configure devices, and how to maintain a reliable video security environment across your organization. Check out these links to get started: [Get Started with Verkada Security Cameras](https://help.verkada.com/verkada-cameras/get-started-with-verkada-security-cameras) [Quick Reference Guide for Verkada Cameras](https://help.verkada.com/verkada-cameras/quick-reference-guide-for-verkada-cameras) [Camera Network Settings](https://help.verkada.com/verkada-cameras/camera-specifications/camera-network-settings) * * * You can also check out this video and others on our [video training center.](https://www.youtube.com/@Verkada) --- # Contact Verkada Support - Government Solutions | Government Solutions | Verkada Help Verkada offers dedicated assistance to government customers who need support from representatives in the United States to ensure fast and secure service. Our US-based team is equipped to handle inquiries related to deployment, troubleshooting, or general product guidance. To get in touch, log in to your [Government Solutions Command Account](https://command.verkadagov.com/admin/support) to open a case. See [Contact Verkada Support](https://help.verkada.com/command/need-help/contact-verkada-support) for the support contact information of non-Government Solutions organizations. * * * [](https://help.verkada.com/government-solutions/contact-verkada-support-government-solutions#contact-verkada-support) Contact Verkada Support --------------------------------------------------------------------------------------------------------------------------------------------------- Before you contact Verkada Support, it is best to have a support token ready. See [Enable Support Access](https://help.verkada.com/command/need-help/enable-support-access) for more information on creating a support token. ### [](https://help.verkada.com/government-solutions/contact-verkada-support-government-solutions#command-navigation) Command navigation 1 #### [](https://help.verkada.com/government-solutions/contact-verkada-support-government-solutions#log-in-to-verkada-command) Log in to Verkada [Command](https://command.verkadagov.com/) . 2 #### [](https://help.verkada.com/government-solutions/contact-verkada-support-government-solutions#at-the-bottom-left-click-greater-than-contact-us) At the bottom left, click **\>** **Contact Us**. 3 #### [](https://help.verkada.com/government-solutions/contact-verkada-support-government-solutions#connect-with-verkada-support-via-live-chat-email-or-phone) Connect with Verkada Support via live chat, email, or phone. ### [](https://help.verkada.com/government-solutions/contact-verkada-support-government-solutions#admin-page) Admin page 1 #### [](https://help.verkada.com/government-solutions/contact-verkada-support-government-solutions#in-verkada-command-go-to-all-products-greater-than-admin) In Verkada Command, go to **All Products** > **Admin** . 2 #### [](https://help.verkada.com/government-solutions/contact-verkada-support-government-solutions#in-the-left-navigation-click-support) In the left navigation, click **Support** . 3 #### [](https://help.verkada.com/government-solutions/contact-verkada-support-government-solutions#connect-with-verkada-support-via-live-chat-email-or-phone-1) Connect with Verkada Support via live chat, email, or phone. ### [](https://help.verkada.com/government-solutions/contact-verkada-support-government-solutions#command-app) Command app 1 #### [](https://help.verkada.com/government-solutions/contact-verkada-support-government-solutions#open-your-verkada-command-app) Open your Verkada Command app. 2 #### [](https://help.verkada.com/government-solutions/contact-verkada-support-government-solutions#in-the-top-left-click) In the top left, click . 3 #### [](https://help.verkada.com/government-solutions/contact-verkada-support-government-solutions#at-the-bottom-tap-help-greater-than-live-chat) At the bottom, tap **Help > Live Chat** **.** a. Tap **Messages** to open an existing case. b. Tap **Send us a Message** to start a new chat. Last updated 22 days ago Was this helpful? --- # Configuration and Setup | Government Solutions | Verkada Help [Add Cellular Gateway to Command - Government Solutions](https://help.verkada.com/government-solutions/configuration-and-setup/add-cellular-gateway-to-command-government-solutions) Last updated 1 month ago Was this helpful? --- # Get Started with Government Solutions | Government Solutions | Verkada Help 1 **Send an email to** [**\[email protected\]**](https://help.verkada.com/cdn-cgi/l/email-protection#74131b0211061a19111a00340211061f1510155a171b19) **with the following information:** * Reason for GovCloud organization (e.g., FedRAMP, CJIS, CMMC, NCIC)\* * Name of the organization * Name of the first user to be invited * Email of the first user to be invited 2 **Verkada reviews the request according to our policy and responds within 48 hours. You will receive an email invitation to join the provisioned organization if approved.** 3 **From the invitation email, click Accept Invite.** 4 **On the invite page:** a. Enter your name. b. Set a password. c. Click **Submit.** 5 **A warning notice will appear. After reading, if you wish to proceed, click Acknowledge.** 6 **(Optional) Select one of the options to enable 2FA.** 7 **You can now access your Government Solutions Command organization.** \*Contact your Sales Representative for more information about Verkada’s compliance offerings. Last updated 19 hours ago Was this helpful? --- # Events and Alerts | Government Solutions | Verkada Help [Enable NCIC Alerts](https://help.verkada.com/government-solutions/events-and-alerts/enable-ncic-alerts) Last updated 1 month ago Was this helpful? --- # Compliance | Government Solutions | Verkada Help [CJIS Support Status](https://help.verkada.com/government-solutions/compliance/cjis-support-status) [Why Government Solutions/FIPS Devices?](https://help.verkada.com/government-solutions/compliance/why-government-solutionsfips-devices) [Government Solutions Licensing](https://help.verkada.com/government-solutions/compliance/government-solutions-licensing) Last updated 1 month ago Was this helpful? --- # Required Network Settings | Government Solutions | Verkada Help [Required Access Control Network Settings - Government Solutions](https://help.verkada.com/government-solutions/required-network-settings/required-access-control-network-settings-government-solutions) [Required Command Connector Network Settings - Government Solutions](https://help.verkada.com/government-solutions/required-network-settings/required-command-connector-network-settings-government-solutions) [Required Cellular Gateway Network Settings - Government Solutions](https://help.verkada.com/government-solutions/required-network-settings/required-cellular-gateway-network-settings-government-solutions) [Required Air Quality Sensor Network Settings - Government Solutions](https://help.verkada.com/government-solutions/required-network-settings/required-air-quality-sensor-network-settings-government-solutions) [Required Camera Network Settings - Government Solutions](https://help.verkada.com/government-solutions/required-network-settings/required-camera-network-settings-government-solutions) Last updated 16 days ago Was this helpful? --- # Single Sign-On (SSO) | Government Solutions | Verkada Help [Okta SAML Integration - Government Solutions](https://help.verkada.com/government-solutions/single-sign-on-sso/okta-saml-integration-government-solutions) [Microsoft Entra ID SAML Integration - Government Solutions](https://help.verkada.com/government-solutions/single-sign-on-sso/microsoft-entra-id-saml-integration-government-solutions) Last updated 1 month ago Was this helpful? --- # Why Government Solutions/FIPS Devices? | Government Solutions | Verkada Help U.S. government customers can have their [Verkada Command](https://help.verkada.com/government-solutions/get-started-with-government-solutions) organization hosted in an isolated AWS region designed to host sensitive data and regulated workloads for those organizations that must adhere to strict government security and compliance requirements. For added compliance and data protection, government customers can choose to host their Verkada Command organization in an isolated AWS region built to support sensitive data and regulated workloads. These solutions are ideal for a wide range of government entities to enable them to meet strict security requirements while leveraging modern, cloud-based physical security tools. ### [](https://help.verkada.com/government-solutions/compliance/why-government-solutionsfips-devices#fips) FIPS Verkada FIPS-validated devices meet the U.S. Federal Information Processing Standard [(FIPS) 140-2 encryption standard](https://csrc.nist.gov/pubs/fips/140-2/upd2/final) , as validated by the National Institute of Standards and Technology (NIST). The FIPS 140 government standard specifies the minimum security requirements for cryptographic modules in information technology products. ### [](https://help.verkada.com/government-solutions/compliance/why-government-solutionsfips-devices#supported-organizations) Supported organizations * Any combination of federal, state, or local government entities * Tribal government organizations * Research institutions * Federal contractors * Government contractors * * * [](https://help.verkada.com/government-solutions/compliance/why-government-solutionsfips-devices#supported-product-lines) Supported product lines ------------------------------------------------------------------------------------------------------------------------------------------------------ Verkada is actively working to bring all product lines into the Government Solutions platform to support organizations with stringent compliance and security requirements. The goal is to provide a unified, secure experience across Verkada’s ecosystem while ensuring compatibility with the standards of AWS GovCloud and FIPS 140 encryption. Below are the product lines that are currently supported on the Government Solutions platform: ### [](https://help.verkada.com/government-solutions/compliance/why-government-solutionsfips-devices#verkada-command) Verkada Command Government customers in the United States can choose to use Verkada Command hosted in an isolated AWS region, which gives them the flexibility to use our secure cloud solutions on top of the additional stringent security controls provided by AWS GovCloud. Government Solutions Command organizations support our FIPS-validated camera models, FIPS-validated SV25 Air Quality Sensor, and Verkada Guest. ### [](https://help.verkada.com/government-solutions/compliance/why-government-solutionsfips-devices#video-security) Video Security Verkada’s FIPS-validated cameras incorporate encryption that meets the FIPS 140 and FedRAMP Moderate standards. They have durable, vandal-resistant designs, advanced computer vision features, and are TAA and FY 2019 NDAA compliant. **Product** **Models** Domes CD43-F / CD43-E-F / CD53-F / CD53-E-F / CD63-F / CD63-E-F / CD42-F / CD42-E-F / CD52-F / CD52-E-F Bullets CB52-E-F / CB52-TE-F / CB62-E-F / CB62-TE-F Multisensors CH52-E-F PTZ CP52-E-F / CP63-E-F Fisheye CF83-F ### [](https://help.verkada.com/government-solutions/compliance/why-government-solutionsfips-devices#air-quality-sensors) Air Quality Sensors Verkada Air Quality Sensors help organizations monitor indoor environments for pollutants, unwanted behaviors, and optimal conditions at scale. Sensors integrate with Verkada cameras to provide visual context, including synced footage and People Analytics. Ideal for sensitive areas like bathrooms and locker rooms, they enable privacy-conscious detection of behaviors such as vaping or bullying. U.S. government customers can use Verkada Sensors to meet strict data and compliance requirements. **Product** **Models** Air Quality Sensors SV25-HW-F ### [](https://help.verkada.com/government-solutions/compliance/why-government-solutionsfips-devices#command-connector) Command Connector Verkada’s Command Connector is a FIPS 140 validated solution designed to bridge third-party ONVIF cameras to Verkada Command. It supports encryption standards required for FedRAMP Moderate deployments and enables organizations to view non-Verkada cameras through a single, secure platform. **Product** **Models** Command Connector CC700-16TB-HW-F ### [](https://help.verkada.com/government-solutions/compliance/why-government-solutionsfips-devices#connectivity) Connectivity Verkada Cellular Gateways make it easy to deploy video security in remote or hard-to-wire locations. By connecting to cellular networks and providing Power-over-Ethernet (PoE) to Verkada cameras and other devices, they enable plug-and-play installation without the need for traditional infrastructure. Ideal for sites like construction zones, parking lots, and temporary facilities, Cellular Gateways help ensure reliable connectivity wherever it’s needed. U.S. government customers can rely on this solution to support Verkada’s FIPS-validated cameras in compliance-driven environments. **Product** **Models** Indoor Cellular Gateway GC31-HW Outdoor Cellular Gateway GC31-E-HW ### [](https://help.verkada.com/government-solutions/compliance/why-government-solutionsfips-devices#access) **Access** Verkada Access Control offers a secure, scalable solution for managing physical access to government facilities. Integrated with Verkada Command, it provides unified visibility and management of doors and cameras through a single cloud-based platform. Administrators can configure permissions, monitor door activity in real time, and respond to security events remotely. The system supports role-based access control, automated door schedules, and video-based event verification. U.S. government customers can deploy Verkada’s FIPS-validated hardware within the government hosting environment. Verkada is actively pursuing an APL listing for FICAM compliance, but does not yet meet the full scope of FIPS 201.3. **Product** **Models** Single Door PoE Controller AC12-G-HW 16 Door Access Controller AC62-G-HW Contactless Badge Reader AD34-G-HW Pinpad Contactless Badge Reader AD64-G-HW ### [](https://help.verkada.com/government-solutions/compliance/why-government-solutionsfips-devices#guest) Guest Verkada Guest is a visitor management system that enhances building security while offering a seamless check-in experience with features like touchless entry, document signing, and host notifications. Built on the Verkada Command platform, it integrates with FIPS-validated cameras to monitor visitor activity. U.S. government customers can use Verkada Guest to add compliance and data security. **Product** **Models** Apple 10.2 inch iPad ACCX-TBL-1 Apple 10.9 inch iPad ACCX-TBL-2 Guest in Government Solutions does not support: * [Security Screens](https://help.verkada.com/guest/configuration-and-setup/security-screening-settings) * Access control door integration * The ability to send visitor invitations through a calendar integration ### [](https://help.verkada.com/government-solutions/compliance/why-government-solutionsfips-devices#viewing-station) Viewing station The Viewing Station is identical to our commercial offering. As an Apple device, it uses Apple-managed FIPS certificates. While Verkada does not manage these certificates, we ensure the device runs the latest iOS. Apple [states](https://support.apple.com/en-au/guide/certifications/apc3fa917cb49/web) the device uses FIPS-compliant encryption. **Product** **Models** Viewing Station VX52-HW Last updated 19 hours ago Was this helpful? --- # End-of-Sale Product Updates | Air Quality | Verkada Help Last updated 1 month ago Was this helpful? --- # Hardware Installation | Air Quality | Verkada Help [Installation Guidelines for Sensors](https://help.verkada.com/air-quality/hardware-installation/installation-guidelines-for-sensors) Last updated 1 month ago Was this helpful? --- # Troubleshooting | Air Quality | Verkada Help [Loss of Network Connection for Air Quality Sensors](https://help.verkada.com/air-quality/troubleshooting/loss-of-network-connection-for-air-quality-sensors) Last updated 1 month ago Was this helpful? --- # Air Quality Sensor Network Settings | Air Quality | Verkada Help This article outlines the required network settings that your Verkada [Air Quality Sensors](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) ("sensors") need to communicate with [Verkada Command](https://help.verkada.com/command/get-started-with-verkada-command) . For more information on the required network settings for other Verkada product lines see [Required Network Settings](https://help.verkada.com/command/required-network-settings) . Verkada devices are incompatible with LANs that require proxy servers or Secure Socket Layer (SSL)/Transport Layer Security (TLS) inspection. If either is in use, a bypass for all Verkada devices must be implemented for Verkada devices to communicate with Verkada Command. [](https://help.verkada.com/air-quality/air-quality-sensor-network-settings#status-led) Status LED ------------------------------------------------------------------------------------------------------- A flashing white or flashing blue [status LED](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-status-led) on the front of the sensor indicates the sensor is not communicating with Verkada Command. If you see this behavior, check that the network is set up correctly with the sensor’s requirements. If the problem persists, contact [Verkada Support](https://help.verkada.com/command/need-help/contact-verkada-support) . When sensors are offline, alerts/events do not trigger. They continue to record measurements and sync with Command once they reconnect. [](https://help.verkada.com/air-quality/air-quality-sensor-network-settings#ip-address) IP address ------------------------------------------------------------------------------------------------------- Verkada Air Quality Sensors must be assigned an IPv4 address to communicate on the LAN and to Verkada Command. Verkada sensors use Dynamic Host Configuration Protocol (DHCP) and User Datagram Protocol (UDP) to obtain their IP addresses and network configurations. If you want to have a specific IP address on your sensor device, you can: * Set up a [static IP address through Command](https://help.verkada.com/air-quality/configuration-and-setup/configure-static-ip-addresses-for-air-quality-sensors-sv20-series-only) for SV20 series sensors (SV21, SV23, SV25) * Set a DHCP reservation using the device’s Media Access Control (MAC) address (found on the device’s label or in Command). To configure a static IP address on a sensor device, the device must initially connect to Command and update to the latest firmware using DHCP. Once the update process is complete, it will have the ability to receive the new static IP configuration. [](https://help.verkada.com/air-quality/air-quality-sensor-network-settings#domain-name-system) Domain Name System ----------------------------------------------------------------------------------------------------------------------- Sensors use the DNS server to resolve Verkada’s fully qualified domain names (FQDN) to IP addresses to communicate with them. Your DHCP server tells the sensor where the DNS server is on the network and the sensor communicates using UDP port 53. DNS over HTTPS (DoH) is currently not supported. [](https://help.verkada.com/air-quality/air-quality-sensor-network-settings#power) Power --------------------------------------------------------------------------------------------- Sensors are powered through Power over Ethernet (PoE). This means the network switch needs to provide power to the sensor, or a PoE injector needs to be utilized. For specifics on power requirements, see the [1st generation](https://docs.verkada.com/docs/sensors-overview.pdf) and [2nd generation](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) sensor datasheets. [](https://help.verkada.com/air-quality/air-quality-sensor-network-settings#network-time-security-nts) Network Time Security (NTS) --------------------------------------------------------------------------------------------------------------------------------------- SV20 series sensors can use Network Time Security (NTS) which uses a Secure Socket Layer (SSL) for secure time synchronization, unlike NTP. We recommend you exempt these connections from SSL decryption policies. [](https://help.verkada.com/air-quality/air-quality-sensor-network-settings#firewall-settings) Firewall settings --------------------------------------------------------------------------------------------------------------------- Sensors require access to many endpoints to ensure they can communicate with Command and all features will be accessible. Many customers may want to allow the sensors to communicate with the general required endpoints. These are the general domains to allow, **applicable for all organization-regions**: Copy *.verkada.com - UDP/123 + TCP+UDP/443 time.cloudflare.com - TCP/4460 + UDP/123 If you prefer a more granular allowlist, you can add both IP addresses and full FQDNs to your firewall rules based on the region where your devices are located. Your region is selected when you [create an organization](https://help.verkada.com/command/get-started-with-verkada-command) in Command. ### [](https://help.verkada.com/air-quality/air-quality-sensor-network-settings#region-united-states) Region: United States Copy api.control.verkada.com - TCP+UDP/443 api.global-prod.control.verkada.com - TCP+UDP/443 firmware.control.verkada.com - TCP+UDP/443 index.control.verkada.com - TCP+UDP/443 relay.control.verkada.com - TCP+UDP/443 relay.global-prod.control.verkada.com - TCP+UDP/443 time.control.verkada.com - UDP/123 update.control.verkada.com - TCP+UDP/443 vconductor.command.verkada.com - TCP+UDP/443 vconductor.global-prod.command.verkada.com - TCP+UDP/443 vsensor.command.verkada.com - TCP+UDP/443 time.cloudflare.com - TCP/4460 + UDP/123 ### [](https://help.verkada.com/air-quality/air-quality-sensor-network-settings#region-europe) Region: Europe Copy api.global-prod.control.verkada.com - TCP+UDP/443 api.prod2.control.verkada.com - TCP+UDP/443 index.prod2.control.verkada.com - TCP+UDP/443 relay.global-prod.control.verkada.com - TCP+UDP/443 relay.prod2.control.verkada.com - TCP+UDP/443 time.control.verkada.com - UDP/123 update.control.verkada.com - TCP+UDP/443 vconductor.global-prod.command.verkada.com - TCP+UDP/443 vconductor.prod2.command.verkada.com - TCP+UDP/443 vsensor.prod2.command.verkada.com - TCP+UDP/443 ### [](https://help.verkada.com/air-quality/air-quality-sensor-network-settings#region-australia) Region: Australia Copy api.global-prod.control.verkada.com - TCP+UDP/443 api.prod-ap-syd.control.verkada.com - TCP+UDP/443 index.prod-ap-syd.control.verkada.com - TCP+UDP/443 relay.global-prod.control.verkada.com - TCP+UDP/443 relay.prod-ap-syd.control.verkada.com - TCP+UDP/443 time.control.verkada.com - UDP/123 update.control.verkada.com - TCP+UDP/443 vconductor.global-prod.command.verkada.com - TCP+UDP/443 vconductor.prod-ap-syd.command.verkada.com - TCP+UDP/443 vsensor.prod-ap-syd.command.verkada.com - TCP+UDP/443 Use the [Verkada Network Tester](https://network-tester.support.verkada.com/) to verify your devices can connect to Verkada Command. Select your region and the **Air Quality** product type to run the check. The following endpoints must be allowed on your network for the test to work: * speed.cloudflare.com * network-tester.support.verkada.com Last updated 22 hours ago Was this helpful? --- # Events and Alerts | Air Quality | Verkada Help [Air Quality Alerts Migration](https://help.verkada.com/air-quality/events-and-alerts/air-quality-alerts-migration) [Air Quality Event Analytics](https://help.verkada.com/air-quality/events-and-alerts/air-quality-event-analytics) [Air Quality Sensor Zones](https://help.verkada.com/air-quality/events-and-alerts/air-quality-sensor-zones) [Configure Air Quality Event Alerts](https://help.verkada.com/air-quality/events-and-alerts/configure-air-quality-event-alerts) Last updated 1 month ago Was this helpful? --- # Get Started with Verkada Air Quality Sensors | Air Quality | Verkada Help Verkada Air Quality Sensors offer a variety of different readings to ensure safe air quality and elevate building performance. ⚠️ **Warning**. The Verkada sensors are not life safety devices and do not satisfy the requirements to be used as emergency smoke or carbon monoxide detectors. You need Org Admin and/or Site Admin [permissions](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) for your Verkada Command organization to complete these actions. ### [](https://help.verkada.com/air-quality/get-started-with-verkada-air-quality-sensors#what-you-need) What you need * PoE-enabled switch or PoE injector * DHCP-enabled network * Cat5 or Cat6 cabling [](https://help.verkada.com/air-quality/get-started-with-verkada-air-quality-sensors#create-a-site) Create a site ---------------------------------------------------------------------------------------------------------------------- Sites are the logical way of grouping and managing devices within your Command organization. Site-level permissions make managing and viewing your devices easier. See [Manage Your Sites and Subsites](https://help.verkada.com/verkada-cameras/configuration-and-setup/manage-sites-and-subsites) for more information on site creation and management. [](https://help.verkada.com/air-quality/get-started-with-verkada-air-quality-sensors#add-a-sensor) Add a sensor -------------------------------------------------------------------------------------------------------------------- Sensors can be added from the **Devices** page or directly from a site. At least one sensor needs to be added to Command before you can see the **Air Quality** tab in the **All Products** menu. See [Add a Device to Your Command Account](https://help.verkada.com/verkada-cameras/configuration-and-setup/add-a-device-to-your-command-organization) for more information. #### [](https://help.verkada.com/air-quality/get-started-with-verkada-air-quality-sensors#sensor-readings) Sensor readings Verkada sensors detect a wide variety of readings that are used to track information about your environment. See [Air Quality Sensor Readings](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) for an in-depth explanation of the sensor readings. [](https://help.verkada.com/air-quality/get-started-with-verkada-air-quality-sensors#licensing) Licensing -------------------------------------------------------------------------------------------------------------- Every sensor you manage in Command needs a license. Verkada licensing is applied for each Command organization, and the licenses co-term to a single expiration date. Your licenses may have been automatically added if you claimed your devices via order number. Otherwise, manually add the licenses from the Admin page. See [Manage Your Licenses](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses) for more information on adding and managing licenses. [](https://help.verkada.com/air-quality/get-started-with-verkada-air-quality-sensors#connect-your-sensor) Connect your sensor ---------------------------------------------------------------------------------------------------------------------------------- While Verkada sensors are considered low-voltage devices that do not require a certified electrician to install, we strongly recommend you work with a system integrator or other professional for installation. Refer to the sensor’s [setup guide](https://www.verkada.com/docs/?product=sensors&contentType=setupGuide) for mounting instructions. ### [](https://help.verkada.com/air-quality/get-started-with-verkada-air-quality-sensors#power-and-network) Power and network Verkada sensors use Power over Ethernet (PoE) for power and communication over the LAN. In most cases, sensors will need to connect directly to a standard switch. PoE injectors can be used when a PoE switch is not available. See the sensor’s [datasheet](https://www.verkada.com/docs/?product=sensors&contentType=datasheet) for the power requirements of your specific sensor model. [](https://help.verkada.com/air-quality/get-started-with-verkada-air-quality-sensors#check-network-settings) Check network settings ---------------------------------------------------------------------------------------------------------------------------------------- Verkada sensors are designed to be plug-and-play. However, if your environment includes a firewall with custom rules and policies, you may need to make some configuration changes to get your sensors connected to the cloud. See [Air Quality Sensor Network Settings](https://help.verkada.com/air-quality/air-quality-sensor-network-settings) for more information. If you require your device to have a specific IP address, create a DHCP reservation using the device’s Media Access Control (MAC) address (found on the device’s label). You can also set up [static IP addresses](https://help.verkada.com/air-quality/configuration-and-setup/configure-static-ip-addresses-for-air-quality-sensors-sv20-series-only) in Command for SV20 Series Air Quality Sensor Devices. To configure a static IP address on a sensor device, the device must initially connect to Command and update to the latest firmware using DHCP. Once the update process is complete, it will have the ability to receive the new static IP configuration. [](https://help.verkada.com/air-quality/get-started-with-verkada-air-quality-sensors#configure-alerts) Configure alerts ---------------------------------------------------------------------------------------------------------------------------- Verkada Command allows you to receive push, email, and SMS alerts for events generated in your organization. The ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-91bd70c6d63692bdc09cfe2b790499421775da49%252F05283db7c21547b9b9a924fe0723bd14f6720315.png%3Falt%3Dmedia&width=300&dpr=4&quality=100&sign=461661e3&sv=2) in the bottom left of Command takes you to the **Alerts** page where you can set up and manage alerts. Sensor events include vape detection, tamper detection, air quality index, and more. See [Configure Air Quality Event Alerts](https://help.verkada.com/air-quality/events-and-alerts/configure-air-quality-event-alerts) for more information on sensor events and creating alerts. Last updated 1 day ago Was this helpful? --- # Sensor Data | Air Quality | Verkada Help [Air Quality Sensor Status LED](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-status-led) [Audio Recording with the SV25](https://help.verkada.com/air-quality/sensor-data/audio-recording-with-the-sv25) [Detect and Understand Carbon Monoxide](https://help.verkada.com/air-quality/sensor-data/detect-and-understand-carbon-monoxide) [Manage Your Sensor Dashboard](https://help.verkada.com/air-quality/sensor-data/manage-your-sensor-dashboard) [Air Quality Sensor Power Requirements](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-power-requirements) [Best Practices for Vape Detection](https://help.verkada.com/air-quality/sensor-data/best-practices-for-vape-detection) [Air Quality Sensor Readings](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) [View Air Quality Sensor Data](https://help.verkada.com/air-quality/sensor-data/view-air-quality-sensor-data) [Air Quality Sensor Settings](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-settings) Last updated 1 month ago Was this helpful? --- # Quick Reference Guide for Verkada Air Quality Sensors | Air Quality | Verkada Help [](https://help.verkada.com/air-quality/quick-reference-guide-for-verkada-air-quality-sensors#hardware-installation) Hardware installation ----------------------------------------------------------------------------------------------------------------------------------------------- * [Sensor datasheets](https://www.verkada.com/docs/?product=sensors&contentType=datasheet) * [Sensor setup guides](https://www.verkada.com/docs/?product=sensors&contentType=setupGuide) * [Installation Guidelines for Sensors](https://help.verkada.com/air-quality/hardware-installation/installation-guidelines-for-sensors) [](https://help.verkada.com/air-quality/quick-reference-guide-for-verkada-air-quality-sensors#configuration-and-setup) Configuration and Setup --------------------------------------------------------------------------------------------------------------------------------------------------- * [Air Quality Sensor Network Settings](https://help.verkada.com/air-quality/air-quality-sensor-network-settings) * [Roles and Permissions for Air Quality Sensors](https://help.verkada.com/air-quality/roles-and-permissions-for-air-quality-sensors) * [Bulk Edit Air Quality Sensor Settings](https://help.verkada.com/air-quality/configuration-and-setup/bulk-edit-air-quality-sensor-settings) * [Integrate Verkada Cameras with Air Quality Sensors](https://help.verkada.com/air-quality/configuration-and-setup/integrate-verkada-cameras-with-air-quality-sensors) * [Air Quality Sensor Readings](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) * [Air Quality Sensor Settings](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-settings) * [Best Practices for Vape Detection](https://help.verkada.com/air-quality/sensor-data/best-practices-for-vape-detection) * [Manage Your Sensor Dashboard](https://help.verkada.com/air-quality/sensor-data/manage-your-sensor-dashboard) * [View Air Quality Sensor Data](https://help.verkada.com/air-quality/sensor-data/view-air-quality-sensor-data) [](https://help.verkada.com/air-quality/quick-reference-guide-for-verkada-air-quality-sensors#events-and-alerts) Events and Alerts --------------------------------------------------------------------------------------------------------------------------------------- * [Configure Air Quality Event Alerts](https://help.verkada.com/air-quality/events-and-alerts/configure-air-quality-event-alerts) * [Manage Alerts Across Verkada Products](https://help.verkada.com/verkada-cameras/events-and-alerts/manage-alerts-across-verkada-products) * [Air Quality Sensor Zones](https://help.verkada.com/air-quality/events-and-alerts/air-quality-sensor-zones) * [Air Quality Event Analytics](https://help.verkada.com/air-quality/events-and-alerts/air-quality-event-analytics) [](https://help.verkada.com/air-quality/quick-reference-guide-for-verkada-air-quality-sensors#troubleshooting) Troubleshooting ----------------------------------------------------------------------------------------------------------------------------------- * [Loss of Network Connection for Air Quality Sensors](https://help.verkada.com/air-quality/troubleshooting/loss-of-network-connection-for-air-quality-sensors) Follow [our blog](https://www.verkada.com/blog/) for all our latest features and announcements! Last updated 1 day ago Was this helpful? --- # MT81 Cloud-Managed Security Trailer FAQ | Security Trailer | Verkada Help Review these FAQs to optimize your MT81 Cloud-Managed Security Trailer experience. * * * [](https://help.verkada.com/security-trailer/mt81-cloud-managed-security-trailer-faq#trials-purchasing-and-returns) Trials, purchasing, & returns ------------------------------------------------------------------------------------------------------------------------------------------------------ When should I buy a Verkada trailer vs. a third-party trailer with Verkada cameras and gateways?[](https://help.verkada.com/security-trailer/mt81-cloud-managed-security-trailer-faq#when-should-i-buy-a-verkada-trailer-vs.-a-third-party-trailer-with-verkada-cameras-and-gateways) The MT81 is a cloud-managed, streamlined solution with a standard configuration that works across the United States. We strongly recommend reviewing our two [Verkada-Validated Configurations](https://docs.verkada.com/docs/mt81-security-trailer-datasheet.pdf#page=8) and selecting whichever one better meets your needs for your trailer solution. A customer’s security requirements, budget, and weather forecast will all impact what the best solution is for them. We fully support our ecosystem of Verkada partners to offer tailored solutions for these needs. Is the MT81 available for trial?[](https://help.verkada.com/security-trailer/mt81-cloud-managed-security-trailer-faq#is-the-mt81-available-for-trial) MT81 trials are not available at this time. However, you can request a demo through your Verkada Account Executive or by contacting [\[email protected\]](https://help.verkada.com/cdn-cgi/l/email-protection) . Purchased MT81s can be returned under our 30-day return policy. Customers are responsible for arranging and paying for return shipping. Returns over $250,000 USD are subject to Verkada approval. How can I purchase the MT81?[](https://help.verkada.com/security-trailer/mt81-cloud-managed-security-trailer-faq#how-can-i-purchase-the-mt81) The MT81 is available to purchase through the Verkada partner network. What’s the difference between the two sizes - MT81-6KWH and MT81-13KWH[](https://help.verkada.com/security-trailer/mt81-cloud-managed-security-trailer-faq#whats-the-difference-between-the-two-sizes-mt81-6kwh-and-mt81-13kwh) The only difference is battery capacity. The MT81-6KWH features a single 6.6KWH lithium ion battery pack. The MT81-13KWH features two 6.6KWH lithium ion battery packs for 13.2KWH total capacity. Can I return my trailer?[](https://help.verkada.com/security-trailer/mt81-cloud-managed-security-trailer-faq#can-i-return-my-trailer) Yes, trailers are covered by our 30-day return policy. Customers are responsible for arranging and paying for return shipping. Reach out to [\[email protected\]](https://help.verkada.com/cdn-cgi/l/email-protection) to initiate a return. * * * [](https://help.verkada.com/security-trailer/mt81-cloud-managed-security-trailer-faq#warranty-and-repairs) Warranty & repairs ---------------------------------------------------------------------------------------------------------------------------------- Is the MT81 covered under warranty?[](https://help.verkada.com/security-trailer/mt81-cloud-managed-security-trailer-faq#is-the-mt81-covered-under-warranty) The MT81 includes a parts-only 5-year warranty. The warranty does not cover servicing or field installation. Claims are managed by Verkada Support and fulfilled by Wanco, subject to their lead times. A part on my trailer is broken. What should I do?[](https://help.verkada.com/security-trailer/mt81-cloud-managed-security-trailer-faq#a-part-on-my-trailer-is-broken.-what-should-i-do) Contact Verkada Support and provide your MT81 serial number with photos of the damaged component. Either Verkada Support will troubleshoot and diagnose the issue, or involve Wanco if it is a trailer specific component needing to be investigated. Will Verkada service my trailer?[](https://help.verkada.com/security-trailer/mt81-cloud-managed-security-trailer-faq#will-verkada-service-my-trailer) Trailer servicing and warranty field installation is handled through the Verkada partner network. Who is Wanco?[](https://help.verkada.com/security-trailer/mt81-cloud-managed-security-trailer-faq#who-is-wanco) Wanco is the manufacturer Verkada partners with to build the MT81 trailer. * * * [](https://help.verkada.com/security-trailer/mt81-cloud-managed-security-trailer-faq#third-party-modifications) Third-party modifications ---------------------------------------------------------------------------------------------------------------------------------------------- Can I mount third-party devices on my Verkada trailer?[](https://help.verkada.com/security-trailer/mt81-cloud-managed-security-trailer-faq#can-i-mount-third-party-devices-on-my-verkada-trailer) _Customers may use third-party cameras, gateways, and devices, but mounting_ compatibility isn’t guaranteed. Third-party devices can’t be monitored in Command, have limited data on the Verkada data plan, and may reduce trailer battery life and uptime. The MT81 trailer is not compatible with [Verkada Command Connectors](https://www.verkada.com/security-cameras/command-connector/) . Command Connectors are typically used to monitor 3rd party cameras in Verkada Command but are only recommended for indoor environments. * * * [](https://help.verkada.com/security-trailer/mt81-cloud-managed-security-trailer-faq#command-management) Command management -------------------------------------------------------------------------------------------------------------------------------- How do I add the MT81 or the attached Verkada devices to Command?[](https://help.verkada.com/security-trailer/mt81-cloud-managed-security-trailer-faq#how-do-i-add-the-mt81-or-the-attached-verkada-devices-to-command) MT81s are commissioned into command similar to any other Verkada device. Do all of the Verkada devices mounted on the MT81 need to be in the same organization and site?[](https://help.verkada.com/security-trailer/mt81-cloud-managed-security-trailer-faq#do-all-of-the-verkada-devices-mounted-on-the-mt81-need-to-be-in-the-same-organization-and-site) Not all devices mounted on the MT81 are required to be in the same org, however we strongly recommend all devices are in the same org to ensure a seamless user experience. Can I add third-party trailers to Verkada Command?[](https://help.verkada.com/security-trailer/mt81-cloud-managed-security-trailer-faq#can-i-add-third-party-trailers-to-verkada-command) Trailer management in Verkada Command is exclusively available to the MT series. * * * [](https://help.verkada.com/security-trailer/mt81-cloud-managed-security-trailer-faq#power-and-battery) Power and battery ------------------------------------------------------------------------------------------------------------------------------ What do I do when my battery runs out and I can’t charge via solar?[](https://help.verkada.com/security-trailer/mt81-cloud-managed-security-trailer-faq#what-do-i-do-when-my-battery-runs-out-and-i-cant-charge-via-solar) You can plug your trailer into an outlet using the male AC port. Can I monitor battery usage in Command?[](https://help.verkada.com/security-trailer/mt81-cloud-managed-security-trailer-faq#can-i-monitor-battery-usage-in-command) Yes, current and historical battery charge percentage is available on the stats page in Command. Can I provide supplemental power to the MT81?[](https://help.verkada.com/security-trailer/mt81-cloud-managed-security-trailer-faq#can-i-provide-supplemental-power-to-the-mt81) Yes you can connect shore power or a generator to the trailer to add supplementary power. This is most helpful in times of low sunlight where you may not get a full battery charge during the day. Set up power alerts to be notified if your trailer is running low on battery power, so you can connect supplementary power to ensure consistent device uptime. How long will the charge on my battery last on a single charge?[](https://help.verkada.com/security-trailer/mt81-cloud-managed-security-trailer-faq#how-long-will-the-charge-on-my-battery-last-on-a-single-charge) * Battery lifespan depends on the number of devices on your trailer and the weather. * For most configurations - [including VVC1 and VVC2](https://docs.verkada.com/docs/mt81-security-trailer-datasheet.pdf#page=8) 1. MT81-6KWH will last >2 days without additional charging 2. MT81-13KWH will last > 4 days without additional charging What is the MT81 battery lifespan?[](https://help.verkada.com/security-trailer/mt81-cloud-managed-security-trailer-faq#what-is-the-mt81-battery-lifespan) These lithium ion batteries have a warranty period of 5 years. If a customer buys the 6KWH version and needs a higher capacity, are they able to buy more batteries?[](https://help.verkada.com/security-trailer/mt81-cloud-managed-security-trailer-faq#if-a-customer-buys-the-6kwh-version-and-needs-a-higher-capacity-are-they-able-to-buy-more-batteries) We have a path to upgrade batteries. Contact your account rep or [\[email protected\]](https://help.verkada.com/cdn-cgi/l/email-protection) * * * [](https://help.verkada.com/security-trailer/mt81-cloud-managed-security-trailer-faq#shipping-and-installation) Shipping & installation -------------------------------------------------------------------------------------------------------------------------------------------- How is the MT81 delivered?[](https://help.verkada.com/security-trailer/mt81-cloud-managed-security-trailer-faq#how-is-the-mt81-delivered) MT81 trailers are delivered by flatbed truck. Customers or partners need a forklift for unloading and equipment to tow them to the final location. Are cameras installed on the trailer before shipping?[](https://help.verkada.com/security-trailer/mt81-cloud-managed-security-trailer-faq#are-cameras-installed-on-the-trailer-before-shipping) Trailers do not ship with Verkada devices installed. Installation of the devices is completed by the partner. Last updated 20 hours ago Was this helpful? --- # Configuration and Setup | Air Quality | Verkada Help [Create a Person of Interest for Air Quality sensors](https://help.verkada.com/air-quality/configuration-and-setup/create-a-person-of-interest-for-air-quality-sensors) [Third-Party VMS Integrations for Air Quality Sensor Events](https://help.verkada.com/air-quality/configuration-and-setup/third-party-vms-integrations-for-air-quality-sensor-events) [Configure Static IP Addresses for Air Quality Sensors (SV20 Series Only)](https://help.verkada.com/air-quality/configuration-and-setup/configure-static-ip-addresses-for-air-quality-sensors-sv20-series-only) [Configure BACnet on Air Quality Sensors](https://help.verkada.com/air-quality/configuration-and-setup/configure-bacnet-on-air-quality-sensors) [BACnet for Verkada Air Quality Sensors](https://help.verkada.com/air-quality/configuration-and-setup/bacnet-for-verkada-air-quality-sensors) [Air Quality Sensor Calibration](https://help.verkada.com/air-quality/configuration-and-setup/air-quality-sensor-calibration) [Bulk Edit Air Quality Sensor Settings](https://help.verkada.com/air-quality/configuration-and-setup/bulk-edit-air-quality-sensor-settings) [Delete Air Quality Sensors from Command](https://help.verkada.com/air-quality/configuration-and-setup/delete-air-quality-sensors-from-command) [Integrate Verkada Cameras with Air Quality Sensors](https://help.verkada.com/air-quality/configuration-and-setup/integrate-verkada-cameras-with-air-quality-sensors) Last updated 1 month ago Was this helpful? --- # Roles and Permissions for Gateway | Connectivity | Verkada Help This article describes the set of roles and associated permissions for Verkada [Gateways](https://docs.verkada.com/docs/gc31-cellular-gateway-datasheet.pdf) . For more information on roles and permissions for other Verkada product lines, see [Roles and Permissions for Command](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) . * **Site-level roles** determine the access a user or group has to devices in the site. * **Org-level roles** allow users or groups to manage permissions and devices at a global level. * **Permissions** are set using roles, which define the level of access users and groups have to devices and settings within an organization and its sites. * * * ### [](https://help.verkada.com/connectivity/roles-and-permissions-for-gateway#permissions-considerations) Permissions considerations * Subsites inherit permissions from all parent sites, including the ultimate parent. * Users can belong to multiple groups. When roles conflict, the user receives the **highest role** granted directly or through any group. * Group-assigned roles can be manually upgraded but not downgraded. Remove the user from the group with the higher role to downgrade their access. * * * [](https://help.verkada.com/connectivity/roles-and-permissions-for-gateway#site-level-roles) Site-level roles ------------------------------------------------------------------------------------------------------------------ No Access[](https://help.verkada.com/connectivity/roles-and-permissions-for-gateway#no-access) A No Access user cannot view gateways within a site. Live-Only Viewer[](https://help.verkada.com/connectivity/roles-and-permissions-for-gateway#live-only-viewer) A Live-Only Viewer user cannot view gateways within a site. Site Viewer[](https://help.verkada.com/connectivity/roles-and-permissions-for-gateway#site-viewer) Site Viewers can: * Access Gateway Home page * Access Gateway Details Page * Run Speed test * View connected devices * View historical power usage * View Activity logs * View data graphs * Set up alerts Site Admin[](https://help.verkada.com/connectivity/roles-and-permissions-for-gateway#site-admin) Site Admins can do everything Site Viewers can as well as: * Claim Device * Setup Device * Manage Device * Delete Device * Manage data License * Access Gateway Home page * Access Gateway Details Page * Run Speed test * Run Packet capture * View connected devices * Power cycle ports * View historical power usage * Switch to WAN mode * View Activity logs * Claim connected devices * Change network settings * Toggle smart data usage * View data graphs * Identify Device * Reboot Device * Set up alerts * * * [](https://help.verkada.com/connectivity/roles-and-permissions-for-gateway#org-level-roles) Org-level roles ---------------------------------------------------------------------------------------------------------------- Org Admin[](https://help.verkada.com/connectivity/roles-and-permissions-for-gateway#org-admin) Org Admins can: * Claim SW License * Claim data License * * * [](https://help.verkada.com/connectivity/roles-and-permissions-for-gateway#set-permissions) Set permissions ---------------------------------------------------------------------------------------------------------------- You can set site permissions for existing users and groups by managing user roles, groups, or sites. You will have access to all cameras, viewing stations, air quality sensors, intercoms, gateways, New Alarms, and Command Connectors once you have been granted permissions for a site. Users[](https://help.verkada.com/connectivity/roles-and-permissions-for-gateway#users) 1. In Verkada Command, go to **All Products > Admin**. 2. Under **Org Settings > Users & Permissions**, select **Users**. 3. Select a user. 4. At the top right, click **Manage Roles**. 1. Set the needed permissions. 2. Click **Save**. Groups[](https://help.verkada.com/connectivity/roles-and-permissions-for-gateway#groups) 1. In Verkada Command, go to **All Products > Admin**. 2. Under **Org Settings > Users & Permissions**, select **Groups**. 3. Select a group. 4. At the top, select **Site Roles > Manage Roles**. 1. Set the needed permissions. 2. Click **Save**. Sites[](https://help.verkada.com/connectivity/roles-and-permissions-for-gateway#sites) 1. In Verkada Command, go to **All Products > Admin**. 2. In the left navigation, select **Sites**. 3. At the top left, click **Manage Sites**. 4. Select a site to manage and in the right pane, click **Manage**. 1. In the top right, click **Add** to add a new user or group. 2. Select an existing user or group to edit their permissions. Last updated 22 hours ago Was this helpful? --- # Classic Alarms Network Settings | Classic Alarms | Verkada Help This article is a guide for classic Alarms. Refer to this [article](https://help.verkada.com/new-alarms/alarms-specifications/alarms-network-settings) if you have new Alarms. See [New Alarms vs Classic Alarms](https://help.verkada.com/new-alarms/new-alarms-vs-classic-alarms) if you are unsure which version of Alarms you have. * * * This article outlines the required network settings that your Verkada Classic Alarms devices need to communicate with [Verkada Command](https://help.verkada.com/command/get-started-with-verkada-command) . For more information on the required network settings for other Verkada product lines see [Required Network Settings](https://help.verkada.com/command/required-network-settings) . Verkada devices are incompatible with LANs that require proxy servers or Secure Socket Layer (SSL)/Transport Layer Security (TLS) inspection. If either is in use, a bypass for all Verkada devices must be implemented for Verkada devices to communicate with Verkada Command. [](https://help.verkada.com/classic-alarms/classic-alarms-network-settings#ip-address) IP address ------------------------------------------------------------------------------------------------------ Alarms devices must be assigned an IPv4 address to communicate on the LAN and to Verkada Command. Alarms devices use Dynamic Host Configuration Protocol (DHCP) and User Datagram Protocol (UDP) to obtain their IP addresses and network configurations. If you require your Alarms device to have a specific IP address, create a DHCP reservation using the device’s Media Access Control (MAC) address (found on the device’s label). [](https://help.verkada.com/classic-alarms/classic-alarms-network-settings#domain-name-system) Domain Name System ---------------------------------------------------------------------------------------------------------------------- Alarms devices use the DNS server to resolve Verkada’s fully qualified domain names (FQDN) to IP addresses to communicate with them. Your DHCP server tells the Alarms device where the DNS server is on the network and the Alarms device communicates using UDP port 53. DNS over HTTPS (DoH) is currently not supported. [](https://help.verkada.com/classic-alarms/classic-alarms-network-settings#power) Power -------------------------------------------------------------------------------------------- Some Alarms devices are powered through Power over Ethernet (PoE). This means the network switch needs to provide power to them, or a PoE injector needs to be utilized. For specifics on power requirements, see the [Alarms device’s datasheet](https://www.verkada.com/docs/?product=alarms&contentType=datasheet) . [](https://help.verkada.com/classic-alarms/classic-alarms-network-settings#firewall-settings) Firewall settings -------------------------------------------------------------------------------------------------------------------- Alarms devices require access to many endpoints to ensure they can communicate with Command and all features will be accessible. Many customers may want to allow the devices to communicate with the general required endpoints. These are the general domains to allow, **applicable for all organization-regions**: Copy 34.216.15.26 - UDP/123 *.verkada.com - UDP/123 + TCP+UDP/443 *.appcenter.ms - TCP/443 global.turn.twilio.com - TCP/443 If you prefer a more granular allowlist, you can add IP addresses, full FQDNs, and wildcard domains to your firewall rules based on the region where your devices are located. Your region is selected when you [create an organization](https://help.verkada.com/command/get-started-with-verkada-command) in Command. ### [](https://help.verkada.com/classic-alarms/classic-alarms-network-settings#region-united-states) Region: United States Copy 34.216.15.26 - UDP/123 alarms.control.verkada.com - TCP+UDP/443 alarms.global-prod.control.verkada.com - TCP+UDP/443 api.control.verkada.com - TCP+UDP/443 api.global-prod.control.verkada.com - TCP+UDP/443 firmware.control.verkada.com - TCP+UDP/443 index.control.verkada.com - TCP+UDP/443 relay.control.verkada.com - TCP+UDP/443 relay.global-prod.control.verkada.com - TCP+UDP/443 time.control.verkada.com - UDP/123 update.control.verkada.com - TCP+UDP/443 valarm.command.verkada.com - TCP+UDP/443 valarm.global-prod.command.verkada.com - TCP+UDP/443 vconductor.command.verkada.com - TCP+UDP/443 vconductor.global-prod.command.verkada.com - TCP+UDP/443 *.appcenter.ms - TCP/443 global.turn.twilio.com - TCP/443 ### [](https://help.verkada.com/classic-alarms/classic-alarms-network-settings#region-europe) Region: Europe Copy alarms.global-prod.control.verkada.com - TCP+UDP/443 alarms.prod2.control.verkada.com - TCP+UDP/443 api.prod2.control.verkada.com - TCP+UDP/443 api.global-prod.control.verkada.com - TCP+UDP/443 index.prod2.control.verkada.com - TCP+UDP/443 relay.global-prod.control.verkada.com - TCP+UDP/443 relay.prod2.control.verkada.com - TCP+UDP/443 time.control.verkada.com - UDP/123 update.control.verkada.com - TCP+UDP/443 valarm.global-prod.command.verkada.com - TCP+UDP/443 valarm.prod2.command.verkada.com - TCP+UDP/443 vbroadcast.command.verkada.com - TCP+UDP/443 vbroadcast.prod2.control.verkada.com - TCP+UDP/443 vconductor.global-prod.command.verkada.com - TCP+UDP/443 vconductor.prod2.command.verkada.com - TCP+UDP/443 ### [](https://help.verkada.com/classic-alarms/classic-alarms-network-settings#all-regions) All regions BC51s **in all regions** require these endpoints: Copy *.apple.com - TCP/80 *.apple.com - TCP/443 *.apple.com - TCP/2197 *.apple.com - TCP/5223 *.apple.com - UDP/123 crl.entrust.net - TCP/80 crl3.digicert.com - TCP/80 crl4.digicert.com - TCP/80 global.stun.twilio.com - UDP/3478 global.turn.twilio.com - UDP/3478 *.mzstatic.com - TCP/80 *.mzstatic.com - TCP/443 ocsp.digicert.com - TCP/80 ocsp.entrust.net - TCP/80 vmdm.command.verkada.com - TCP+UDP/443 vmdm.global-prod.command.verkada.com - TCP+UDP/443 BK21s in **all regions** require these endpoints: Copy time.cloudflare.com - TCP/4460 time.cloudflare.com - UDP/123 BZ11s in **all regions** require these endpoints: Copy global.stun.twilio.com - UDP/3478 global.turn.twilio.com - UDP/3478 Use the [Verkada Network Tester](https://network-tester.support.verkada.com/) to verify your devices can connect to Verkada Command. Select your region and the **Classic Alarms** product type to run the check. The following endpoints must be allowed on your network for the test to work: * speed.cloudflare.com * network-tester.support.verkada.com Last updated 23 hours ago Was this helpful? --- # Get Started with the Cellular Gateway | Connectivity | Verkada Help Verkada’s [GC31 Cellular Gateway](https://www.verkada.com/cellular-gateway) helps you connect Verkada products in remote locations, such as parks, parking lots, construction sites, oil and gas drilling sites, school buses, and even police cars. Anyone can easily set up the GC31 with its Power over Ethernet (PoE) input and PoE output. You can also easily manage and troubleshoot the router remotely via [Verkada Command](https://help.verkada.com/command/get-started-with-verkada-command) . The GC31 natively integrates with Verkada products to enable faster setup, remote troubleshooting, and more efficient data usage. The GC31 instantly recognizes any Verkada device you connect to it, eliminating the need to input serial numbers or scan QR codes during device setup. You can track data usage for each connected device and receive alerts if a device is offline. More key features include: * View the status and GPS location of your gateways * See which cell tower each gateway is using * Remotely run packet capture and speed tests * Remotely power cycle devices * Recognize connected Verkada devices and streamline setup. [](https://help.verkada.com/connectivity/get-started-with-the-cellular-gateway#step-1-set-up-verkada-command) Step 1: Set up Verkada Command ------------------------------------------------------------------------------------------------------------------------------------------------- **Required**. You must create a [Verkada Command account](https://command.verkada.com/register) to activate and configure a GC31. You must be an Org Admin to configure a GC31. Learn more about [Roles and Permissions for Command](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) . [](https://help.verkada.com/connectivity/get-started-with-the-cellular-gateway#step-2-set-up-the-hardware) Step 2: Set up the hardware ------------------------------------------------------------------------------------------------------------------------------------------- Follow the steps to set up, install (wire and mount) the GC31 ([indoor](https://docs.verkada.com/docs/gc31-indoor-cellular-gateway-install-guide.pdf) ) | GC31-E ([outdoor](https://docs.verkada.com/docs/gc31e-outdoor-cellular-gateway-install-guide.pdf) ). * * * [](https://help.verkada.com/connectivity/get-started-with-the-cellular-gateway#troubleshoot-the-gc31) Troubleshoot the GC31 -------------------------------------------------------------------------------------------------------------------------------- If you experience any issues with your GC31, we recommend following these steps: 1 **Power cycle the GC31.** 2 **If the device connected to the GC31 is not getting power, check for the following:** * Is the GC31 powered on? * If not, check the power input to the GC31. * Is the GC31 powered by a PoE injector? * Check if the injector is rated to provide enough power (must be 90W) to the GC31 and devices connected to it. * Check if the ethernet cable is connected properly and is verified. * Is the gateway powered through the terminal block? * Check if the power input line is rated 12–36V and is providing enough wattage to power the GC31 and devices connected to it. * Is the GC31 powered through an AC/DC power adapter? * Check if the power input line is rated 12–36V and is providing enough wattage to power the GC31 and devices connected to it. * * * [](https://help.verkada.com/connectivity/get-started-with-the-cellular-gateway#faq) FAQ -------------------------------------------------------------------------------------------- How should I manage the cellular connectivity?[](https://help.verkada.com/connectivity/get-started-with-the-cellular-gateway#how-should-i-manage-the-cellular-connectivity) A common issue with the GC31 is that the cellular connectivity might not be powerful enough. If this is the case, consider external/directional antennas to increase the signal strength and connectivity. What if I have a weak connection?[](https://help.verkada.com/connectivity/get-started-with-the-cellular-gateway#what-if-i-have-a-weak-connection) If cameras don’t have a good connection, when making changes, such as enabling analytics, the CV image might not get downloaded properly. A weak connection might lead to issues with uploading and downloading data, resulting in degraded device performance. The only way to resolve this issue is to reboot the camera so that it attempts again. Last updated 22 hours ago Was this helpful? --- # Roles and Permissions for Classic Alarms | Classic Alarms | Verkada Help This article is a guide for classic Alarms. Refer to this [article](https://help.verkada.com/new-alarms/roles-and-permissions-for-new-alarms) if you have new Alarms. See [New Alarms vs Classic Alarms](https://help.verkada.com/new-alarms/new-alarms-vs-classic-alarms) if you are unsure which version of Alarms you have. * * * This article describes the set of roles and associated permissions for [Verkada Classic Alarms](https://docs.verkada.com/docs/alarms-professional-monitoring-overview.pdf) . For more information on roles and permissions for other Verkada product lines, see [Roles and Permissions for Command](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) . * **Site-level roles** determine the access a user or group has to devices in the site. * **Org-level roles** allow users or groups to manage permissions and devices at a global level. * **Permissions** are set using roles, which define the level of access users and groups have to devices and settings within an organization and its sites. * * * [](https://help.verkada.com/classic-alarms/roles-and-permissions-for-classic-alarms#site-level-roles) Site-level roles --------------------------------------------------------------------------------------------------------------------------- No Access[](https://help.verkada.com/classic-alarms/roles-and-permissions-for-classic-alarms#no-access) * By default, cannot arm/disarm Alarm sites. * Unable to view any details about Alarm sites in Command. * When explicitly granted alarm user permissions, can arm/disarm an Alarm site in Command and from the Alarms mobile app. Live-Only Viewer[](https://help.verkada.com/classic-alarms/roles-and-permissions-for-classic-alarms#live-only-viewer) * By default, cannot arm/disarm Alarm sites. * When explicitly granted alarm user permissions, can arm/disarm an Alarm site in Command and from the Alarms mobile app. * If Arm/Disarm Geofencing is enabled, the user will only be able to arm/disarm sites from the Verkada Alarms Mobile App. * See live video and new events on the Alarm site page. Site Viewer[](https://help.verkada.com/classic-alarms/roles-and-permissions-for-classic-alarms#site-viewer) * By default, cannot arm/disarm Alarm sites. * When explicitly granted alarm user permissions, can arm/disarm an Alarm site in Command and from the Alarms mobile app. * If Arm/Disarm Geofencing is enabled, the user will only be able to arm/disarm sites from the Verkada Alarms Mobile App. * View all alarm activity and event history with historical footage. * Listen in and initiate talk-downs to the alarm console. Site Admin[](https://help.verkada.com/classic-alarms/roles-and-permissions-for-classic-alarms#site-admin) * By default, can arm/disarm sites via Command and the Alarms mobile app. You can find the arm/disarm capability in the user settings profile (**Site Access** > **Alarm User** checkbox). * Update all site settings, including trigger events and alarm response notifications/actions, via the Command and Alarms mobile apps. * Add or remove Verkada devices and wired inputs/outputs on the site. * View all alarm activity and event history with historical video. * Listen in and initiate talk-downs to the alarm console. You also need Org Admin permissions to generate key codes. [](https://help.verkada.com/classic-alarms/roles-and-permissions-for-classic-alarms#org-level-roles) Org-level roles ------------------------------------------------------------------------------------------------------------------------- Org Admin[](https://help.verkada.com/classic-alarms/roles-and-permissions-for-classic-alarms#org-admin) * Can generate user key codes. * By default, can arm/disarm sites via Command and the Alarms mobile app. You can find the arm/disarm capability in the user settings profile (**Site Access** > **Alarm User** checkbox). * Set up new alarm sites and change all site settings, including trigger events and alarm response notifications/actions via Command and the Alarms mobile app. * Add or remove Verkada devices and wired inputs/outputs on the site. * View all alarm activity and event history with historical video. * Listen in and initiate talk-downs to the alarm console. * * * [](https://help.verkada.com/classic-alarms/roles-and-permissions-for-classic-alarms#set-permissions) Set permissions ------------------------------------------------------------------------------------------------------------------------- Users[](https://help.verkada.com/classic-alarms/roles-and-permissions-for-classic-alarms#users) In Verkada Command, go to All Products > Admin .UnderOrg Settings, select Users.Select a user.At the top right, click Manage Roles.a. Check the Alarm User box. b. Click Save. Groups[](https://help.verkada.com/classic-alarms/roles-and-permissions-for-classic-alarms#groups) In Verkada Command, go to All Products > Admin .UnderOrg Settings, select Groups.Select a group.At the top, select Site Roles > Manage Roles.a. Check the Alarm User box. b. Click Save. Sites[](https://help.verkada.com/classic-alarms/roles-and-permissions-for-classic-alarms#sites) In Verkada Command, go to All Products > Admin .In the left navigation, select Sites.Select a site to manage and in the right pane, click Manage .a. In the top right, click Add to add a new user or group. b. Select an existing user or group to edit their permissions. Last updated 23 hours ago Was this helpful? --- # Quick Reference Guide for Verkada Alarms | Classic Alarms | Verkada Help [](https://help.verkada.com/classic-alarms/quick-reference-guide-for-verkada-alarms#hardware-installation) Hardware installation ------------------------------------------------------------------------------------------------------------------------------------- * [Alarms datasheets](https://www.verkada.com/docs/?product=alarms&contentType=datasheet) * [Alarms setup guides](https://www.verkada.com/docs/?product=alarms&contentType=setupGuide) * [Alarm Setup and Install Best Practices](https://help.verkada.com/classic-alarms/hardware-installation/alarm-setup-and-install-best-practices) * [Set Up Your Wireless Alarm Devices](https://help.verkada.com/classic-alarms/hardware-installation/set-up-your-wireless-alarm-devices) [](https://help.verkada.com/classic-alarms/quick-reference-guide-for-verkada-alarms#configuration-and-setup) Configuration and Setup ----------------------------------------------------------------------------------------------------------------------------------------- * [Add an Alarm to Your Site](https://help.verkada.com/classic-alarms/configuration-and-setup/classic-alarms-sites) * [Configure Alarms Site Settings](https://help.verkada.com/classic-alarms/configuration-and-setup/configure-classic-alarms-site-settings) * [Set Up and Install Wireless Sensors](https://help.verkada.com/classic-alarms/configuration-and-setup/set-up-and-install-wireless-sensors) * [Set Up the BC82 Alarm Console](https://help.verkada.com/classic-alarms/hardware-installation/set-up-the-bc82-alarm-console) * [How to Arm/Disarm Your Alarm Site](https://help.verkada.com/classic-alarms/configuration-and-setup/how-to-armdisarm-your-alarm-site) [](https://help.verkada.com/classic-alarms/quick-reference-guide-for-verkada-alarms#events-and-alerts) Events and Alerts ----------------------------------------------------------------------------------------------------------------------------- * [Configure Alarms Event Alerts](https://help.verkada.com/classic-alarms/events-and-alerts/configure-alarms-event-alerts) * [Manage Alerts Across Verkada Products](https://help.verkada.com/verkada-cameras/events-and-alerts/manage-alerts-across-verkada-products) * [Configure Camera Alarm Trigger Events](https://help.verkada.com/classic-alarms/events-and-alerts/configure-camera-alarm-trigger-events) [](https://help.verkada.com/classic-alarms/quick-reference-guide-for-verkada-alarms#troubleshooting) Troubleshooting ------------------------------------------------------------------------------------------------------------------------- * [Troubleshoot Inrush Current Issues](https://help.verkada.com/classic-alarms/troubleshooting/troubleshoot-inrush-current-issues) Follow [our blog](https://www.verkada.com/blog/) for all our latest features and announcements! Last updated 1 day ago Was this helpful? --- # Gateways Network Settings | Connectivity | Verkada Help This article outlines the required network settings that your Verkada [Gateways](https://docs.verkada.com/docs/gc31-cellular-gateway-datasheet.pdf) need to communicate with [Verkada Command](https://help.verkada.com/command/get-started-with-verkada-command) . The gateways can connect to your network by utilizing the [WAN Failover](https://help.verkada.com/connectivity/configuration-and-setup/use-cellular-gateways-for-wan-failover) mode. For more information on the required network settings for other Verkada product lines, see [Required Network Settings](https://help.verkada.com/command/required-network-settings) . Verkada devices are incompatible with LANs that require proxy servers or Secure Socket Layer (SSL)/Transport Layer Security (TLS) inspection. If either is in use, a bypass for all Verkada devices must be implemented for Verkada devices to communicate with Verkada Command. [](https://help.verkada.com/connectivity/gateways-network-settings#status-led) **Status LED** -------------------------------------------------------------------------------------------------- A flashing blue status LED on the gateway indicates the device is not communicating with Command. Check the [status LED](https://help.verkada.com/connectivity/configuration-and-setup/cellular-gateway-status-leds) doc for explanations of each LED pattern. If you see this behavior, check that the network is set up with the gateway’s requirements. If the problem persists, contact [Verkada Support](https://help.verkada.com/command/need-help/contact-verkada-support) . When gateways are offline, alerts/events do not trigger. They continue to record data and sync with Command once they reconnect. [](https://help.verkada.com/connectivity/gateways-network-settings#ip-address) **IP address** -------------------------------------------------------------------------------------------------- Verkada gateways must be assigned an IPv4 address to communicate on the LAN and to Verkada Command. Gateways use Dynamic Host Configuration Protocol (DHCP) and User Datagram Protocol (UDP) to obtain their IP addresses and network configurations. [](https://help.verkada.com/connectivity/gateways-network-settings#domain-name-system) **Domain Name System** ------------------------------------------------------------------------------------------------------------------ Verkada gateways use the DNS server to resolve Verkada’s fully qualified domain names (FQDN) to IP addresses to communicate with them. Your DHCP server tells the gateway where the DNS server is on the network and the gateway communicates using UDP port 53. DNS over HTTPS (DoH) is currently not supported. [](https://help.verkada.com/connectivity/gateways-network-settings#power) **Power** ---------------------------------------------------------------------------------------- Verkada GC31-Es are powered through Power over Ethernet (PoE). This means the network switch needs to provide power to the GC31-E, or a PoE injector needs to be utilized. A GC31 is powered through a barrel-jack adapter. For specifics on power requirements, see the [gateway’s datasheet](https://docs.verkada.com/docs/gc31-cellular-gateway-datasheet.pdf) . [](https://help.verkada.com/connectivity/gateways-network-settings#firewall-settings) **Firewall settings** ---------------------------------------------------------------------------------------------------------------- Gateways require access to many endpoints to ensure they can communicate with Command and all features will be accessible. Many customers may want to allow the gateways to communicate with the general required endpoints. These are the general domains to allow, **applicable for all organization-regions:** Copy 34.216.15.26 - UDP/123 *.verkada.com - UDP/123 + TCP+UDP/443 If you prefer a more granular allowlist, you can add both IP addresses and full FQDNs to your firewall rules based on the region where your devices are located. Your region is selected when you [create an organization](https://help.verkada.com/command/get-started-with-verkada-command) in Command. ### [](https://help.verkada.com/connectivity/gateways-network-settings#region-united-states) **Region: United States** Copy 34.216.15.26 - UDP/123 api.control.verkada.com - TCP+UDP/443 api.global-prod.control.verkada.com - TCP+UDP/443 firmware.control.verkada.com - TCP+UDP/443 index.control.verkada.com - TCP+UDP/443 relay.control.verkada.com - TCP+UDP/443 relay.global-prod.control.verkada.com - TCP+UDP/443 time.control.verkada.com - UDP/123 update.control.verkada.com - TCP+UDP/443 vconductor.command.verkada.com - TCP+UDP/443 vconductor.global-prod.command.verkada.com - TCP+UDP/443 vnet.command.verkada.com - TCP+UDP/443 ### [](https://help.verkada.com/connectivity/gateways-network-settings#region-europe) **Region: Europe** Copy api.global-prod.control.verkada.com - TCP+UDP/443 api.prod2.control.verkada.com - TCP+UDP/443 index.prod2.control.verkada.com - TCP+UDP/443 relay.global-prod.control.verkada.com - TCP+UDP/443 relay.prod2.control.verkada.com - TCP+UDP/443 time.control.verkada.com - UDP/123 update.control.verkada.com - TCP+UDP/443 vconductor.global-prod.command.verkada.com - TCP+UDP/443 vconductor.prod2.command.verkada.com - TCP+UDP/443 vnet.prod2.command.verkada.com - TCP+UDP/443 ### [](https://help.verkada.com/connectivity/gateways-network-settings#region-australia) **Region: Australia** Copy api.global-prod.control.verkada.com - TCP+UDP/443 api.prod-ap-syd.control.verkada.com - TCP+UDP/443 index.prod-ap-syd.control.verkada.com - TCP+UDP/443 relay.global-prod.control.verkada.com - TCP+UDP/443 relay.prod-ap-syd.control.verkada.com - TCP+UDP/443 time.control.verkada.com - UDP/123 update.control.verkada.com - TCP+UDP/443 vconductor.global-prod.command.verkada.com - TCP+UDP/443 vconductor.prod-ap-syd.command.verkada.com - TCP+UDP/443 vnet.prod-ap-syd.command.verkada.com - TCP+UDP/443 Use the [Verkada Network Tester](https://network-tester.support.verkada.com/) to verify your devices can connect to Verkada Command. Select your region and the **Gateways** product type to run the check. The following endpoints must be allowed on your network for the test to work: * speed.cloudflare.com * network-tester.support.verkada.com Last updated 22 hours ago Was this helpful? --- # Required Camera Network Settings - Government Solutions | Government Solutions | Verkada Help Verkada devices need to communicate with a [Government Solution Command organization](https://www.verkada.com/solutions/government-grade) via their local network. In most cases, minimal updates to your network settings are needed. Additional configuration may be required for complex or highly secure networks. See [Required Network Settings](https://help.verkada.com/command/required-network-settings) for more information on the required network settings for other Verkada product lines. * * * [](https://help.verkada.com/government-solutions/required-network-settings/required-camera-network-settings-government-solutions#compatibility) Compatibility ------------------------------------------------------------------------------------------------------------------------------------------------------------------ Verkada devices are incompatible with local area networks (LANs) that require proxy servers or Secure Socket Layer (SSL)/Transport Layer Security (TLS) inspection. If either is in use, a bypass for all Verkada devices must be implemented for your Verkada devices to communicate with Verkada Command. [](https://help.verkada.com/government-solutions/required-network-settings/required-camera-network-settings-government-solutions#ip-address) IP address ------------------------------------------------------------------------------------------------------------------------------------------------------------ Verkada devices must be assigned an IPv4 address to communicate on the LAN and to Verkada Command through the internet. By default, all Verkada devices use Dynamic Host Configuration Protocol (DHCP) and User Datagram Protocol (UDP) to obtain their IP addresses and network configurations. If you require your device to have a specific IP address, create a DHCP reservation using the device’s Media Access Control (MAC) address (found on the device’s label). You can also set up [static IP addresses](https://help.verkada.com/verkada-cameras/hardware-installation/advanced-installation/configure-static-ip-addresses-for-cameras) in Command for cameras. Verkada devices may utilize path MTU discovery to determine the maximum transmission unit of the network path. Therefore, it is necessary to permit ICMP Fragmentation Needed (Type 3, Code 4) and ICMPv6 Packet Too Big (Type 2) packets. Ensure your firewall(s) are configured to permit this in the return path to your Verkada devices. [](https://help.verkada.com/government-solutions/required-network-settings/required-camera-network-settings-government-solutions#domain-name-system) Domain Name System ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Verkada devices use the Domain Name System (DNS) server to resolve Verkada’s fully qualified domain names (FQDN) to IP addresses to communicate with them. Your DHCP server tells the Verkada device where the DNS server is on the network, and the device communicates using UDP port 53. DNS over HTTPS (DoH) is not currently supported. [](https://help.verkada.com/government-solutions/required-network-settings/required-camera-network-settings-government-solutions#power) Power -------------------------------------------------------------------------------------------------------------------------------------------------- Most Verkada devices are powered through Power over Ethernet (PoE). You can use the product [datasheets](https://www.verkada.com/docs/?contentType=datasheet) to figure out the power requirements for your Verkada devices. These are the most common power requirements: * IEE 802.3af, Type 1 PoE * IEEE 802.3at, Type 2 PoE+ * IEEE 802.3bt, Type 3 PoE++ * * * [](https://help.verkada.com/government-solutions/required-network-settings/required-camera-network-settings-government-solutions#camera-firewall-settings) Camera firewall settings ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Verkada cameras require access to many endpoints to ensure they can communicate with Command and that all features are accessible. #### [](https://help.verkada.com/government-solutions/required-network-settings/required-camera-network-settings-government-solutions#region-united-states-gov) Region: United States Gov * api.global-prod.control.verkada.com (HTTPS/443) * update.control.verkada.com (HTTPS/443) * NTP: returned by DHCP client option 42, if not provided, falls back to time.nist.gov (UDP/123) * Local streaming: \*:4100 on LAN (HTTPS/443) * RTSP: \*:8554 on LAN * \*.kinesisvideo.us-gov-west-1.amazonaws.com (HTTPS/443) * s3.us-gov-west-1.amazonaws.com (HTTPS/443) * verkada-firmware.s3.us-west-2.amazonaws.com (HTTPS/443) * \*.prod-govus-pine.control.verkadagov.com (HTTPS/443) * api.control.verkada.com (HTTPS/443) * * * **Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=5pRUeH_bhw0) . Last updated 1 day ago Was this helpful? --- # Hardware Installation | Command Connector | Verkada Help [Prepare for a Command Connector Deployment](https://help.verkada.com/command-connector/hardware-installation/prepare-for-a-command-connector-deployment) Last updated 1 month ago Was this helpful? --- # Cellular Data Options | Connectivity | Verkada Help [Smart Data Usage](https://help.verkada.com/connectivity/cellular-data-options/smart-data-usage) [Bring Your Own Data Plan](https://help.verkada.com/connectivity/cellular-data-options/bring-your-own-data-plan) [Verkada Data Plan](https://help.verkada.com/connectivity/cellular-data-options/verkada-data-plan) Last updated 1 month ago Was this helpful? --- # Troubleshooting | Classic Alarms | Verkada Help [Troubleshoot Inrush Current Issues](https://help.verkada.com/classic-alarms/troubleshooting/troubleshoot-inrush-current-issues) Last updated 1 month ago Was this helpful? --- # Mailroom Network Settings | Mailroom | Verkada Help This article outlines the required network settings that your [Verkada Mailroom](https://docs.verkada.com/docs/mailroom-overview.pdf) tablets and phones need to be able to communicate with [Verkada Command](https://help.verkada.com/command/get-started-with-verkada-command) . For more information on the required network settings for other Verkada product lines see [Required Network Settings](https://help.verkada.com/command/required-network-settings) . Verkada devices are incompatible with LANs that require proxy servers or Secure Socket Layer (SSL)/Transport Layer Security (TLS) inspection. If either is in use, a bypass for all Verkada devices must be implemented for Verkada devices to communicate with Verkada Command. [](https://help.verkada.com/mailroom/mailroom-network-settings#ip-address) IP address ------------------------------------------------------------------------------------------ Mailroom tablets and phones must be assigned an IPv4 address to communicate on the LAN and to Verkada Command. Mailroom devices use Dynamic Host Configuration Protocol (DHCP) and User Datagram Protocol (UDP) to obtain their IP addresses and network configurations. If you require your Mailroom device to have a specific IP address, create a DHCP reservation using the device’s Media Access Control (MAC) address (found on the device’s label). [](https://help.verkada.com/mailroom/mailroom-network-settings#domain-name-system) Domain Name System ---------------------------------------------------------------------------------------------------------- Mailroom tablets and phones use the DNS server to resolve Verkada’s fully qualified domain names (FQDN) to IP addresses to communicate with them. Your DHCP server tells the Mailroom device where the DNS server is on the network and the Mailroom device communicates using UDP port 53. DNS over HTTPS (DoH) is currently not supported. [](https://help.verkada.com/mailroom/mailroom-network-settings#firewall-settings) Firewall settings -------------------------------------------------------------------------------------------------------- Mailroom tablets and phones require access to many endpoints to ensure they can communicate with Command and all features will be accessible. Many customers may want to allow the Mailroom devices to communicate with the general required endpoints. These are the general domains to allow, **applicable for all organization-regions**: Copy 3.1.77.0/24 - UDP/10000-20000 3.104.90.0/24 - UDP/10000-20000 3.112.80.0/24 - UDP/10000-20000 3.122.181.0/24 - UDP/10000-20000 18.228.249.0/24 - UDP/10000-20000 34.203.250.0/23 - UDP/10000-20000 34.216.15.26 - UDP/123 35.156.191.128/25 - UDP/10000-20000 52.215.127.0/24 - UDP/10000-20000 54.65.63.192/26 - UDP/10000-20000 54.169.127.128/26 - UDP/10000-20000 54.171.127.192/26 - UDP/10000-20000 54.172.60.0/23 - UDP/10000-20000 54.244.51.0/24 - UDP/1024-65535 54.252.254.64/26 - UDP/10000-20000 177.71.206.192/26 - UDP/10000-20000 *.verkada.com - UDP/123 + TCP+UDP/443 If you prefer a more granular allowlist, you can add both IP addresses and full FQDNs to your firewall rules based on the region where your devices are located. Your region is selected when you [create an organization](https://help.verkada.com/command/get-started-with-verkada-command) in Command. ### [](https://help.verkada.com/mailroom/mailroom-network-settings#region-united-states) Region: United States Copy 3.1.77.0/24 - UDP/10000-20000 3.104.90.0/24 - UDP/10000-20000 3.112.80.0/24 - UDP/10000-20000 3.122.181.0/24 - UDP/10000-20000 18.228.249.0/24 - UDP/10000-20000 34.203.250.0/23 - UDP/10000-20000 34.216.15.26 - UDP/123 35.156.191.128/25 - UDP/10000-20000 52.215.127.0/24 - UDP/10000-20000 54.65.63.192/26 - UDP/10000-20000 54.169.127.128/26 - UDP/10000-20000 54.171.127.192/26 - UDP/10000-20000 54.172.60.0/23 - UDP/10000-20000 54.244.51.0/24 - UDP/1024-65535 54.252.254.64/26 - UDP/10000-20000 177.71.206.192/26 - UDP/10000-20000 api.control.verkada.com - TCP+UDP/443 api.global-prod.control.verkada.com - TCP+UDP/443 device.pyramid.verkada.com - TCP+UDP/443 firmware.control.verkada.com - TCP+UDP/443 index.control.verkada.com - TCP+UDP/443 relay.control.verkada.com - TCP+UDP/443 relay.global-prod.control.verkada.com - TCP+UDP/443 time.control.verkada.com - UDP/123 update.control.verkada.com - TCP+UDP/443 user.pyramid.verkada.com - TCP+UDP/443 vconductor.global-prod.command.verkada.com - TCP+UDP/443 vdoorman.command.verkada.com - TCP+UDP/443 vdoorman.prod1.command.verkada.com - TCP+UDP/443 ### [](https://help.verkada.com/mailroom/mailroom-network-settings#region-europe) Region: Europe Copy 3.1.77.0/24 - UDP/10000-20000 3.104.90.0/24 - UDP/10000-20000 3.112.80.0/24 - UDP/10000-20000 3.122.181.0/24 - UDP/10000-20000 18.228.249.0/24 - UDP/10000-20000 34.203.250.0/23 - UDP/10000-20000 34.216.15.26 - UDP/123 35.156.191.128/25 - UDP/10000-20000 52.215.127.0/24 - UDP/10000-20000 54.65.63.192/26 - UDP/10000-20000 54.169.127.128/26 - UDP/10000-20000 54.171.127.192/26 - UDP/10000-20000 54.172.60.0/23 - UDP/10000-20000 54.244.51.0/24 - UDP/1024-65535 54.252.254.64/26 - UDP/10000-20000 177.71.206.192/26 - UDP/10000-20000 api.global-prod.control.verkada.com - TCP+UDP/443 api.prod2.control.verkada.com - TCP+UDP/443 index.prod2.control.verkada.com - TCP+UDP/443 relay.global-prod.control.verkada.com - TCP+UDP/443 relay.prod2.control.verkada.com - TCP+UDP/443 time.control.verkada.com - UDP/123 update.control.verkada.com - TCP+UDP/443 vconductor.global-prod.command.verkada.com - TCP+UDP/443 vconductor.prod2.command.verkada.com - TCP+UDP/443 vdoorman.prod2.command.verkada.com - TCP+UDP/443 Last updated 22 hours ago Was this helpful? --- # Smart Tiles | Viewing Station | Verkada Help Smart Tiles allows you to display key information from access events, sensor data, and notable camera activity. You must be an **Org Admin** to claim and manage a Viewing Station. * * * [](https://help.verkada.com/viewing-station/smart-tiles#configuration) Configuration ----------------------------------------------------------------------------------------- 1 **In Verkada Command, go to All Products > Devices.** 2 **Select your viewing station, then click the arrow on the right to open its page.** 3 **At the top right, click Manage Tiles > Smart Tiles.** 4 **Choose the type of Smart Tile to add.** * [Active Area](https://help.verkada.com/viewing-station/smart-tiles#h_269a6209f8) * [Access Control](https://help.verkada.com/viewing-station/smart-tiles#h_1e8080a3ec) * [Sensor Readings](https://help.verkada.com/viewing-station/smart-tiles#h_df6f11f1ca) * [Live Face Blur](https://help.verkada.com/viewing-station/smart-tiles#h_c692516d8c) * * * ### [](https://help.verkada.com/viewing-station/smart-tiles#active-area) Active Area Displays the camera with the most motion. To change which camera(s) display on the active area tile, select the tile to see the information panel where you can select from the following options: * **Current Page -** Includes all cameras on the current page. * **All Pages -** Includes all cameras on all pages. * **Select Cameras -** Choose which cameras you want to display. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1530499399-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FfFkKNdIGPl0XHde4cZf7%252Fuploads%252Fgit-blob-6bf65156c31b8abb454223478b8592910b088c34%252F97542e96f9ed47be968c501f4f2afd861575de00.gif%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=1cf00117&sv=2) ### [](https://help.verkada.com/viewing-station/smart-tiles#access-control) Access Control Displays the most recent door events, including all events visible in **Door History**, such as: * Access granted * Access denied * Door opened * Door held open (DHO) * Door forced open (DFO) When you select this tile, you can choose which door is displayed. ### [](https://help.verkada.com/viewing-station/smart-tiles#sensor-readings) Sensor Readings Displays air quality readings from a selected sensor. From the **Customize Data** tab, choose which sensor reading to display in the tile. See [Air Quality Sensor Readings](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) for more information. ### [](https://help.verkada.com/viewing-station/smart-tiles#live-face-blur) Live Face Blur Displays a live camera feed with faces automatically blurred in real time to protect individual privacy. When you select this tile, choose which camera feed to display with Live Face Blur enabled. * The selected camera must support Live Face Blur. See [Enable Face Blur on Verkada Cameras](https://help.verkada.com/verkada-cameras/configuration-and-setup/enable-face-blur-on-verkada-cameras) for a list of supported cameras. * The Viewing Station must be running the latest software version and tvOS. You can find the software version and serial number under **Settings > Device**. Last updated 1 day ago Was this helpful? --- # Create Guardian Forms for Reunification | Incident Response | Verkada Help Verkada Incident Response helps schools manage every step of a Reunification event. Guardian forms allow schools to collect required information from guardians before releasing students. * * * [](https://help.verkada.com/incident-response/create-guardian-forms-for-reunification#create-guardian-forms) Create guardian forms --------------------------------------------------------------------------------------------------------------------------------------- Admins can create site-specific guardian forms or global forms that can be used across multiple sites. ### [](https://help.verkada.com/incident-response/create-guardian-forms-for-reunification#global) Global You need at least **Org Admin** permissions to create global guardian forms. 1 **In Verkada Command, go to All Products > Workplace Incident Response.** 2 **On the left navigation, click Incident Response Settings.** 3 **Under Guardian Sign-In, select Manage Guardian Forms.** a. In the top right, select **Add Guardian Form**. b. Enter a unique name. c. Click **Save.** ### [](https://help.verkada.com/incident-response/create-guardian-forms-for-reunification#site-specific) Site-specific You need at least **Workplace Site Admin** permissions to create site-specific guardian forms. 1 **In Verkada Command, go to All Products > Workplace Incident Response.** 2 **On the left navigation, click Incident Response Settings > your site.** 3 **Under Guardian Sign-In, select Manage Guardian Forms.** a. In the top right, select **Add Guardian Form**. b. Enter a unique name. c. Click **Save.** * * * [](https://help.verkada.com/incident-response/create-guardian-forms-for-reunification#configuration) Configuration ----------------------------------------------------------------------------------------------------------------------- All guardian forms must collect the guardian’s name and the names of the students they are requesting. Organizations can also include the following optional steps: * Contact Info (email and/or phone number) * [Security Screening](https://help.verkada.com/guest/configuration-and-setup/guest-security-screening) * Guardian Photo * Open Response Questions * Multiple Choice Questions * Questionnaires * Videos * PDFs * Documents The security screening step requires capturing an image of the guardian’s ID at check-in. The feature extracts the legal name and date of birth from the ID for verification. * * * [](https://help.verkada.com/incident-response/create-guardian-forms-for-reunification#add-a-guardian-form-to-a-response-template) Add a guardian form to a Response template --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- A guardian form must be assigned for Response templates enabled for Reunification. You can select the desired form when configuring the Response template. See [Create a Response Template](https://help.verkada.com/incident-response/create-response-templates) for more information. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3922624211-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252Fn49pz7ZddUdVxNdz2EFE%252Fuploads%252Fgit-blob-2e0f410520a8d71df6264f938ec39670fb823fec%252F5fb614c160fe81792a9622d16160c9152a68a982.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=c2ef6906&sv=2) Last updated 18 hours ago Was this helpful? --- # Compliance, Licensing, Trials | Classic Alarms | Verkada Help [Determine Relevant Alarm Permits](https://help.verkada.com/classic-alarms/compliance-licensing-trials/determine-relevant-alarm-permits) [Classic Alarms Licensing](https://help.verkada.com/classic-alarms/compliance-licensing-trials/classic-alarms-licensing) [Start Your Free 30-Day Alarm Trial](https://help.verkada.com/classic-alarms/compliance-licensing-trials/start-your-free-30-day-alarm-trial) [Security Controls for Verkada Alarms](https://help.verkada.com/classic-alarms/compliance-licensing-trials/security-controls-for-verkada-alarms) Last updated 1 month ago Was this helpful? --- # Viewing Station Network Settings | Viewing Station | Verkada Help This article outlines the required network settings that your Verkada [viewing stations](https://docs.verkada.com/docs/viewing-station-overview.pdf) need to communicate with [Verkada Command](https://help.verkada.com/command/get-started-with-verkada-command) . For more information on the required network settings for other Verkada product lines see [Required Network Settings](https://help.verkada.com/command/required-network-settings) . Verkada devices are incompatible with LANs that require proxy servers or Secure Socket Layer (SSL)/Transport Layer Security (TLS) inspection. If either is in use, a bypass for all Verkada devices must be implemented for Verkada devices to communicate with Verkada Command. [](https://help.verkada.com/viewing-station/viewing-station-network-settings#ip-address) IP address -------------------------------------------------------------------------------------------------------- Viewing stations must be assigned an IPv4 address to communicate on the LAN and to Verkada Command. Viewing stations support both wired and wireless internet connections. They use Dynamic Host Configuration Protocol (DHCP) and User Datagram Protocol (UDP) to obtain their IP addresses and network configurations. If you require your viewing station to have a specific IP address, create a DHCP reservation using the device’s Media Access Control (MAC) address (found on the device’s label). [](https://help.verkada.com/viewing-station/viewing-station-network-settings#domain-name-system) Domain Name System ------------------------------------------------------------------------------------------------------------------------ Viewing stations use the DNS server to resolve Verkada’s fully qualified domain names (FQDN) to IP addresses to communicate with them. Your DHCP server tells the intercom where the DNS server is on the network and the intercom communicates using UDP port 53. DNS over HTTPS (DoH) is currently not supported. [](https://help.verkada.com/viewing-station/viewing-station-network-settings#firewall-settings) Firewall settings ---------------------------------------------------------------------------------------------------------------------- Viewing stations require access to many endpoints to ensure they can communicate with Command and all features will be accessible. Many customers may want to allow the viewing stations to communicate with the general required endpoints. These are the general domains to allow, **applicable for all organization-regions**: Copy 34.216.15.26 - UDP/123 *:4100 - TCP/UDP on local network *.verkada.com - UDP/123 + TCP+UDP/443 *.vcamera.net - TCP+UDP/443 apple.com - TCP/80 apple.com - TCP/443 *.apple.com - TCP/80 *.apple.com - TCP/443 *.apple.com - TCP/2197 *.apple.com - TCP/5223 *.apple.com - UDP/123 *.cdn-apple.com 443 *.aaplimg.com - TCP/80/443+UDP/123 app-measurement.com - TCP+UDP/443 browser-intake-datadoghq.com - TCP+UDP/443 firebaselogging-pa.googleapis.com - TCP+UDP/443 crl.entrust.net - TCP/80 crl3.digicert.com - TCP/80 crl4.digicert.com - TCP/80 *.mzstatic.com - TCP/443 ocsp.digicert.com - TCP/80 ocsp.entrust.net - TCP/80 If you prefer a more granular allowlist, you can add IP addresses, full FQDNs, and wildcard domains to your firewall rules based on the region where your devices are located. Your region is selected when you [create an organization](https://help.verkada.com/command/get-started-with-verkada-command) in Command. ### [](https://help.verkada.com/viewing-station/viewing-station-network-settings#region-united-states) Region: United States Copy 34.216.15.26 - UDP/123 *:4100 - TCP/UDP on local network api.control.verkada.com - TCP+UDP/443 api.global-prod.control.verkada.com - TCP+UDP/443 firmware.control.verkada.com - TCP+UDP/443 index.control.verkada.com - TCP+UDP/443 relay.control.verkada.com - TCP+UDP/443 relay.global-prod.control.verkada.com - TCP+UDP/443 time.control.verkada.com - UDP/123 update.control.verkada.com - TCP+UDP/443 vconductor.command.verkada.com - TCP+UDP/443 vconductor.global-prod.command.verkada.com - TCP+UDP/443 vecho.command.verkada.com - TCP+UDP/443 vfilter.verkada.com - TCP+UDP/443 vlocaldns.command.verkada.com - TCP+UDP/443 vmdm.command.verkada.com - TCP+UDP/443 vmdm.global-prod.verkada.com - TCP+UDP/443 vprovision.command.verkada.com - TCP+UDP/443 vsensor.command.verkada.com - TCP+UDP/443 vstream.command.verkada.com - TCP+UDP/443 vsubmit.command.verkada.com - TCP+UDP/443 vvx.command.verkada.com - TCP+UDP/443 apple.com - TCP/80 apple.com - TCP/443 *.apple.com - TCP/80 *.apple.com - TCP/443 *.apple.com - TCP/2197 *.apple.com - TCP/5223 *.apple.com - UDP/123 *.cdn-apple.com 443 *.aaplimg.com - TCP/80/443+UDP/123 app-measurement.com - TCP+UDP/443 browser-intake-datadoghq.com - TCP+UDP/443 firebaselogging-pa.googleapis.com - TCP+UDP/443 crl.entrust.net - TCP/80 crl3.digicert.com - TCP/80 crl4.digicert.com - TCP/80 *.mzstatic.com - TCP/443 ocsp.digicert.com - TCP/80 ocsp.entrust.net - TCP/80 ### [](https://help.verkada.com/viewing-station/viewing-station-network-settings#region-europe) Region: Europe Copy 34.216.15.26 - UDP/123 *:4100 - TCP/UDP on local network api.global-prod.control.verkada.com - TCP+UDP/443 api.prod2.control.verkada.com - TCP+UDP/443 firmware.control.verkada.com - TCP+UDP/443 index.prod2.control.verkada.com - TCP+UDP/443 relay.global-prod.control.verkada.com - TCP+UDP/443 relay.prod2.control.verkada.com - TCP+UDP/443 time.control.verkada.com - UDP/123 update.control.verkada.com - TCP+UDP/443 vconductor.global-prod.command.verkada.com - TCP+UDP/443 vconductor.prod2.command.verkada.com - TCP+UDP/443 vfilter.prod2.verkada.com - TCP+UDP/443 vecho.prod2.verkada.com - TCP+UDP/443 vlocaldns.prod2.verkada.com - TCP+UDP/443 vmdm.command.verkada.com - TCP+UDP/443 vmdm.global-prod.verkada.com - TCP+UDP/443 vprovision.prod2.verkada.com - TCP+UDP/443 vsensor.prod2.verkada.com - TCP+UDP/443 vstream.prod2.verkada.com - TCP+UDP/443 vsubmit.prod2.verkada.com - TCP+UDP/443 vvx.prod2.verkada.com - TCP+UDP/443 apple.com - TCP/80 apple.com - TCP/443 *.apple.com - TCP/80 *.apple.com - TCP/443 *.apple.com - TCP/2197 *.apple.com - TCP/5223 *.apple.com - UDP/123 *.cdn-apple.com 443 *.aaplimg.com - TCP/80/443+UDP/123 app-measurement.com - TCP+UDP/443 browser-intake-datadoghq.com - TCP+UDP/443 firebaselogging-pa.googleapis.com - TCP+UDP/443 crl.entrust.net - TCP/80 crl3.digicert.com - TCP/80 crl4.digicert.com - TCP/80 *.mzstatic.com - TCP/443 ocsp.digicert.com - TCP/80 ocsp.entrust.net - TCP/80 ### [](https://help.verkada.com/viewing-station/viewing-station-network-settings#region-australia) Region: Australia Copy 34.216.15.26 - UDP/123 *:4100 - TCP/UDP on local network api.global-prod.control.verkada.com - TCP+UDP/443 api.prod-ap-syd.control.verkada.com - TCP+UDP/443 firmware.control.verkada.com - TCP+UDP/443 index.prod-ap-syd.control.verkada.com - TCP+UDP/443 relay.global-prod.control.verkada.com - TCP+UDP/443 relay.prod-ap-syd.control.verkada.com - TCP+UDP/443 time.control.verkada.com - UDP/123 update.control.verkada.com - TCP+UDP/443 vconductor.global-prod.command.verkada.com - TCP+UDP/443 vconductor.prod-ap-syd.command.verkada.com - TCP+UDP/443 vfilter.prod-ap-syd.verkada.com - TCP+UDP/443 vecho.prod-ap-syd.verkada.com - TCP+UDP/443 vlocaldns.prod-ap-syd.verkada.com - TCP+UDP/443 vmdm.command.verkada.com - TCP+UDP/443 vmdm.global-prod.verkada.com - TCP+UDP/443 vprovision.prod-ap-syd.verkada.com - TCP+UDP/443 vsensor.prod-ap-syd.verkada.com - TCP+UDP/443 vstream.prod-ap-syd.verkada.com - TCP+UDP/443 vsubmit.prod-ap-syd.verkada.com - TCP+UDP/443 vvx.prod-ap-syd.verkada.com - TCP+UDP/443 apple.com - TCP/80 apple.com - TCP/443 *.apple.com - TCP/80 *.apple.com - TCP/443 *.apple.com - TCP/2197 *.apple.com - TCP/5223 *.apple.com - UDP/123 *.cdn-apple.com 443 *.aaplimg.com - TCP/80/443+UDP/123 app-measurement.com - TCP+UDP/443 browser-intake-datadoghq.com - TCP+UDP/443 firebaselogging-pa.googleapis.com - TCP+UDP/443 crl.entrust.net - TCP/80 crl3.digicert.com - TCP/80 crl4.digicert.com - TCP/80 *.mzstatic.com - TCP/443 ocsp.digicert.com - TCP/80 ocsp.entrust.net - TCP/80 Use the [Verkada Network Tester](https://network-tester.support.verkada.com/) to verify your devices can connect to Verkada Command. Select your region and the **Viewing Station** product type to run the check. The following endpoints must be allowed on your network for the test to work: * speed.cloudflare.com * network-tester.support.verkada.com Last updated 22 hours ago Was this helpful? --- # Incident Response Portal | Incident Response | Verkada Help The Incident Response portal is a web page where employees can account for evacuees during an active Response. Any Workplace employee can access the Incident Response portal to interact with active responses at their site. * * * [](https://help.verkada.com/incident-response/incident-response-portal#incident-response-portal) Incident Response portal ------------------------------------------------------------------------------------------------------------------------------ When a Response is launched in **Incident** or **Drill mode** with employee notifications enabled, all Workplace employees at the site receive a magic link via email and/or SMS to access the Incident Response portal. Employees can also log in at any time at [unite.my.verkada.com](https://unite.my.verkada.com/) . * * * [](https://help.verkada.com/incident-response/incident-response-portal#people-status-page) People Status page ------------------------------------------------------------------------------------------------------------------ You can search evacuees by name and view or update their status and location. To update an evacuee’s status or location: 1 **Log in to** [**unite.my.verkada.com**](https://unite.my.verkada.com/) **.** 2 **(Optional) Apply** [**filters**](https://help.verkada.com/incident-response/incident-response-portal#h_457b70e469) **.** 3 **Select an evacuee.** a. Select a **Status**. b. Select a **Location**. c. Click **Save**. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3922624211-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252Fn49pz7ZddUdVxNdz2EFE%252Fuploads%252Fgit-blob-8efa1e1c34ef32faedc58f921e0c38fabd392ad5%252Fe7ed808760100e642989622ddd0b011ee89b8c4c.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=75803cf3&sv=2) ### [](https://help.verkada.com/incident-response/incident-response-portal#filters) Filters Workplace Employees can use the search bar and filters on the People Status page to find specific evacuees. Filters include: 1 **Evacuee status** 2 **Evacuee location** 3 **Teacher & Section (for K12 customers with an SIS integration)** 4 **Edited by me** * * * [](https://help.verkada.com/incident-response/incident-response-portal#sign-in-guardians-page) Sign in Guardians page -------------------------------------------------------------------------------------------------------------------------- Employees will see the **Sign in Guardians** page for Response Templates with [Reunification enabled](https://help.verkada.com/incident-response/create-response-templates) . From here, employees can sign in and review guardians: 1 **Log in to** [**unite.my.verkada.com**](https://unite.my.verkada.com/) **.** 2 **Select the Sign in Guardians page.** 3 **Select your location.** 4 **At the bottom, select Sign in a guardian.** 5 **Fill out the** [**form**](https://app.intercom.com/a/apps/q5re5q6g/knowledge-hub/all-content?activeContentId=13666171&activeContentType=article&editorMode=view&search=guardian%20form) **on behalf of the guardian.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3922624211-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252Fn49pz7ZddUdVxNdz2EFE%252Fuploads%252Fgit-blob-23eef526c5eceba76c17719709dd72c22943aaf5%252F87cf0fc6596ffd6affb0ebe0c910b2c0eecd386f.jpg%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=2a62ee05&sv=2) By default, the **Sign in Guardians** page shows all waiting guardians. Employees can filter to view: * All guardians checked in during the Response * Denied guardians * Reunified guardians By selecting a guardian, employees can view the student(s) they requested to release and the employee who checked them in. * * * [](https://help.verkada.com/incident-response/incident-response-portal#reunify-students-and-guardians) Reunify Students and Guardians ------------------------------------------------------------------------------------------------------------------------------------------ Employees will see the **Reunify Students + Guardians** page for Response Templates with [Reunification enabled](https://help.verkada.com/incident-response/create-response-templates) . By default, this page displays all student/guardian pairings where: 1 **The student’s status is not unknown and not reunified.** 2 **The guardian is signed in and fully approved (e.g., passed security screening or temporary guardian exception)** Employees can use location and status filters to refine which pairings appear. Filters only affect the individual’s view and do not impact what other employees see. The location filter applies to both guardians and students. Last updated 18 hours ago Was this helpful? --- # Events and Alerts | Connectivity | Verkada Help [Gateway Monthly Data Usage Alerts](https://help.verkada.com/connectivity/events-and-alerts/gateway-monthly-data-usage-alerts) [SIM Failover Alerts](https://help.verkada.com/connectivity/events-and-alerts/sim-failover-alerts) [Gateway Tamper Alerts](https://help.verkada.com/connectivity/events-and-alerts/gateway-tamper-alerts) [Configure Gateway Status Alerts](https://help.verkada.com/connectivity/events-and-alerts/configure-gateway-status-alerts) Last updated 1 month ago Was this helpful? --- # Events and Alerts | Mailroom | Verkada Help [Enable Mailroom Notifications](https://help.verkada.com/mailroom/events-and-alerts/enable-mailroom-notifications) Last updated 1 month ago Was this helpful? --- # Get started with Command Connector | Command Connector | Verkada Help The Command Connector enables organizations to integrate non-Verkada video feeds into Verkada’s Command platform for centralized video security management. It offers a cost-effective migration for non-Verkada cameras. You need Organization Admin and/or Site Admin [permissions](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) for your Verkada Command organization to complete these actions. ### [](https://help.verkada.com/command-connector/get-started-with-command-connector#what-you-need) What you need * A standard AC electrical outlet * DHCP-enabled network * Cat5 or Cat6 cabling [](https://help.verkada.com/command-connector/get-started-with-command-connector#create-a-site) Create a site ------------------------------------------------------------------------------------------------------------------ Sites are the logical way of grouping and managing devices within your Command organization. Site-level permissions make managing and viewing your devices easier. See [Manage Your Sites and Subsites](https://help.verkada.com/verkada-cameras/configuration-and-setup/manage-sites-and-subsites) for more information on site creation and management. [](https://help.verkada.com/command-connector/get-started-with-command-connector#add-a-command-connector) Add a Command Connector -------------------------------------------------------------------------------------------------------------------------------------- Command Connectors can be added from the **Devices** page or directly from a site. See [Add a Device to Your Command Account](https://help.verkada.com/verkada-cameras/configuration-and-setup/add-a-device-to-your-command-organization) for more information. #### [](https://help.verkada.com/command-connector/get-started-with-command-connector#connect-a-non-verkada-camera) Connect a non-Verkada camera You can connect multiple non-Verkada cameras to Command using a Command Connector. All non-Verkada cameras must be on the same LAN and support ONVIF (Profile S). See [Add a Non-Verkada Camera to a Command Connector](https://help.verkada.com/command-connector/configuration-and-setup/add-a-non-verkada-camera-to-a-command-connector) for more information. [](https://help.verkada.com/command-connector/get-started-with-command-connector#licensing) Licensing ---------------------------------------------------------------------------------------------------------- Every non-Verkada camera that is connected to the Command Connector will require a valid camera license. The Command Connector itself does not require a license. Verkada licensing is applied for each Command organization, and the licenses co-term to a single expiration date. Your licenses may have been automatically added if you claimed your devices via order number. Otherwise, manually add the license key from the Admin page. See [Manage Your Licenses](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses) for more information on adding and managing licenses. [](https://help.verkada.com/command-connector/get-started-with-command-connector#connect-your-command-connector) Connect your Command Connector ---------------------------------------------------------------------------------------------------------------------------------------------------- While Command Connectors are considered low-voltage devices that do not require a certified electrician to install, we strongly recommend you work with a system integrator or other professional for installation. Please refer to the Command Connector [setup guide](https://docs.verkada.com/docs/Verkada-CC300-500-700-Command-Connector-Install-Guide.pdf) for instructions on mounting the device. The device can be mounted on a standard 19-inch server rack and takes up 1 rack unit or 1U. #### [](https://help.verkada.com/command-connector/get-started-with-command-connector#power-and-network) Power and network Command Connectors are powered via AC power and connect to your network via Ethernet. The Command Connector has 2 RJ-45 Ethernet interfaces. Only **connect one** of the interfaces to your network for initial configuration. To configure both ports, see [Configure Two Ethernet Ports for Command Connector](https://help.verkada.com/command-connector/configuration-and-setup/configure-two-ethernet-ports-for-command-connector) . [](https://help.verkada.com/command-connector/get-started-with-command-connector#check-network-settings) Check Network Settings ------------------------------------------------------------------------------------------------------------------------------------ The Command Connector is designed to be plug-and-play. However, if your environment includes a firewall with custom rules and policies, you may need to make some configuration changes to get your connected cameras to stream on Command. See [Command Connector Network Settings](https://help.verkada.com/command-connector/command-connector-network-settings) for more information. Last updated 1 day ago Was this helpful? --- # Create Response Templates | Incident Response | Verkada Help Workplace Site Admins can create Response Templates for different types of incidents. A Response Template defines: * Who needs to be accounted for as evacuees * What statuses can be assigned to evacuees * Where evacuees can be marked as present For schools, configure the Response Template for [Reunification](https://help.verkada.com/incident-response/create-response-templates#h_4e94526bd9) and set up a Guardian Form. * * * [](https://help.verkada.com/incident-response/create-response-templates#create-a-response-template) Create a Response Template ----------------------------------------------------------------------------------------------------------------------------------- 1 **In Verkada Command, go to All Products > Workplace Incident Response.** 2 **On the left navigation, click Response Templates.** 3 **At the top, select your site.** 4 **Select Add Template and configure the template settings:** a. [General](https://help.verkada.com/incident-response/create-response-templates#h_6b3cdc0e04) b. [People](https://help.verkada.com/incident-response/create-response-templates#h_f2978457f3) c. [Reunification](https://help.verkada.com/incident-response/create-response-templates#h_4e94526bd9) d. [People Statuses](https://help.verkada.com/incident-response/create-response-templates#h_57bacd963e) e. [Location Names](https://help.verkada.com/incident-response/create-response-templates#h_86abe03c6c) Response Templates are site-specific and apply to a single site. ### [](https://help.verkada.com/incident-response/create-response-templates#general) General 1 **Enter a unique Template Name.** 2 **Choose Template Color.** 3 **Choose Template Icon.** 4 **Enter a Template Description.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3922624211-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252Fn49pz7ZddUdVxNdz2EFE%252Fuploads%252Fgit-blob-bee8dab09c23c3dadb35624470783d209e8a29cb%252F57bec27fc52fb1e2c06b5c79c0756a66e2c2de38.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=41b167a0&sv=2) ### [](https://help.verkada.com/incident-response/create-response-templates#people) People This setting defines who will be tracked as evacuees when a Response Template is launched. You can choose from three groups: * **Students** – All students in the school linked to the Workplace site. * [**Staff**](https://help.verkada.com/guest/configuration-and-setup/manage-host-lists-in-guest) – All Workplace employees assigned to the site. * **Visitors (from Guest)** – All visitors signed in on the day the Response is launched. ### [](https://help.verkada.com/incident-response/create-response-templates#reunification) Reunification For K12 customers, enabling Reunification lets employees check in guardians and mark students as reunified. This adds a Reunified status for evacuees. Admins can also customize a Guardian Form to collect guardian information at check-in. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3922624211-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252Fn49pz7ZddUdVxNdz2EFE%252Fuploads%252Fgit-blob-2f69fcb500692de5c49da48c72258c5f6dcbd32d%252Fba6bbf045344b9a7311db27d223cf3d8da758064.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=38f11fcf&sv=2) ### [](https://help.verkada.com/incident-response/create-response-templates#person-statuses) Person Statuses Admins can define which statuses can be assigned to evacuees. If Reunification is enabled, a Reunified status will always be available. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3922624211-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252Fn49pz7ZddUdVxNdz2EFE%252Fuploads%252Fgit-blob-4e42d24522bc654ebea118704c0a66fbc2b2e235%252F2a990dd19725b6b5f0462426509dffcaa1581d8a.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=bfe5b360&sv=2) ### [](https://help.verkada.com/incident-response/create-response-templates#location-names) Location Names Admins can define where evacuees and guardians (if Reunification is enabled) are expected to assemble. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3922624211-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252Fn49pz7ZddUdVxNdz2EFE%252Fuploads%252Fgit-blob-0cf1da1a1554d8772de2a01930aee8ec8786688c%252F7a65b5d40bb7b7db4a0c748e03ace7004c58dd73.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=ec8eea84&sv=2) Last updated 18 hours ago Was this helpful? --- # Networking and Reports | Classic Alarms | Verkada Help [Verkada Monitoring Phone Numbers for Classic Alarms](https://help.verkada.com/classic-alarms/networking-and-reports/verkada-monitoring-phone-numbers-for-classic-alarms) [High-Volume Events](https://help.verkada.com/classic-alarms/networking-and-reports/high-volume-events) [Classic Alarms Devices Bandwidth Usage](https://help.verkada.com/classic-alarms/networking-and-reports/classic-alarms-devices-bandwidth-usage) [Alarms Reports](https://help.verkada.com/classic-alarms/networking-and-reports/alarms-reports) Last updated 1 month ago Was this helpful? --- # Troubleshooting | Command Connector | Verkada Help [Troubleshooting a Command Connector](https://help.verkada.com/command-connector/troubleshooting/troubleshooting-a-command-connector) Last updated 1 month ago Was this helpful? --- # Events and Alerts | Classic Alarms | Verkada Help [Configure Alarms Event Alerts](https://help.verkada.com/classic-alarms/events-and-alerts/configure-alarms-event-alerts) [Alarm Override Schedule](https://help.verkada.com/classic-alarms/events-and-alerts/alarm-override-schedule) [Configure Camera Alarm Trigger Events](https://help.verkada.com/classic-alarms/events-and-alerts/configure-camera-alarm-trigger-events) Last updated 1 month ago Was this helpful? --- # Prepare for a Command Connector Deployment | Command Connector | Verkada Help [](https://help.verkada.com/command-connector/hardware-installation/prepare-for-a-command-connector-deployment#prerequisites-and-planning) Prerequisites and planning -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- * **Are the cameras IP-based?** * Analog cameras require an encoder to function (not recommended). * **Are cameras on the** [Hardware Compatibility List](https://www.verkada.com/security-cameras/command-connector/hcl) ? * If not, verify they support ONVIF Profile S or RTSP. * Use the [ONVIF Conformant Products](https://www.onvif.org/conformant-products/) tool to verify compatibility. * **Do you have complete camera specifications?** * Camera type and model * Megapixel resolution * Encoding format * Number of video feeds * IP address and login credentials * **Where are the cameras connected?** * Ideally, they should connect to the same network switch as the Command Connector. * * * [](https://help.verkada.com/command-connector/hardware-installation/prepare-for-a-command-connector-deployment#device-requirements) Device requirements ------------------------------------------------------------------------------------------------------------------------------------------------------------ ### [](https://help.verkada.com/command-connector/hardware-installation/prepare-for-a-command-connector-deployment#camera-capabilities) Camera capabilities * **Encoding format**: Only H.264 streams are supported. * **Resolution**: * **≤ 5MP**: Recommended for optimal performance. * **8MP** = Supported, but reduces the number of cameras that can be connected per Command Connector. * **\> 8MP** = May not be supported. Contact your Verkada Solutions Engineer for more information. * **Multisensor cameras**: Require one license per video stream. * **Login access**: Each camera must have a known IP address and admin credentials. ### [](https://help.verkada.com/command-connector/hardware-installation/prepare-for-a-command-connector-deployment#network-setup) Network setup * Cameras must be on the same LAN as the Command Connector. * Avoid configurations where cameras are only accessible through an NVR’s internal switch. * IT resources: * [Network Requirements](https://help.verkada.com/command-connector/command-connector-network-settings) * [Local Streaming](https://help.verkada.com/verkada-cameras/live-streaming/local-streaming-on-verkada-cameras) * * * [](https://help.verkada.com/command-connector/hardware-installation/prepare-for-a-command-connector-deployment#sizing-and-licensing) Sizing and licensing -------------------------------------------------------------------------------------------------------------------------------------------------------------- Collaborate with your Verkada Partner or Sales Rep to determine: * The number of Command Connectors required. * Whether camera retention settings align with expected video usage and storage needs. One **LIC-CAM** license is required per video stream. * * * [](https://help.verkada.com/command-connector/hardware-installation/prepare-for-a-command-connector-deployment#physical-installation) Physical installation ---------------------------------------------------------------------------------------------------------------------------------------------------------------- Each Command Connector is a 1RU rack-mount server and requires: * AC power * One network connection to the site switch * (Optional) Alternative mounting solutions are available from third-party suppliers. Reference: [Command Connector Install Guide (PDF)](https://docs.verkada.com/docs/Verkada-CC300-500-700-Command-Connector-Install-Guide.pdf) . Last updated 1 day ago Was this helpful? --- # Configuration and Setup | Mailroom | Verkada Help [Supported Mailroom Carriers](https://help.verkada.com/mailroom/configuration-and-setup/supported-mailroom-carriers) [View and Edit Mailroom Settings](https://help.verkada.com/mailroom/configuration-and-setup/view-and-edit-mailroom-settings) [Mailroom Sites](https://help.verkada.com/mailroom/configuration-and-setup/mailroom-sites) [Customize Your Mailroom Dashboard](https://help.verkada.com/mailroom/configuration-and-setup/customize-your-mailroom-dashboard) Last updated 1 month ago Was this helpful? --- # Get Started with Verkada Mailroom | Mailroom | Verkada Help [Verkada Mailroom](https://docs.verkada.com/docs/mailroom-overview.pdf) enables your organization to quickly and securely manage packages that are delivered. Mailroom can also leverage camera feeds to allow you to see when a package was delivered, scanned, or picked up. [](https://help.verkada.com/mailroom/get-started-with-verkada-mailroom#create-a-site) Create a site -------------------------------------------------------------------------------------------------------- Sites are the logical way of grouping and managing devices within your Command organization. Site-level permissions make managing and viewing your devices easier. See [Mailroom Sites](https://help.verkada.com/mailroom/configuration-and-setup/mailroom-sites) for more information on site creation and management. ### [](https://help.verkada.com/mailroom/get-started-with-verkada-mailroom#configure-settings) Configure settings You can edit Mailroom settings at the organization level or site level. You can add pickup locations, add context cameras, manage multiple languages, etc, to make your Mailroom pickup experience easier. See [Mailroom Settings](https://help.verkada.com/mailroom/configuration-and-setup/view-and-edit-mailroom-settings) for more information. ### [](https://help.verkada.com/mailroom/get-started-with-verkada-mailroom#download-the-mailroom-app) Download the Mailroom app Verkada Mailroom allows you to use your existing phone or tablet without the need to purchase any additional devices. Download the Mailroom app from the [App Store](https://apps.apple.com/us/app/verkada-mailroom/id1631622141) or the [Google Play](https://play.google.com/store/apps/details?id=com.verkada.mailroom&hl=en&gl=US&pli=1) store. [](https://help.verkada.com/mailroom/get-started-with-verkada-mailroom#supported-mailroom-carriers) Supported Mailroom carriers ------------------------------------------------------------------------------------------------------------------------------------ Verkada Mailroom supports a variety of mail carriers to streamline your experience. See [Supported Mailroom Carriers](https://help.verkada.com/mailroom/configuration-and-setup/supported-mailroom-carriers) for more information. [](https://help.verkada.com/mailroom/get-started-with-verkada-mailroom#licensing) Licensing ------------------------------------------------------------------------------------------------ Every Mailroom site you manage in Command will need a license. Verkada licensing is applied for each Command organization, and the licenses co-term to a single expiration date. For more information on adding and managing licenses, see [Manage Your Licenses](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses) . [](https://help.verkada.com/mailroom/get-started-with-verkada-mailroom#check-network-settings) Check network settings -------------------------------------------------------------------------------------------------------------------------- Verkada Mailroom is designed to be plug-and-play. However, if your environment includes a firewall, you may need to make some configuration changes to get your Mailroom devices online. For more information on Mailroom network settings, see [Mailroom Network Settings](https://help.verkada.com/mailroom/mailroom-network-settings) . Last updated 22 hours ago Was this helpful? --- # Roles and Permissions for Mailroom | Mailroom | Verkada Help This article describes the set of roles and associated permissions for Verkada Mailroom. For more information on roles and permissions for other Verkada product lines, see [Roles and Permissions for Command](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) . * **Site-level roles** determine the access a user or group has to devices in the site. * **Org-level roles** allow users or groups to manage permissions and devices at a global level. * **Permissions** are set using roles, which define the level of access users and groups have to devices and settings within an organization and its sites. * * * ### [](https://help.verkada.com/mailroom/roles-and-permissions-for-mailroom#permissions-considerations) Permissions considerations * Subsites inherit permissions from all parent sites, including the ultimate parent. * Users can belong to multiple groups. When roles conflict, the user receives the **highest role** granted directly or through any group. * Group-assigned roles can be manually upgraded but not downgraded. Remove the user from the group with the higher role to downgrade their access. * * * [](https://help.verkada.com/mailroom/roles-and-permissions-for-mailroom#site-level-roles) Site-level roles --------------------------------------------------------------------------------------------------------------- Site-level roles can be assigned to individual users or groups and are specific to a particular site. Subsites inherit the permissions from the parent sites above them. Site Viewer[](https://help.verkada.com/mailroom/roles-and-permissions-for-mailroom#site-viewer) * View Mailroom logs and analytics. * Scan in delivered packages. * Search for packages delivered. * View context camera footage (if the user has the appropriate [camera permissions](https://help.verkada.com/verkada-cameras/configuration-and-setup/roles-and-permissions-for-cameras) ). Site Admin[](https://help.verkada.com/mailroom/roles-and-permissions-for-mailroom#site-admin) * Manage employees from site-specific employee lists. * Edit site-specific Mailroom Settings. * Add/edit cameras (only if the user has at least a Live-Only Viewer role for Cameras). * Add/edit doors (only if the user is an [Access Site Admin](https://help.verkada.com/access-control/roles-and-permissions-for-access-control) ). * View Mailroom logs and analytics. * Scan in delivered packages. * Search for packages delivered. * View context camera footage (if the user has the appropriate [camera permissions](https://help.verkada.com/verkada-cameras/configuration-and-setup/roles-and-permissions-for-cameras) ). [](https://help.verkada.com/mailroom/roles-and-permissions-for-mailroom#org-level-roles) Org-level roles ------------------------------------------------------------------------------------------------------------- Org Admin[](https://help.verkada.com/mailroom/roles-and-permissions-for-mailroom#org-admin) * Assign/remove Workplace Site Admin role. * Assign/remove Workplace Site Viewer role. * Import and modify sites. * Manage employees from site-specific and organization-level employee lists. * Edit site-specific and organization-level Mailroom settings. * Add/edit cameras (if the user is at least a Live-Only Viewer for the cameras in the site). * View Mailroom logs and analytics. * Scan in delivered packages. * Search for packages delivered. * View context camera footage (if the user has the appropriate [camera permissions](https://help.verkada.com/verkada-cameras/configuration-and-setup/roles-and-permissions-for-cameras) ). * * * [](https://help.verkada.com/mailroom/roles-and-permissions-for-mailroom#set-permissions) Set permissions ------------------------------------------------------------------------------------------------------------- You can set site permissions for existing users and groups by managing user roles, groups, or sites. Users[](https://help.verkada.com/mailroom/roles-and-permissions-for-mailroom#users) In Verkada Command, go to All Products > Admin .Under Org Settings, select Users.Select a user.At the top right, click Manage Roles.a. Set the needed permissions. b. Click Save. Groups[](https://help.verkada.com/mailroom/roles-and-permissions-for-mailroom#groups) In Verkada Command, go to All Products > Admin .Under Org Settings, select Groups.Select a group.At the top, select Site Roles > Manage Roles.a. Set the needed permissions. b. Click Save. Sites[](https://help.verkada.com/mailroom/roles-and-permissions-for-mailroom#sites) In Verkada Command, go to All Products > Admin .In the left navigation, select Sites.Select a site to manage and in the right pane, click Manage .a. In the top right, click Add to add a new user or group. b. Select an existing user or group to edit their permissions. * * * [](https://help.verkada.com/mailroom/roles-and-permissions-for-mailroom#faq) FAQ ------------------------------------------------------------------------------------- How do I grant Mailroom permissions but not Guest permissions, or vice versa?[](https://help.verkada.com/mailroom/roles-and-permissions-for-mailroom#how-do-i-grant-mailroom-permissions-but-not-guest-permissions-or-vice-versa) To separate these permissions, make your Mailroom site and Guest site separate sites entirely. Guest and Mailroom sites imported from the same site will share the roles given to users. Learn more about [Roles and Permissions for Mailroom](https://help.verkada.com/mailroom/roles-and-permissions-for-mailroom) . Can a Mailroom user get access to my cameras if they have "No Access" to the site in Command?[](https://help.verkada.com/mailroom/roles-and-permissions-for-mailroom#can-a-mailroom-user-get-access-to-my-cameras-if-they-have-no-access-to-the-site-in-command) Mailroom users must have at least the Live-Only Viewer role for the cameras in the site to view the camera feeds in Mailroom. What are the minimum permissions needed to see the Mailroom tab under All Products in Command?[](https://help.verkada.com/mailroom/roles-and-permissions-for-mailroom#what-are-the-minimum-permissions-needed-to-see-the-mailroom-tab-under-all-products-in-command) Users must be at least a Site Viewer for 1 site to see the **Mailroom** tab under **All Products**. What is the best role I should grant to my front desk receptionist?[](https://help.verkada.com/mailroom/roles-and-permissions-for-mailroom#what-is-the-best-role-i-should-grant-to-my-front-desk-receptionist) It depends on the specific permissions you want to grant. In most scenarios, receptionists only need to be Site Viewers. What access is needed to use the Mailroom app?[](https://help.verkada.com/mailroom/roles-and-permissions-for-mailroom#what-access-is-needed-to-use-the-mailroom-app) To use the Mailroom app to scan in packages, ensure that a user is at least a Site Viewer for the site(s) they need access to. Last updated 1 day ago Was this helpful? --- # Set Up Your Viewing Station | Viewing Station | Verkada Help The Verkada [Viewing Station](https://docs.verkada.com/docs/viewing-station-overview.pdf) is a plug-and-play device that streams multiple camera feeds simultaneously on a display with no local configuration required. It serves as a dedicated, admin-managed device with customizable layouts. * Supports up to 30 camera feeds per page * Supports up to 10 pages You must be an **Org Admin** to claim and manage a Viewing Station. * * * [](https://help.verkada.com/viewing-station/set-up-your-viewing-station#connect-your-viewing-station) Connect your viewing station --------------------------------------------------------------------------------------------------------------------------------------- In the box, you’ll find: * HDMI cable * Power cord * Viewing Station remote You’ll need to provide an Ethernet cable. For network configuration details, see [Viewing Station Network Settings](https://help.verkada.com/viewing-station/set-up-your-viewing-station) . ### [](https://help.verkada.com/viewing-station/set-up-your-viewing-station#installation) Installation 1 **Connect the power cord to the Viewing Station and plug it into a power source.** 2 **Connect one end of the HDMI cable to the Viewing Station and the other end to your display.** 3 **Connect an Ethernet cable from the Viewing Station to your network.** * * * [](https://help.verkada.com/viewing-station/set-up-your-viewing-station#claim-your-viewing-station) Claim your viewing station ----------------------------------------------------------------------------------------------------------------------------------- ### [](https://help.verkada.com/viewing-station/set-up-your-viewing-station#find-the-serial-number) Find the serial number There are two ways to find your Viewing Station’s serial number: 1 **On the device: When powered on, the serial number and a QR code appear on the display.** 2 **In Verkada Command:** * Go to **All Products > Devices** and select the Viewing Station. * The right panel displays details such as **Site**, **Location**, **Date Added**, **Serial Number**, **Model**, **Timezone**, and **Local IP**. ### [](https://help.verkada.com/viewing-station/set-up-your-viewing-station#claim-the-device) Claim the device 1 **In Verkada Command, go to All Products > Devices > Add Devices.** 2 **Enter or scan the Viewing Station’s serial number.** 3 **When prompted, claim and configure the device as needed.** Once the VX52 is claimed, it’s ready to be configured and added to your organization’s layout. * * * [](https://help.verkada.com/viewing-station/set-up-your-viewing-station#configure-your-viewing-station) Configure your viewing station ------------------------------------------------------------------------------------------------------------------------------------------- ### [](https://help.verkada.com/viewing-station/set-up-your-viewing-station#find-your-viewing-station) Find your viewing station 1 **In Verkada Command, go to All Products > Devices.** 2 **Filter the list to show Viewing Stations.** 3 **At the top right, select the arrow icon to begin configuration.** ### [](https://help.verkada.com/viewing-station/set-up-your-viewing-station#edit-the-viewing-station-name) Edit the viewing station name 1 **At the top left of the page, select the current name.** 2 **Enter a new, unique name.** ### [](https://help.verkada.com/viewing-station/set-up-your-viewing-station#add-camera-tiles-and-smart-tiles) Add camera tiles and Smart Tiles You can add up to 10 pages and up to 30 live feeds per page. 1 **On the Viewing Station page, select Add Camera Tiles.** 2 **To display additional data, select Add Smart Tiles. Smart Tiles can show:** * The most active camera * The most recent access control event * Air quality or environmental sensor information ### [](https://help.verkada.com/viewing-station/set-up-your-viewing-station#customize-the-layout) Customize the layout 1 **Select Settings (gear icon) > Layout.** 2 **Choose your preferred display layout.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1530499399-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FfFkKNdIGPl0XHde4cZf7%252Fuploads%252Fgit-blob-74ce41d466d1203cc83effd9133c98a73828c18e%252F697768105502ec0b69d723597293bb8821984e8f.jpg%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=28866f2e&sv=2) ### [](https://help.verkada.com/viewing-station/set-up-your-viewing-station#add-additional-pages) Add additional pages 1 **Select the plus (+) icon.** 2 **You can create up to 10 pages, each supporting 30 live feeds.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1530499399-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FfFkKNdIGPl0XHde4cZf7%252Fuploads%252Fgit-blob-baf9e1eeb4f952768ec6abac63f9ca8e7a0d55d5%252F037f5febaca9c158848814a406fa358a31f1c807.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=1f2b617b&sv=2) Each page includes a **timer** that automatically cycles through different sets of cameras on your Viewing Station. * * * [](https://help.verkada.com/viewing-station/set-up-your-viewing-station#configure-viewing-station-settings) Configure viewing station settings --------------------------------------------------------------------------------------------------------------------------------------------------- **Category** **Settings** **Description** **Notifications** Offline Notifications Select which users should receive alerts when the viewing station goes offline. **General** Name Edit your viewing station name. Show Labels If enabled, Viewing Station will show camera names. Enable Cloud Streaming Stream video through the cloud (only when video is unavailable on the local network). This option must be enabled to stream remote cameras. Enable History Playback Allows viewers to scrub through past footage with their Apple TV remote. Due to privacy concerns, some organizations choose to disable this feature, restricting their VX to display only live footage. Test Offline Mode Simulate a WAN outage on the viewing station to test offline connectivity. Mute Audio Mute the audio in camera video playback. Global Banner Create a text banner on every page on this Viewing Station. Locale Set the language on your Viewing Station. Delete Device will be removed from this organization. **Intercoms** Intercom Integrations Select intercoms that will display video during an in-progress call. [**Wi-Fi**](https://help.verkada.com/viewing-station/set-up-your-viewing-station#h_f283fae089) Wi-Fi Configure your viewing station to use Wi-Fi. **Device** General settings View general device settings. Copy Existing Viewing Station Copy live feed configurations and Viewing Station settings from another Viewing Station in your organization. Restart Viewing Station The viewing station becomes unavailable for a few minutes while it restarts. ### [](https://help.verkada.com/viewing-station/set-up-your-viewing-station#configure-wi-fi) Configure Wi-Fi Wi-Fi support on the Viewing Station requires Verkada software version 2.2.0 (137) or higher. You can find the software version and serial number under **Settings > Device**. 1 **Connect the Viewing Station to a wired network and complete the setup process.** 2 **Once it is online via a wired network, enter the Wi-Fi Network Name (SSID).** 3 **Select the Security Type (WPA3, WPA2, WPA, WEP, or None).** 4 **Enter the Wi-Fi network Password, then click Save.** **Note:** Hidden SSIDs are not supported. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1530499399-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FfFkKNdIGPl0XHde4cZf7%252Fuploads%252Fgit-blob-eade08960dae5235133c37c6ebc3ad02f5e306b7%252F9894a169ef95c64b46bbecff3d0c965ad16169be.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=22710d4d&sv=2) 5 **Wait 1–2 minutes and then power down the viewing station, disconnect the network cable, and power it back on. The viewing station should then connect to Wi-Fi and continue operating as usual.** Last updated 17 hours ago Was this helpful? --- # Review Responses from Command | Incident Response | Verkada Help In Command, you can manage active and historic Responses, review key metrics, track evacuees and guardians, and access a complete log of actions taken. These tools give Workplace Site Admins a central view to monitor and manage every stage of the Incident Response process. You need at least Workplace Site Admin permissions to view the Analytics page. * * * ### [](https://help.verkada.com/incident-response/review-responses-from-command#analytics) Analytics The **Analytics** page displays key metrics for each Response, including: * Evacuees updated by person type (Student, Staff, or Visitor) * Total number of evacuees by status * Total unique evacuees updated by each staff member ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3922624211-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252Fn49pz7ZddUdVxNdz2EFE%252Fuploads%252Fgit-blob-c089fa43d1900485235a6616bb90526b3ebedd0e%252F84e91c9f156ee4266f57674da82dfb1858721dea.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=d4bc3683&sv=2) * * * ### [](https://help.verkada.com/incident-response/review-responses-from-command#evacuees) Evacuees Workplace Site Admins can review the status and updates for all evacuees on the **Evacuees** page. Admins can filter the list of evacuees by status, location, as well as class section. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3922624211-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252Fn49pz7ZddUdVxNdz2EFE%252Fuploads%252Fgit-blob-632b3e064f8d1c3566bedabe747fdde349536348%252F9a4a196f24ee73de9abc931c750d246c2edcfc44.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=67af96d0&sv=2) ### [](https://help.verkada.com/incident-response/review-responses-from-command#guardians) Guardians Employees will see the **Guardians** page for Response Templates with Reunification enabled. This allows Workplace Site Admins to view all signed-in guardians and their details. ### [](https://help.verkada.com/incident-response/review-responses-from-command#history) History The **History** page shows all actions taken in the Incident Response Portal for a single Response. Logs can be exported as a .json file from this page. 1 **In Verkada Command, go to All Products > Workplace Incident Response.** 2 **Select a Response.** 3 **At the top, select History.** 4 **In the top right, select Export logs.** Last updated 18 hours ago Was this helpful? --- # Roles and Permissions for Air Quality Sensors | Air Quality | Verkada Help This article describes the set of roles and associated permissions for Verkada [Air Quality Sensors](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) . For more information on roles and permissions for other Verkada product lines, see [Roles and Permissions for Command](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) . * **Site-level roles** determine the access a user or group has to devices in the site. * **Org-level roles** allow users or groups to manage permissions and devices at a global level. * **Permissions** are set using roles, which define the level of access users and groups have to devices and settings within an organization and its sites. * * * ### [](https://help.verkada.com/air-quality/roles-and-permissions-for-air-quality-sensors#permissions-considerations) Permissions considerations * Subsites inherit permissions from all parent sites, including the ultimate parent. * Users can belong to multiple groups. When roles conflict, the user receives the **highest role** granted directly or through any group. * Group-assigned roles can be manually upgraded but not downgraded. Remove the user from the group with the higher role to downgrade their access. * * * [](https://help.verkada.com/air-quality/roles-and-permissions-for-air-quality-sensors#site-level-roles) Site-level roles ----------------------------------------------------------------------------------------------------------------------------- No Access[](https://help.verkada.com/air-quality/roles-and-permissions-for-air-quality-sensors#no-access) A No Access user **cannot** view air quality devices within a site. Live-Only Viewer[](https://help.verkada.com/air-quality/roles-and-permissions-for-air-quality-sensors#live-only-viewer) A Live-Only Viewer user **cannot** view air quality devices within a site. Site Viewer[](https://help.verkada.com/air-quality/roles-and-permissions-for-air-quality-sensors#site-viewer) * View the sensors in the site * View analytics values for the sensors in the site * Toggle between different durations (live, today, this week, etc.) * View dashboards Site Admin[](https://help.verkada.com/air-quality/roles-and-permissions-for-air-quality-sensors#site-admin) For each category below, Site Admins can perform specific actions. **Air Quality Sensors Home** * Add/remove devices. * Move devices between sites. * Set up (enable/disable) and edit triggers and their sensitivity values. * Reboot a device. * Set up offline notifications for the sensors in the sites they have access to. * Link a camera as a context camera to monitor events. **Note:** You must be a Site Admin for the site the camera is in. * Download a (comma-separated value) CSV file of the sensor data for any of the readings. * Enable live audio and recorded audio (for [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) s that support audio recording and have this feature enabled). **Dashboards** * Pair dashboards with a display. * Share the dashboard with other users. * Delete dashboards. * Edit tiles to view a time-series line graph. * Display sensor readings only. * View a single aggregated metric, a gauge, or a list of the readings’ values. * Delete tiles on the dashboard. * Choose the sensor to view on the dashboard. * Choose which sensor readings to display on each tile (for example, Temp/Vape Index/Humidity, and so on). * Choose the timescale (3 hrs or 24 hrs \[only two options available\]). * Adjust the thresholds for each of the selected values to set their own ranges for good, fair, and bad values. **Analytics** * View the values and the sites where the Site Admin has access. * Sort filters to view specific readings, such as Temp/Vape Index/Humidity, and duration (weekly, daily, monthly). * Toggle between sites where the Site Admin has access. [](https://help.verkada.com/air-quality/roles-and-permissions-for-air-quality-sensors#org-level-roles) Org-level roles --------------------------------------------------------------------------------------------------------------------------- Org Admin[](https://help.verkada.com/air-quality/roles-and-permissions-for-air-quality-sensors#org-admin) The Org Admin must also be a Site Admin for the sites where the sensors are located. * Create and edit dashboards. * Enable/disable features for sensors (sensor audio, BACnet, calibration). * **Only role** that can calibrate sensors. * **Only role** that can create, edit, and remove dashboards. * * * [](https://help.verkada.com/air-quality/roles-and-permissions-for-air-quality-sensors#set-permissions) Set permissions --------------------------------------------------------------------------------------------------------------------------- You can set site permissions for existing users and groups by managing user roles, groups, or sites. You will have access to all cameras, viewing stations, air quality sensors, intercoms, gateways, New Alarms, and Command Connectors once you have been granted permissions for a site. Users[](https://help.verkada.com/air-quality/roles-and-permissions-for-air-quality-sensors#users) In Verkada Command, go to All Products > Admin .UnderOrg Settings, select Users.Select a user.At the top right, click Manage Roles.a. Set the needed permissions. b. Click Save. Groups[](https://help.verkada.com/air-quality/roles-and-permissions-for-air-quality-sensors#groups) In Verkada Command, go to All Products > Admin .UnderOrg Settings, select Groups.Select a group.At the top, select Site Roles > Manage Roles.a. Set the needed permissions. b. Click Save. Sites[](https://help.verkada.com/air-quality/roles-and-permissions-for-air-quality-sensors#sites) In Verkada Command, go to All Products > Admin .In the left navigation, select Sites.Select a site to manage and in the right pane, click Manage .a. In the top right, click Add to add a new user or group. b. Select an existing user or group to edit their permissions. Last updated 22 hours ago Was this helpful? --- # Customize Your Mailroom Dashboard | Mailroom | Verkada Help Verkada Mailroom streamlines delivery management across all your facilities, ensuring inventory, supplies, and packages reach the right people on time. Each Mailroom site includes a customizable dashboard for tracking and managing deliveries. * * * [](https://help.verkada.com/mailroom/configuration-and-setup/customize-your-mailroom-dashboard#switch-between-your-mailroom-sites) Switch between your Mailroom sites -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- To switch between your different Mailroom sites, click the dropdown at the top left corner and select a site. * * * [](https://help.verkada.com/mailroom/configuration-and-setup/customize-your-mailroom-dashboard#search-for-packages) Search for packages -------------------------------------------------------------------------------------------------------------------------------------------- 1 **In Verkada Command, go to All Products > Workplace > Mailroom.** 2 **In the left navigation, select Mailroom Home.** 3 **On the right, Mailroom Admins can:** * Search for packages by **recipient name**, **location**, **carrier**, or **arrival/pickup date**. * Switch between packages that are **waiting** or **picked up**. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F287279980-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FNVCL5fLNdL5l9LkT0AR5%252Fuploads%252Fgit-blob-0cdd8831874fe76fe323a05c74bfe15b41e9fdcf%252F066f8c944bdb3491fcca63f4a0110b3c9c8316cc.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=dc40bdf3&sv=2) * * * [](https://help.verkada.com/mailroom/configuration-and-setup/customize-your-mailroom-dashboard#add-context-cameras) Add context cameras -------------------------------------------------------------------------------------------------------------------------------------------- You can add up to 4 context cameras to a Mailroom site. It can be helpful to link cameras that cover areas ,such as loading docks, lobbies, package rooms, etc. 1 **In Verkada Command, go to All Products > Workplace > Mailroom.** 2 **On the left navigation, select Mailroom Settings.** 3 **At the top, click Sites > your site.** 4 **Under Context Cameras, click Manage cameras.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F287279980-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FNVCL5fLNdL5l9LkT0AR5%252Fuploads%252Fgit-blob-26499fb2da4ccc9976377237b92b55eb62619611%252F2411830ea6864bb58af244492348861a53d6cb1c.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=f1b5c36f&sv=2) 5 **Select up to 4 cameras that will appear at the top of the Mailroom site page. To clear the selected cameras (or existing cameras), click Clear.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F287279980-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FNVCL5fLNdL5l9LkT0AR5%252Fuploads%252Fgit-blob-ff46f5d9339d58796923de030ff33e041218d56b%252Fb0eebacbd0485a0111cb9669d91ae0ecd65b24b2.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=9ef5124&sv=2) Last updated 17 hours ago Was this helpful? --- # Command Connector Network Settings | Command Connector | Verkada Help This article outlines the required network settings for your Command Connector to communicate with non-Verkada cameras and [Verkada Command](https://help.verkada.com/command/get-started-with-verkada-command) . For more information on the required network settings for other Verkada product lines, see [Required Network Settings](https://help.verkada.com/command/required-network-settings) . The Command Connector has 2 RJ-45 Ethernet interfaces. Only **connect one** of the interfaces to your network for initial configuration. To configure both ports, see [Configure Two Ethernet Ports for Command Connector](https://help.verkada.com/command-connector/configuration-and-setup/configure-two-ethernet-ports-for-command-connector) . [](https://help.verkada.com/command-connector/command-connector-network-settings#ip-address) IP address ------------------------------------------------------------------------------------------------------------ The Command Connector must be assigned an IPv4 address to communicate on the LAN and with Verkada Command. The Command Connector obtains its IP address and network configurations using Dynamic Host Configuration Protocol (DHCP). The Command Connector has two ethernet interfaces. If you are using IP address reservations, it is recommended to configure two reservations—one for each Ethernet port. [](https://help.verkada.com/command-connector/command-connector-network-settings#domain-name-system) Domain Name System ---------------------------------------------------------------------------------------------------------------------------- Command Connectors use a DNS server to resolve Verkada’s fully qualified domain names (FQDN) to IP addresses to communicate with them. Your DHCP server tells the Command Connector where the DNS server is on the network, and it communicates using UDP port 53. DNS over HTTPS (DoH) is currently not supported. [](https://help.verkada.com/command-connector/command-connector-network-settings#non-verkada-cameras) Non-Verkada cameras ------------------------------------------------------------------------------------------------------------------------------ Ensure that the Command Connector and non-Verkada cameras can communicate bi-directionally. If they are on separate or remote subnets, verify that routing works correctly in both directions. Note that dynamic NAT or Layer 3 (L3) translation is not supported between these devices. Command Connector connects to non-Verkada cameras over the LAN using port 554 to pull RTSP streams, and port 80 or 8080 for ONVIF HTTP requests. Verify these ports are allowed on the network: * **TCP+UDP ports 80, 8080, 443**: Enables the Command Connector to read and set camera parameters. * **TCP+UDP port 554**: Enables the Command Connector to ingest RTSP video streams from non-Verkada cameras. * **TCP+UDP Port 3702**: Enables WS-Discovery so the Command Connector can discover and connect to non-Verkada cameras over the LAN. [](https://help.verkada.com/command-connector/command-connector-network-settings#firewall-settings) Firewall settings -------------------------------------------------------------------------------------------------------------------------- Command Connectors require access to many endpoints to ensure they can communicate with Command and all features will be accessible. Many customers may want to allow the Command Connector to communicate with the general required endpoints. These are the general domains to allow, **applicable for all organizations**: Copy 34.216.15.26 - UDP/123 (Fallback NTP) *:4100 - TCP/UDP on LAN *.verkada.com - UDP/123 + TCP+UDP/443 time.cloudflare.com - TCP/4460 + UDP/123 *.amazonaws.com - TCP+UDP/443 If you prefer a more granular allowlist, you can add IP addresses, full FQDNs, and wildcard domains to your firewall rules based on the region where your devices are located. Your region is selected when you [create an organization](https://help.verkada.com/command/get-started-with-verkada-command) in Command. ### [](https://help.verkada.com/command-connector/command-connector-network-settings#region-united-states) Region: United States Copy 34.216.15.26 - UDP/123 (Fallback NTP) *:4100 - TCP/UDP on LAN (for local streaming) api.control.verkada.com - TCP+UDP/443 api-ga.control.verkada.com - TCP+UDP/443 api.global-prod.control.verkada.com - TCP+UDP/443 device.pyramid.verkada.com - TCP+UDP/443 firmware.control.verkada.com - TCP+UDP/443 index.control.verkada.com - TCP+UDP/443 relay.control.verkada.com - TCP+UDP/443 relay.global-prod.control.verkada.com - TCP+UDP/443 time.control.verkada.com - UDP/123 update.control.verkada.com - TCP+UDP/443 vlogging.command.verkada.com - TCP+UDP/443 user.pyramid.verkada.com - TCP+UDP/443 vconductor.global-prod.command.verkada.com - TCP+UDP/443 *.kinesisvideo.us-west-2.amazonaws.com - TCP+UDP/443 s3.ap-southeast-2.amazonaws.com - TCP/443†‡ s3.ca-central-1.amazonaws.com - TCP/443†‡ s3.eu-west-1.amazonaws.com - TCP/443†‡ s3.us-west-2.amazonaws.com - TCP/443† time.cloudflare.com - TCP/4460 + UDP/123 vlogging.command.verkada.com/connect-box-logs - TCP+UDP/443 vlogging.global-prod.command.verkada.com/connect-box-logs - TCP+UDP/443 ### [](https://help.verkada.com/command-connector/command-connector-network-settings#region-europe) Region: Europe Copy 34.216.15.26 - UDP/123 (Fallback NTP) *:4100 - TCP/UDP on LAN (for local streaming) api-ga.control.verkada.com - TCP+UDP/443 api.global-prod.control.verkada.com - TCP+UDP/443 api.prod2.control.verkada.com - TCP+UDP/443 index.prod2.control.verkada.com - TCP+UDP/443 relay.global-prod.control.verkada.com - TCP+UDP/443 relay.prod2.control.verkada.com - TCP+UDP/443 time.cloudflare.com - TCP/4460 + UDP/123 time.control.verkada.com - UDP/123 update.control.verkada.com - TCP+UDP/443 vconductor.global-prod.command.verkada.com - TCP+UDP/443 vconductor.prod2.command.verkada.com - TCP+UDP/443 *.eu-west-1.compute.amazonaws.com - TCP+UDP/443 *.eu-west-1.compute.amazonaws.com - UDP/1024 to 65535 (only required for PTZ cameras) *.kinesisvideo.eu-west-1.amazonaws.com - TCP+UDP/443 s3.eu-west-1.amazonaws.com - TCP/443† vlogging.prod2.command.verkada.com/connect-box-logs TCP+UDP/443 vlogging.global-prod.command.verkada.com/connect-box-logs - TCP+UDP/443 ### [](https://help.verkada.com/command-connector/command-connector-network-settings#region-australia) Region: Australia Copy 34.216.15.26 - UDP/123 (Fallback NTP) *:4100 - TCP/UDP on LAN (only required for local streaming) api-ga.control.verkada.com - TCP+UDP/443 api.global-prod.control.verkada.com - TCP+UDP/443 api.prod-ap-syd.control.verkada.com - TCP+UDP/443 index.prod.ap.syd.control.verkada.com - TCP+UDP/443 relay.global-prod.control.verkada.com - TCP+UDP/443 relay.prod-ap-syd.control.verkada.com - TCP+UDP/443 time.cloudflare.com - TCP/4460 + UDP/123 time.control.verkada.com - UDP/123 update.control.verkada.com - TCP+UDP/443 vconductor.global-prod.command.verkada.com - TCP+UDP/443 vconductor.prod.ap.syd.command.verkada.com - TCP+UDP/443 *.eu-west-1.compute.amazonaws.com - TCP+UDP/443 *.eu-west-1.compute.amazonaws.com - UDP/1024 to 65535 (only required for PTZ cameras) *.kinesisvideo.eu-west-1.amazonaws.com - TCP+UDP/443 s3.eu-west-1.amazonaws.com - TCP/443† vlogging.prod-ap-syd.command.verkada.com/connect-box-logs TCP+UDP/443 vlogging.global-prod.command.verkada.com/connect-box-logs - TCP+UDP/443 **Footnotes:** * †Required for cloud backup. * ‡Only required if your [data storage location](https://help.verkada.com/command/data-protection-and-security/set-a-default-or-camera-specific-location-for-image-and-video-data-storage-and-processing) is set outside of the US. Use the [Verkada Network Tester](https://network-tester.support.verkada.com/) to verify your devices can connect to Verkada Command. Select your region and the **Command Connector** product type to run the check. The following endpoints must be allowed on your network for the test to work: * speed.cloudflare.com * network-tester.support.verkada.com Last updated 22 hours ago Was this helpful? --- # Get Started with Incident Response | Incident Response | Verkada Help Incident Response helps organizations track the well-being and location of people during an incident. It enables organizations to account for employees and visitors, and allows schools to reunite students with their guardians. Incident Response is only available in sites with Verkada Guest. * * * [](https://help.verkada.com/incident-response/get-started-with-incident-response#set-up-incident-response) Set up Incident Response ---------------------------------------------------------------------------------------------------------------------------------------- You need **Org Admin** permissions to configure Incident Response. ### [](https://help.verkada.com/incident-response/get-started-with-incident-response#initial-site) Initial site 1 **In Verkada Command, go to All Products > Workplace Incident Response.** 2 **Click Import Existing Guest Sites.** 3 **Select your site > Import Site.** ### [](https://help.verkada.com/incident-response/get-started-with-incident-response#additional-sites) Additional sites After setting up the first Workplace site for Incident Response, you can configure additional sites. 1 **In Verkada Command, go to All Products > Workplace Incident Response.** 2 **On the left navigation, click Incident Response Settings.** 3 **At the top, select Organization > Sites.** 4 **Click Import Site.** * * * [](https://help.verkada.com/incident-response/get-started-with-incident-response#response-templates) Response templates ---------------------------------------------------------------------------------------------------------------------------- Workplace Site Admins can create Response Templates for different types of incidents. A Response Template defines: * Who needs to be accounted for as evacuees * What statuses can be assigned to evacuees * Where evacuees can be marked as present For schools, configure the Response Template for Reunification and set up a Guardian Form. See [Create Response Templates](https://help.verkada.com/incident-response/create-response-templates) for more information. * * * [](https://help.verkada.com/incident-response/get-started-with-incident-response#workplace-employees) Workplace Employees ------------------------------------------------------------------------------------------------------------------------------ Employees assigned to an Incident Response site can take part in any active Response at that site. Employees are shared across all Workplace products (Guest, Mailroom, and Incident Response) for that site. * You need **Workplace Site Admins** to manage site-level employee lists. * You need **Org Admins** permissions to manage the organization-level employee list. 1 **In Verkada Command, go to All Products > Workplace Incident Response.** 2 **On the left navigation, click Incident Response Settings.** 3 **At the top, select Site > Employees.** 4 **Select Manage Employee List.** See [Manage Host Lists in Guest](https://help.verkada.com/guest/configuration-and-setup/manage-host-lists-in-guest) for more information. * * * [](https://help.verkada.com/incident-response/get-started-with-incident-response#launch-a-response) Launch a Response -------------------------------------------------------------------------------------------------------------------------- Only **Workplace Site Admins** can launch a Response. 1 **In Verkada Command, go to All Products > Workplace Incident Response.** 2 **On the Incident Response Home, click Launch Response.** 3 **Select a Response Template.** 4 **(Optional) Toggle on Drill mode to treat the Response as a drill.** **Note:** If Drill mode is enabled, toggle on **Notify Staff** to send notifications with magic links to employees. 5 **Click Launch.** When a Response is launched (Drill mode disabled), all employees will be sent notifications that include magic links to the [Incident Response portal](https://help.verkada.com/incident-response/incident-response-portal) . ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3922624211-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252Fn49pz7ZddUdVxNdz2EFE%252Fuploads%252Fgit-blob-80eb931955c613ccbd9286b6a1cc67c55f4d3a9d%252F7a71e02311aa5330d387458c32ea839bfb9f90f4.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=6b59e4e7&sv=2) At the beginning of a Response, all evacuees have a status and location of **Unknown**. * * * [](https://help.verkada.com/incident-response/get-started-with-incident-response#end-a-response) End a Response -------------------------------------------------------------------------------------------------------------------- You need permissions **Workplace Site Admins** to end a Response. 1 **In Verkada Command, go to All Products > Workplace Incident Response.** 2 **On the Incident Response Home, click Active Response.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3922624211-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252Fn49pz7ZddUdVxNdz2EFE%252Fuploads%252Fgit-blob-08d26370f24e2030d89ddf46cecca217fe977375%252F71fbc94f4fb1839db5b4d5618af5f6c415d8d453.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=26f179a1&sv=2) 3 **In the top right, click End.** 4 **In the confirmation menu, select End Incident.** Ending a Response locks further changes on the Incident Response portal. For non-Drill Responses, all employees are notified that the Response has ended. Last updated 18 hours ago Was this helpful? --- # Hardware Installation | Classic Alarms | Verkada Help [Set Up Universal Transmitter Mode on a BR31 with Classic Alarms](https://help.verkada.com/classic-alarms/hardware-installation/set-up-universal-transmitter-mode-on-a-br31-with-classic-alarms) [Set Up the BK11/BK21 Alarm Keypad](https://help.verkada.com/classic-alarms/hardware-installation/set-up-the-bk11bk21-alarm-keypad) [Alarm Setup and Install Best Practices](https://help.verkada.com/classic-alarms/hardware-installation/alarm-setup-and-install-best-practices) [Set Up the BC82 Alarm Console](https://help.verkada.com/classic-alarms/hardware-installation/set-up-the-bc82-alarm-console) [Configure a BX21 Wireless Relay](https://help.verkada.com/classic-alarms/hardware-installation/configure-a-bx21-wireless-relay) [Battery Backup for the BP41 Alarm Panel](https://help.verkada.com/classic-alarms/hardware-installation/battery-backup-for-the-bp41-alarm-panel) [Set Up Your Wireless Alarm Devices](https://help.verkada.com/classic-alarms/hardware-installation/set-up-your-wireless-alarm-devices) [Set Up the BC51 Alarm Console](https://help.verkada.com/classic-alarms/hardware-installation/set-up-the-bc51-alarm-console) [Configure and Wire Inputs/Outputs on the BP41](https://help.verkada.com/classic-alarms/hardware-installation/configure-and-wire-inputsoutputs-on-the-bp41) [Supervised Wiring with Classic Alarms](https://help.verkada.com/classic-alarms/hardware-installation/supervised-wiring-with-classic-alarms) Last updated 1 month ago Was this helpful? --- # Get Started with Verkada Classic Alarms | Classic Alarms | Verkada Help This article is a guide for classic Alarms. Refer to this [article](https://help.verkada.com/new-alarms/getting-started-with-verkada-alarms) if you have new Alarms. See [New Alarms vs Classic Alarms](https://help.verkada.com/new-alarms/new-alarms-vs-classic-alarms) if you are unsure which version of Alarms you have. * * * Verkada [Alarms](https://docs.verkada.com/docs/alarms-professional-monitoring-overview.pdf) , also known in the industry as _intrusion detection_ or simply _intrusion_, provide fully integrated, 24/7 professional monitoring with emergency dispatch services. You can use your existing Verkada devices without purchasing any additional hardware. You need Org Admin and/or Site Admin [permissions](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) for your Verkada Command organization to complete these actions. ### [](https://help.verkada.com/classic-alarms/get-started-with-verkada-classic-alarms#what-you-need) What you need * PoE-enabled switch or PoE injector * DHCP-enabled network * Cat5 or Cat6 cabling [](https://help.verkada.com/classic-alarms/get-started-with-verkada-classic-alarms#create-a-site) Create a site -------------------------------------------------------------------------------------------------------------------- Sites are the logical way of grouping and managing devices within your Command organization. Site-level permissions make managing and viewing your devices easier. See [Alarms Sites](https://help.verkada.com/classic-alarms/configuration-and-setup/classic-alarms-sites) for more information on site creation and management. ### [](https://help.verkada.com/classic-alarms/get-started-with-verkada-classic-alarms#configure-settings) Configure settings The Alarms site settings page allows you to configure various settings, such as alarm triggers, arm/disarm schedules, alarm responses, and more. Each site’s settings can be uniquely configured to suit your security needs. See [Configure Alarms Site Settings](https://help.verkada.com/classic-alarms/configuration-and-setup/configure-classic-alarms-site-settings) for more information. [](https://help.verkada.com/classic-alarms/get-started-with-verkada-classic-alarms#add-alarms-devices) Add Alarms devices ------------------------------------------------------------------------------------------------------------------------------ You can add an Alarms device from the **Devices** page. See [Add a Device to Your Command Account](https://help.verkada.com/verkada-cameras/configuration-and-setup/add-a-device-to-your-command-organization) for more information. [](https://help.verkada.com/classic-alarms/get-started-with-verkada-classic-alarms#licensing) Licensing ------------------------------------------------------------------------------------------------------------ Most Alarms devices you manage in Command will need a license. Verkada licensing is applied for each Command organization, and the licenses co-term to a single expiration date. Your licenses may have been automatically added if you claimed your devices via order number. Otherwise, manually add the licenses from the Admin page. See [Manage Your Licenses](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses) for more information on adding and managing licenses. [](https://help.verkada.com/classic-alarms/get-started-with-verkada-classic-alarms#connect-your-alarms-devices) Connect your Alarms devices ------------------------------------------------------------------------------------------------------------------------------------------------ While Verkada Alarms devices are considered low-voltage devices that do not require a certified electrician to install, we strongly recommend you work with a system integrator or other professional for installation. Please refer to the device [setup guide](https://www.verkada.com/docs/?product=alarms&contentType=setupGuide) for installation instructions. #### [](https://help.verkada.com/classic-alarms/get-started-with-verkada-classic-alarms#powered-and-network) Powered and network The Alarms devices are powered in various ways. * The Alarms consoles, hub, and horn speaker use Power over Ethernet (PoE) for power and communication over the LAN. In most cases, these devices need to connect directly to a standard switch. PoE injectors can be used when a PoE switch is not available. * The Alarm panel is powered via AC power and connects to your network via Ethernet. * The wireless relay is powered via DC power. * The wireless Alarms devices are powered by CR123A lithium batteries. For more information on power and network requirements, see the product [datasheet](https://www.verkada.com/docs/?product=alarms&contentType=datasheet) . [](https://help.verkada.com/classic-alarms/get-started-with-verkada-classic-alarms#check-network-settings) Check network settings -------------------------------------------------------------------------------------------------------------------------------------- Verkada Alarms devices are designed to be plug-and-play. However, if your environment includes a firewall with custom rules and policies, you may need to make some configuration changes to get your devices connected to the cloud. See [Alarms Network Settings](https://help.verkada.com/classic-alarms/classic-alarms-network-settings) for more information. [](https://help.verkada.com/classic-alarms/get-started-with-verkada-classic-alarms#alarms-reports) Alarms reports ---------------------------------------------------------------------------------------------------------------------- Reports allow you to easily gather information about your Alarms site. You can create reports for a variety of events, including device actions and video verifications. For more information on creating reports, see [Alarms Reports](https://help.verkada.com/classic-alarms/networking-and-reports/alarms-reports) . [](https://help.verkada.com/classic-alarms/get-started-with-verkada-classic-alarms#alarms-monitoring-certificate) Alarms Monitoring Certificate ---------------------------------------------------------------------------------------------------------------------------------------------------- An Alarm Monitoring Certificate confirms that Verkada professionally monitors your alarm system and serves as proof for your insurance provider. See [Verkada Alarms Monitoring Certificate](https://help.verkada.com/new-alarms/alarms-specifications/verkada-alarms-monitoring-certificate) for more information. ​ Last updated 1 day ago Was this helpful? --- # Configuration and Setup | Command Connector | Verkada Help [Change a non-Verkada Camera Resolution](https://help.verkada.com/command-connector/configuration-and-setup/change-a-non-verkada-camera-resolution) [Configure a Non-Verkada PTZ (Pan-Tilt-Zoom) Camera](https://help.verkada.com/command-connector/configuration-and-setup/configure-a-non-verkada-ptz-pan-tilt-zoom-camera) [Configure Two Ethernet Ports for Command Connector](https://help.verkada.com/command-connector/configuration-and-setup/configure-two-ethernet-ports-for-command-connector) [Configure Static IP Addresses for Command Connector](https://help.verkada.com/command-connector/configuration-and-setup/configure-static-ip-addresses-for-command-connector) [Change a non-Verkada Channel Orientation](https://help.verkada.com/command-connector/configuration-and-setup/change-a-non-verkada-channel-orientation) [Change Storage Settings on Non-Verkada Cameras](https://help.verkada.com/command-connector/configuration-and-setup/change-storage-settings-on-non-verkada-cameras) [Add a non-Verkada camera to a Command Connector](https://help.verkada.com/command-connector/configuration-and-setup/add-a-non-verkada-camera-to-a-command-connector) Last updated 1 month ago Was this helpful? --- # Troubleshooting | Intercom | Verkada Help [Loss of Network Connection for Intercom](https://help.verkada.com/intercom/troubleshooting/loss-of-network-connection-for-intercom) Last updated 1 month ago Was this helpful? --- # Alerts and Events | Access Control | Verkada Help [Access Control Tailgate Detection](https://help.verkada.com/access-control/alerts-and-events/access-control-tailgate-detection) [Configure Access Control Event Alerts](https://help.verkada.com/access-control/alerts-and-events/configure-access-control-event-alerts) Last updated 1 month ago Was this helpful? --- # Configuration and Setup | Classic Alarms | Verkada Help [Classic Alarms App Download](https://help.verkada.com/classic-alarms/configuration-and-setup/classic-alarms-app-download) [Alarm Schedule Exception](https://help.verkada.com/classic-alarms/configuration-and-setup/alarm-schedule-exception) [Verkada Alarm API](https://help.verkada.com/classic-alarms/configuration-and-setup/verkada-alarm-api) [Agent Talk Down with Classic Alarms](https://help.verkada.com/classic-alarms/configuration-and-setup/agent-talk-down-with-classic-alarms) [Verification Rules](https://help.verkada.com/classic-alarms/configuration-and-setup/verification-rules) [Set Up the BZ11 Horn Speaker with Classic Alarms](https://help.verkada.com/classic-alarms/configuration-and-setup/set-up-the-bz11-horn-speaker-with-classic-alarms) [Set Up and Install Wireless Sensors](https://help.verkada.com/classic-alarms/configuration-and-setup/set-up-and-install-wireless-sensors) [Generate a User or General Keycode with Classic Alarms](https://help.verkada.com/classic-alarms/configuration-and-setup/generate-a-user-or-general-keycode-with-classic-alarms) [How to Arm/Disarm Your Alarm Site](https://help.verkada.com/classic-alarms/configuration-and-setup/how-to-armdisarm-your-alarm-site) [Configure Classic Alarms Site Settings](https://help.verkada.com/classic-alarms/configuration-and-setup/configure-classic-alarms-site-settings) [Classic Alarms Sites](https://help.verkada.com/classic-alarms/configuration-and-setup/classic-alarms-sites) Last updated 1 month ago Was this helpful? --- # Hardware and Installation | Intercom | Verkada Help [TD53/63 Intercom Lens Cover Replacement](https://help.verkada.com/intercom/hardware-and-installation/td5363-intercom-lens-cover-replacement) [Wire an Intercom to a Blue Light Tower](https://help.verkada.com/intercom/hardware-and-installation/wire-an-intercom-to-a-blue-light-tower) [Configure a Second-Generation Intercom as a 1-Door AC](https://help.verkada.com/intercom/hardware-and-installation/configure-a-second-generation-intercom-as-a-1-door-ac) [Mount a TD52](https://help.verkada.com/intercom/hardware-and-installation/mount-a-td52) Last updated 1 month ago Was this helpful? --- # Roles and Permissions for Intercom | Intercom | Verkada Help This article describes the set of roles and associated permissions for [Verkada Intercom](https://help.verkada.com/intercom/get-started-with-verkada-intercom) . For more information on roles and permissions for other Verkada product lines, see [Roles and Permissions for Command](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) . * **Site-level roles** determine the access a user or group has to devices in the site. * **Permissions** are set using roles, which define the level of access users and groups have to devices and settings within an organization and its sites. * * * ### [](https://help.verkada.com/intercom/roles-and-permissions-for-intercom#permissions-considerations) Permissions considerations * Subsites inherit permissions from all parent sites, including the ultimate parent. * Users can belong to multiple groups. When roles conflict, the user receives the **highest role** granted directly or through any group. * Group-assigned roles can be manually upgraded but not downgraded. Remove the user from the group with the higher role to downgrade their access. * * * [](https://help.verkada.com/intercom/roles-and-permissions-for-intercom#site-level-roles) Site-level roles --------------------------------------------------------------------------------------------------------------- Verkada Intercom permissions determine who can receive calls, view intercom video, and unlock intercom doors. Intercom permissions depend on your site-level permissions and whether you’re configured as a Receiver. You must be configured as a receiver to receive calls. At a high level, these are the permissions granted to each level of Intercom devices: ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3022285914-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FTH6kITd3Fb5UOnnsfQ9r%252Fuploads%252Fgit-blob-3c0d4d35489d7c354c25e790a8403f314714b5f4%252F6dd199e34e75c9300457af4e6fe86e544ec5e6d2.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=72f3ae9e&sv=2) Receiver[](https://help.verkada.com/intercom/roles-and-permissions-for-intercom#receiver) Verkada Intercom Receivers have the baseline receiver permissions. A user’s intercom permissions for a site are based on their baseline and site-level roles. Receivers, such as Desk Stations and Session Initiation Protocol (SIP) phones\*\*,\*\* are not tied to a Verkada Command user. This means these receivers cannot be granted site-level permissions. Regardless of their site-level permissions, a Receiver can: * Receive calls with video. * See 24/7 live intercom video, even if not on an active call. * Unlock the door both during and outside of a call. * Talk down to the intercom. Live-View Only[](https://help.verkada.com/intercom/roles-and-permissions-for-intercom#live-view-only) * Receive calls with video. * See 24/7 live intercom video, even if not on an active call. Site Viewer[](https://help.verkada.com/intercom/roles-and-permissions-for-intercom#site-viewer) * Receive calls with video. * See 24/7 live intercom video, even if not on an active call. * View historical video and events. Site Admin[](https://help.verkada.com/intercom/roles-and-permissions-for-intercom#site-admin) * Receive calls with video. * See 24/7 live intercom video, even if not on an active call. * View historical video and events. * Unlock the door both during and outside of a call. * Unlock the door 24/7. * Talk down to the intercom. * Change Receivers and device settings. * * * ### [](https://help.verkada.com/intercom/roles-and-permissions-for-intercom#verify-a-users-eligibility-to-receive-verkada-pass-calls) Verify a user’s eligibility to receive Verkada Pass calls Users configured as receivers can answer calls from the Pass app. To check their eligibility, hover over![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3022285914-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FTH6kITd3Fb5UOnnsfQ9r%252Fuploads%252Fgit-blob-1025db08c5e6037ca1add97d01d61e290737f5f5%252F49ef4eb350f3daea087651a2bb2502c8dc5bd92e.png%3Falt%3Dmedia&width=300&dpr=4&quality=100&sign=fb71d87c&sv=2) next to the user’s name in the receiver list. * A user who has **previously logged in** to Verkada Pass will see **Pass App**. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3022285914-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FTH6kITd3Fb5UOnnsfQ9r%252Fuploads%252Fgit-blob-d4fbf243067696300febaaa88e549c1a9ae54270%252Fee0f927746019a9d211a636944976a26046fdc27.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=20715ca1&sv=2) * A user who has **never logged in** to the Verkada Pass will see **Send Pass App Invite** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3022285914-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FTH6kITd3Fb5UOnnsfQ9r%252Fuploads%252Fgit-blob-3837a7e6d709232a65455d0640b85df88ac5691a%252F2496e67c27edda822836d16c93bbf9bb4e8c7a34.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=f143d425&sv=2) * * * [](https://help.verkada.com/intercom/roles-and-permissions-for-intercom#set-permissions) Set permissions ------------------------------------------------------------------------------------------------------------- You can set site permissions for existing users and groups by managing user roles, groups, or sites. You will have access to all cameras, viewing stations, air quality sensors, intercoms, gateways, New Alarms, and Command Connectors once you have been granted permissions for a site. Users[](https://help.verkada.com/intercom/roles-and-permissions-for-intercom#users) In Verkada Command, go to All Products > Admin .UnderOrg Settings, select Users.Select a user.At the top right, click Manage Roles.a. Set the needed permissions. b. Click Save. Groups[](https://help.verkada.com/intercom/roles-and-permissions-for-intercom#groups) In Verkada Command, go to All Products > Admin .UnderOrg Settings, select Groups.Select a group.At the top, select Site Roles > Manage Roles.a. Set the needed permissions. b. Click Save. * * * **Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=SeBWHZAwCBg) . Last updated 1 day ago Was this helpful? --- # Getting Started with Verkada Alarms | New Alarms | Verkada Help This article is a guide for new Alarms. Refer to this [article](https://help.verkada.com/classic-alarms/get-started-with-verkada-classic-alarms) if you have classic Alarms. See [New Alarms vs Classic Alarms](https://help.verkada.com/new-alarms/new-alarms-vs-classic-alarms) if you are unsure which version of Alarms you have. * * * Verkada Alarms, also known in the industry as _intrusion detection_ or simply _intrusion_, provides fully integrated, 24/7 professional monitoring with emergency dispatch services. You can use your existing Verkada devices without purchasing any additional hardware. You need Org Admin and/or Site Admin [permissions](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) for your Verkada Command organization to complete these actions. ### [](https://help.verkada.com/new-alarms/getting-started-with-verkada-alarms#what-you-need) What you need * PoE-enabled switch or PoE injector (Cameras) * DHCP-enabled network * Cat5 or Cat6 cabling [](https://help.verkada.com/new-alarms/getting-started-with-verkada-alarms#create-a-site) Create a site ------------------------------------------------------------------------------------------------------------ Sites are the logical way of grouping and managing devices within your Command organization. Site-level permissions make managing and viewing your devices easier. See Alarms Sites for more information on site creation and management. ### [](https://help.verkada.com/new-alarms/getting-started-with-verkada-alarms#configure-settings) Configure settings The Alarms site settings page allows you to configure various settings, such as alarm triggers, arm/disarm schedules, alarm responses, and more. Each site’s settings can be uniquely configured to suit your security needs. See Configure Alarms Site Settings for more information. [](https://help.verkada.com/new-alarms/getting-started-with-verkada-alarms#add-alarms-devices) Add Alarms devices ---------------------------------------------------------------------------------------------------------------------- You can add serialized alarm devices (keypad, expander, etc.) from the alarm devices page you will need to change the view. Click the three horizontal lines located in the top right [](https://help.verkada.com/new-alarms/getting-started-with-verkada-alarms#licensing) Licensing ---------------------------------------------------------------------------------------------------- The cellular backup module is the only hardware device that requires a license. An Alarms license is required for each location that is monitored. Verkada licensing is applied for each Command organization, and the licenses co-term to a single expiration date. Your licenses may have been automatically added if you claimed your devices via order number. Otherwise, manually add the licenses from the Admin page. See [Manage Your Licenses](https://app.intercom.com/a/apps/q5re5q6g/articles/articles/6326326/show) for more information on adding and managing licenses. [](https://help.verkada.com/new-alarms/getting-started-with-verkada-alarms#connect-your-alarms-devices) Connect your Alarms devices ---------------------------------------------------------------------------------------------------------------------------------------- While Verkada Alarms devices are considered low-voltage devices that do not require a certified electrician to install, we strongly recommend you work with a system integrator or other professional for installation. Please refer to the device [setup guide](https://www.verkada.com/docs/?product=alarms&contentType=setupGuide) for installation instructions. ### [](https://help.verkada.com/new-alarms/getting-started-with-verkada-alarms#powered-and-network) Powered and network The alarm devices are powered in various ways. * The Alarms console requires DC power via the alarm panel and connects to your network via Ethernet. * The Alarm panel is powered via AC power and connects to your network via Ethernet. * The horn speaker uses Power over Ethernet (PoE) for power and communication over the LAN. In most cases, it needs to connect directly to a standard switch. PoE injectors can be used when a PoE switch is not available. * The wireless Alarms devices are powered by CR123A lithium batteries. For more information on power and network requirements, see the product datasheet. [](https://help.verkada.com/new-alarms/getting-started-with-verkada-alarms#check-network-settings) Check network settings ------------------------------------------------------------------------------------------------------------------------------ Verkada Alarms devices are designed to be plug-and-play. However, if your environment includes a firewall with custom rules and policies, you may need to make some configuration changes to get your devices connected to the cloud. See [Alarms Network Settings](https://help.verkada.com/new-alarms/alarms-specifications/alarms-network-settings) for more information. [](https://help.verkada.com/new-alarms/getting-started-with-verkada-alarms#alarms-monitoring-certificate) Alarms Monitoring Certificate -------------------------------------------------------------------------------------------------------------------------------------------- An Alarm Monitoring Certificate confirms that Verkada professionally monitors your alarm system and serves as proof for your insurance provider. See [Verkada Alarms Monitoring Certificate](https://help.verkada.com/new-alarms/alarms-specifications/verkada-alarms-monitoring-certificate) for more information. ​ Last updated 23 hours ago Was this helpful? --- # Notifications | Guest | Verkada Help [Set Up Bells for Verkada Guest](https://help.verkada.com/guest/notifications/set-up-bells-for-verkada-guest) Last updated 1 month ago Was this helpful? --- # Access Control Network Settings | Access Control | Verkada Help This article outlines the required network settings that your Verkada [access controllers](https://docs.verkada.com/docs/access-controllers-series-overview.pdf) need to communicate with [Verkada Command](https://help.verkada.com/command/get-started-with-verkada-command) . For more information on the required network settings for other Verkada product lines see [Required Network Settings](https://help.verkada.com/command/required-network-settings) . Verkada devices are incompatible with LANs that require proxy servers or Secure Socket Layer (SSL)/Transport Layer Security (TLS) inspection. If either is in use, a bypass for all Verkada devices must be implemented for Verkada devices to communicate with Verkada Command. [](https://help.verkada.com/access-control/access-control-network-settings#status-led) Status LED ------------------------------------------------------------------------------------------------------ At the top left of the physical access controller, if you see a flashing blue [status LED](https://help.verkada.com/access-control/troubleshooting/verkada-ac41-status-led) this indicates that the access controller is not communicating with Command. If you see this behavior: * Check that the network is set up correctly for the access controller. * See [Verkada Access Offline Operation](https://help.verkada.com/access-control/troubleshooting/verkada-access-offline-operation) to understand what the access system does when it cannot communicate with Command. If the problem persists, contact [Verkada Support](https://help.verkada.com/command/need-help/contact-verkada-support) . [](https://help.verkada.com/access-control/access-control-network-settings#ip-address) IP address ------------------------------------------------------------------------------------------------------ Access controllers need an IPv4 address to communicate on the local area network (LAN) and to Command through the internet. Access controllers use Dynamic Host Configuration Protocol (DHCP), UDP ports 67 and 68, to obtain their IP addresses and network configurations. If you want to have a specific IP address on your access controller, set a DHCP reservation using the access controller’s [Media Access Control (MAC) address](https://help.verkada.com/access-control/hardware-installation/find-a-serial-number-and-mac-address) (found on the device’s label). [](https://help.verkada.com/access-control/access-control-network-settings#domain-name-system) Domain Name System ---------------------------------------------------------------------------------------------------------------------- Access Controllers use the DNS server to resolve Verkada’s fully qualified domain names (FQDN) to IP addresses to communicate with them. Your DHCP server tells the access controller where the DNS server is on the network and the access controller communicates using UDP port 53. DNS over HTTPS (DoH) is currently not supported. [](https://help.verkada.com/access-control/access-control-network-settings#power) Power -------------------------------------------------------------------------------------------- For specifics on power requirements, see the [access controller’s datasheet](https://www.verkada.com/docs/?product=accessControl&contentType=datasheet) . [](https://help.verkada.com/access-control/access-control-network-settings#firewall-settings) Firewall settings -------------------------------------------------------------------------------------------------------------------- Verkada access controllers require access to many endpoints to ensure they can communicate with Command and all features will be accessible. Many customers may want to allow the access controllers to communicate with the general required endpoints. These are the general domains to allow, **applicable for all organization-regions**: Copy 34.216.15.26 - UDP/123 35.166.49.153 - UDP/123 + TCP+UDP/443 *.verkada.com - UDP/123 + TCP+UDP/443 If you prefer a more granular allowlist, you can add both IP addresses and full FQDNs to your firewall rules based on the region where your devices are located. Your region is selected when you [create an organization](https://help.verkada.com/command/get-started-with-verkada-command) in Command. ### [](https://help.verkada.com/access-control/access-control-network-settings#region-united-states) Region: United States **Standard Verkada Endpoints** Copy api.control.verkada.com - TCP+UDP/443 api.global-prod.control.verkada.com - TCP+UDP/443 api-ga.control.verkada.com - TCP+UDP 443 firmware.control.verkada.com - TCP+UDP/443 update.control.verkada.com - TCP+UDP/443 vconductor.global-prod.command.verkada.com - TCP+UDP/443 **NTP Endpoints** Copy 34.216.15.26 - UDP/123 35.166.49.153 - UDP/123 + TCP+UDP/443 time.control.verkada.com - UDP/123 time.cloudflare.com - TCP/4460 time.cloudflare.com - UDP/123 **Access Control Endpoints** Copy access.control.verkada.com - TCP+UDP/443 vcerberus.command.verkada.com - TCP+UDP/443 ### [](https://help.verkada.com/access-control/access-control-network-settings#region-europe) Region: Europe **Standard Verkada Endpoints** Copy access.prod2.command.verkada.com - TCP+UDP/443 api.global-prod.control.verkada.com - TCP+UDP/443 api.prod2.control.verkada.com - TCP+UDP/443 api-ga.control.verkada.com - TCP+UDP 443 relay.prod2.control.verkada.com - TCP+UDP/443 update.control.verkada.com - TCP+UDP/443 vconductor.global-prod.command.verkada.com - TCP+UDP/443 vconductor.prod2.command.verkada.com - TCP+UDP/443 vpeer-to-peer.prod2.command.verkada.com - TCP+UDP/443 vinnout.prod2.command.verkada.com - TCP+UDP/443 **NTP Endpoints** Copy 35.166.49.153 - UDP/123 + TCP+UDP/443 time.control.verkada.com - UDP/123 time.cloudflare.com - TCP/4460 time.cloudflare.com - UDP/123 **Access Control Endpoints** Copy access.prod2.command.verkada.com - TCP+UDP/443 vcerberus.command.verkada.com - TCP+UDP/443 ### [](https://help.verkada.com/access-control/access-control-network-settings#region-australia) Region: Australia **Standard Verkada Endpoints** Copy access.prod-ap-syd.command.verkada.com - TCP+UDP/443 api.global-prod.control.verkada.com - TCP+UDP/443 api.prod-ap-syd.control.verkada.com - TCP+UDP/443 api-ga.control.verkada.com - TCP+UDP 443 relay.prod-ap-syd.control.verkada.com - TCP+UDP/443 update.control.verkada.com - TCP+UDP/443 vconductor.global-prod.command.verkada.com - TCP+UDP/443 vconductor.prod-ap-syd.command.verkada.com - TCP+UDP/443 vpeer-to-peer.prod-ap-syd.command.verkada.com - TCP+UDP/443 vinnout.prod-ap-syd.command.verkada.com - TCP+UDP/443 **NTP Endpoints** Copy 35.166.49.153 - UDP/123 + TCP+UDP/443 time.control.verkada.com - UDP/123 time.cloudflare.com - TCP/4460 time.cloudflare.com - UDP/123 **Access Control Endpoints** Copy access.prod-ap-syd.command.verkada.com - TCP+UDP/443 vcerberus.command.verkada.com - TCP+UDP/443 Use the [Verkada Network Tester](https://network-tester.support.verkada.com/) to verify your devices can connect to Verkada Command. Select your region and the **Access** product type to run the check. The following endpoints must be allowed on your network for the test to work: * speed.cloudflare.com * network-tester.support.verkada.com Last updated 22 hours ago Was this helpful? --- # Events and Alerts | New Alarms | Verkada Help [Configure New Alarms Event Alerts](https://help.verkada.com/new-alarms/events-and-alerts/configure-new-alarms-event-alerts) Last updated 1 month ago Was this helpful? --- # Troubleshooting | New Alarms | Verkada Help [Wireless Signal Troubleshooting](https://help.verkada.com/new-alarms/troubleshooting/wireless-signal-troubleshooting) [BR31 Troubleshooting Guide](https://help.verkada.com/new-alarms/troubleshooting/br31-troubleshooting-guide) Last updated 1 month ago Was this helpful? --- # Get Started with Verkada Intercom | Intercom | Verkada Help Verkada’s intercom solution enables you to answer calls, grant entry, and secure entrances from anywhere. **Required.** You need Org Admin and/or Site Admin [permissions](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) for your Verkada Command organization to complete these actions. ### [](https://help.verkada.com/intercom/get-started-with-verkada-intercom#what-you-need) What you need * PoE-enabled switch or PoE injector * DHCP-enabled network * Cat5 or Cat6 cabling [](https://help.verkada.com/intercom/get-started-with-verkada-intercom#create-a-site) Create a site -------------------------------------------------------------------------------------------------------- Sites are the logical way of grouping and managing devices within your Command organization. Site-level permissions make managing and viewing your devices easier. See [Manage Your Sites and Subsites](https://help.verkada.com/verkada-cameras/configuration-and-setup/manage-sites-and-subsites) for more information on site creation and management. [](https://help.verkada.com/intercom/get-started-with-verkada-intercom#add-an-intercom) Add an intercom ------------------------------------------------------------------------------------------------------------ At least one intercom needs to be added to Command before you can see the **Intercom** tab in the **All Products** menu. Intercoms can be added to Command from the **Devices** page. See [Add an Intercom to Your Site](https://help.verkada.com/intercom/configuration-and-setup/add-an-intercom-to-your-site) for more information. #### [](https://help.verkada.com/intercom/get-started-with-verkada-intercom#connect-a-door) Connect a door You can pair an existing access-controlled door or wire a door to the intercom that can be unlocked by an [intercom receiver](https://help.verkada.com/intercom/get-started-with-verkada-intercom#h_c6863790e9) . See [Configure a TD52](https://help.verkada.com/intercom/configuration-and-setup/configure-a-td52) and [Wire a TD52 Video Intercom](https://help.verkada.com/intercom/configuration-and-setup/wire-a-video-intercom) for more information. #### [](https://help.verkada.com/intercom/get-started-with-verkada-intercom#configure-receivers) Configure receivers Receivers allow you to answer calls from an intercom and unlock any associated doors. See [Add and Configure Receivers in Intercom](https://help.verkada.com/intercom/configuration-and-setup/add-and-configure-receivers-in-intercom) for more information. [](https://help.verkada.com/intercom/get-started-with-verkada-intercom#licensing) Licensing ------------------------------------------------------------------------------------------------ Every intercom you manage in Command will need a license. Verkada licensing is applied for each Command organization, and the licenses co-term to a single expiration date. Your licenses may have been automatically added if you claimed your devices via order number. Otherwise, manually add the licenses from the Admin page. See [Manage Your Licenses](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses) for more information on adding and managing licenses. [](https://help.verkada.com/intercom/get-started-with-verkada-intercom#connect-your-intercom) Connect your intercom ------------------------------------------------------------------------------------------------------------------------ **Recommendation**. While Verkada intercoms are considered low-voltage devices that do not require a certified electrician to install, we strongly recommend you work with a system integrator or other professional for installation. Please refer to the intercom [setup guide](https://www.verkada.com/docs/?product=intercom&contentType=setupGuide) for instructions on mounting and wiring the door port. #### [](https://help.verkada.com/intercom/get-started-with-verkada-intercom#power-and-network) Power and network Verkada intercoms use Power over Ethernet (PoE) for power and communication over the LAN. In most cases, intercoms will connect directly to an 802.3af PoE standard switch. PoE injectors can be used when a PoE switch is not available. See the intercom’s [datasheet](https://www.verkada.com/docs/?product=intercom&contentType=datasheet) for more information. [](https://help.verkada.com/intercom/get-started-with-verkada-intercom#check-network-settings) Check network settings -------------------------------------------------------------------------------------------------------------------------- Verkada intercoms are designed to be plug-and-play. However, if your environment includes a firewall with custom rules and policies, you may need to make some configuration changes to get your access controllers connected to the cloud. See [Intercom Network Settings](https://help.verkada.com/intercom/intercom-network-settings) for more information. * * * **Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=O26przAa220) . Last updated 1 day ago Was this helpful? --- # Troubleshooting | Access Control | Verkada Help [Reader Connectivity Status on Command](https://help.verkada.com/access-control/troubleshooting/reader-connectivity-status-on-command) [Configure Dry Lock on an AC41](https://help.verkada.com/access-control/troubleshooting/configure-dry-lock-on-an-ac41) [Access Control Hardware Checks](https://help.verkada.com/access-control/troubleshooting/access-control-hardware-checks) [Verkada Card Reader LED Behavior](https://help.verkada.com/access-control/troubleshooting/verkada-card-reader-led-behavior) [Verkada Access Offline Operation](https://help.verkada.com/access-control/troubleshooting/verkada-access-offline-operation) [Troubleshoot an Immediate Door Relock](https://help.verkada.com/access-control/troubleshooting/troubleshoot-an-immediate-door-relock) [Verkada AC41 Status LED](https://help.verkada.com/access-control/troubleshooting/verkada-ac41-status-led) [Use the AC41 Test Buttons](https://help.verkada.com/access-control/troubleshooting/use-the-ac41-test-buttons) [Restart an Access Controller](https://help.verkada.com/access-control/troubleshooting/restart-an-access-controller) Last updated 1 month ago Was this helpful? --- # Get Started with Verkada Guest | Guest | Verkada Help Verkada Guest enables your organization to quickly and securely manage guest access to your building and key areas. Guest leverages camera feeds and door events to track guests and hosts across your organization. You need Org Admin and/or Site Admin [permissions](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) for your Verkada Command organization to complete these actions. ### [](https://help.verkada.com/guest/get-started-with-verkada-guest#what-you-need) What you need * iPad on iOS 14 or higher * Badge printer * iPad stand (optional, but recommended for best Guest experience) [](https://help.verkada.com/guest/get-started-with-verkada-guest#create-a-site) Create a site -------------------------------------------------------------------------------------------------- Sites are the logical way of grouping and managing devices within your Command organization. Site-level permissions make managing and viewing your devices easier. See [Guest Sites](https://help.verkada.com/guest/configuration-and-setup/guest-sites) for more information on site creation and management. #### [](https://help.verkada.com/guest/get-started-with-verkada-guest#configure-settings) Configure settings You can edit Guest settings at the organization level or site level. You can create Guest types, add cameras and doors to your sites, manage multiple languages, etc, to make your guest check-in experience easier. See [Guest Settings](https://help.verkada.com/guest/configuration-and-setup/view-and-edit-guest-settings) for more information. [](https://help.verkada.com/guest/get-started-with-verkada-guest#add-and-connect-guest-devices) Add and connect Guest devices ---------------------------------------------------------------------------------------------------------------------------------- #### [](https://help.verkada.com/guest/get-started-with-verkada-guest#guest-tablet) Guest tablet Guest tablets are used to check in guests to your organization. You can add a tablet from the Guest site settings page. See [Set up a Guest Tablet](https://help.verkada.com/guest/configuration-and-setup/set-up-a-guest-tablet) for more information. #### [](https://help.verkada.com/guest/get-started-with-verkada-guest#badge-printer) Badge printer Badge printers are used to print badges for your guests to wear while they are on your premises. You can add a badge printer from the Guest site settings page. See [Add a Printer to Verkada Guest](https://help.verkada.com/guest/configuration-and-setup/printers/brother-printer-setup-guide) for more information. [](https://help.verkada.com/guest/get-started-with-verkada-guest#licensing) Licensing ------------------------------------------------------------------------------------------ Every Guest tablet you manage in Command will need a license. Verkada licensing is applied for each Command organization, and the licenses co-term to a single expiration date. For more information on adding and managing licenses, see [Manage Your Licenses](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses) . [](https://help.verkada.com/guest/get-started-with-verkada-guest#check-network-settings) Check network settings -------------------------------------------------------------------------------------------------------------------- Verkada Guest is designed to be plug-and-play. However, if your environment includes a firewall, you may need to make some configuration changes to get your Guest devices online. See [Guest Network Setting](https://help.verkada.com/guest/guest-network-settings) [**s**](https://help.verkada.com/guest/guest-network-settings) for more information. For security screens to load properly in Guest from a computer, you should allowlist crimimages.com for TCP port 443 in any filtering device between the computer and your Internet Service Provider (ISP). Last updated 22 hours ago Was this helpful? --- # Healthcare | Guest | Verkada Help [Configure the Patient Visit Guest Type](https://help.verkada.com/guest/healthcare/configure-the-patient-visit-guest-type) [Set up a Guest Tablet for Healthcare](https://help.verkada.com/guest/healthcare/set-up-a-guest-tablet-for-healthcare) [Healthcare Visitor Verification](https://help.verkada.com/guest/healthcare/healthcare-visitor-verification) [Use the Guest Healthcare Portal](https://help.verkada.com/guest/healthcare/use-the-guest-healthcare-portal) [Inpatient Visitor Sign-in](https://help.verkada.com/guest/healthcare/inpatient-visitor-sign-in) [Manage Departments and Checkpoints](https://help.verkada.com/guest/healthcare/manage-departments-and-checkpoints) Last updated 1 month ago Was this helpful? --- # Roles and Permissions for New Alarms | New Alarms | Verkada Help This article is a guide for New Alarms. Refer to this [article](https://help.verkada.com/classic-alarms/roles-and-permissions-for-classic-alarms) if you have classic Alarms. See [New Alarms vs Classic Alarms](https://help.verkada.com/new-alarms/new-alarms-vs-classic-alarms) if you are unsure which version of Alarms you have. This article describes the set of roles and associated permissions for Verkada Alarms. For more information on roles and permissions for other Verkada product lines, see [Roles and Permissions for Command](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) . * **Site-level roles** determine the access a user or group has to devices in the site. * **Permissions** are set using roles, which define the level of access users and groups have to devices and settings within an organization and its sites. * * * ### [](https://help.verkada.com/new-alarms/roles-and-permissions-for-new-alarms#permissions-considerations) Permissions considerations * Subsites inherit permissions from all parent sites, including the ultimate parent. * Users can belong to multiple groups. When roles conflict, the user receives the **highest role** granted directly or through any group. * Group-assigned roles can be manually upgraded but not downgraded. Remove the user from the group with the higher role to downgrade their access. * * * [](https://help.verkada.com/new-alarms/roles-and-permissions-for-new-alarms#new-alarms-roles) New Alarms roles ------------------------------------------------------------------------------------------------------------------- #### [](https://help.verkada.com/new-alarms/roles-and-permissions-for-new-alarms#arm-disarm) Arm / Disarm Users with this role can arm and disarm the site and resolve alarms through Command (web or mobile). They cannot access the alarm site configuration or other products unless explicitly granted permission. This role is suited for users such as guards, cleaning staff, or contractors who need basic permissions to arm or disarm the alarm system without broader site or product access. #### [](https://help.verkada.com/new-alarms/roles-and-permissions-for-new-alarms#unassigned) Unassigned This is the default role for users without an assigned New Alarms role. Users with this role cannot arm and disarm, access the alarm site configuration, or access other products. * * * [](https://help.verkada.com/new-alarms/roles-and-permissions-for-new-alarms#site-level-roles) Site-level roles ------------------------------------------------------------------------------------------------------------------- No Access[](https://help.verkada.com/new-alarms/roles-and-permissions-for-new-alarms#no-access) * Cannot view the alarm site. * If added as a **response contact** for the alarm site, they can resolve an alarm and disarm the site through the incident link and agent call. Site Viewer[](https://help.verkada.com/new-alarms/roles-and-permissions-for-new-alarms#site-viewer) * Cannot create or edit an alarm site. * Cannot arm or disarm alarm sites or resolve an alarm via Command. * Can view all alarm activity and event history with historical footage and live streams. * If added as a **response contact** for the alarm site, they can resolve an alarm and disarm the site through the incident link and agent call. Site Admin[](https://help.verkada.com/new-alarms/roles-and-permissions-for-new-alarms#site-admin) * Can create or edit an alarm site. * Can create and edit keycodes along with all other alarm configurations. * Can arm or disarm alarm sites or resolve an alarm via Command. * Can add or remove Verkada devices and wired inputs/outputs on the site. * Can view all alarm activity and event history with historical video. * If added as a **response contact** for the alarm site, they can resolve an alarm and disarm the site through the incident link and agent call. If a user is granted a **keycode** to the alarm site, they can arm or disarm the site and resolve an alarm via the keypad. * * * [](https://help.verkada.com/new-alarms/roles-and-permissions-for-new-alarms#set-permissions) Set permissions ----------------------------------------------------------------------------------------------------------------- You will have access to all cameras, viewing stations, air quality sensors, intercoms, gateways, New Alarms, and Command Connectors once you have been granted permissions for a site. User[](https://help.verkada.com/new-alarms/roles-and-permissions-for-new-alarms#user) 1. In Verkada Command, go to All Products > Admin ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2Fdownloads.intercomcdn.com%2Fi%2Fo%2Fq5re5q6g%2F1486870999%2F45308fafc2d4613daa8b2e50f802%2FScreenshot%2B2024-04-11%2Bat%2B10_49_58%25E2%2580%25AFAM.png%3Fexpires%3D1745388000%26signature%3Dadc8ee4008a88dbed98588be5a71a05c30176d978fc19ff1720bfa8b1e7e126a%26req%3DdSQvEMF5nYhWUPMW3Hu4gRH6C4wj8sPMsy1omMhZz9LkqOm09%252BcWpkMJ0rXo%250AQw%253D%253D%250A&width=300&dpr=4&quality=100&sign=20d08960&sv=2). 2. Under![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2Fdownloads.intercomcdn.com%2Fi%2Fo%2Fq5re5q6g%2F1488258786%2Fbfea6facb65e1cbe7142300986ce%2FScreenshot%252B2024-04-11%252Bat%252B10_49_58-E2-80-AFAM.png%3Fexpires%3D1745336400%26signature%3D97b6c7014329f46a270b4108105e8b7f39c894f12860e81c2df1f348cbd17db5%26req%3DdSQvHst7lYZXX%252FMU3HP0gJiLx0FTeXLfgq5wX6mb892cKMRzWgc%253D%250A&width=300&dpr=4&quality=100&sign=69a560c0&sv=2)Org Settings, select Users. 3. Select a user. 4. At the top right, click Manage Roles. 1. Set the needed permissions. 2. Click Save. Groups[](https://help.verkada.com/new-alarms/roles-and-permissions-for-new-alarms#groups) 1. In Verkada Command, go to All Products > Admin ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2Fdownloads.intercomcdn.com%2Fi%2Fo%2Fq5re5q6g%2F1486870999%2F45308fafc2d4613daa8b2e50f802%2FScreenshot%2B2024-04-11%2Bat%2B10_49_58%25E2%2580%25AFAM.png%3Fexpires%3D1745388000%26signature%3Dadc8ee4008a88dbed98588be5a71a05c30176d978fc19ff1720bfa8b1e7e126a%26req%3DdSQvEMF5nYhWUPMW3Hu4gRH6C4wj8sPMsy1omMhZz9LkqOm09%252BcWpkMJ0rXo%250AQw%253D%253D%250A&width=300&dpr=4&quality=100&sign=20d08960&sv=2). 2. Under ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2Fdownloads.intercomcdn.com%2Fi%2Fo%2Fq5re5q6g%2F1488258786%2Fbfea6facb65e1cbe7142300986ce%2FScreenshot%252B2024-04-11%252Bat%252B10_49_58-E2-80-AFAM.png%3Fexpires%3D1745336400%26signature%3D97b6c7014329f46a270b4108105e8b7f39c894f12860e81c2df1f348cbd17db5%26req%3DdSQvHst7lYZXX%252FMU3HP0gJiLx0FTeXLfgq5wX6mb892cKMRzWgc%253D%250A&width=300&dpr=4&quality=100&sign=69a560c0&sv=2)Org Settings, select Groups. 3. Select a group. 4. At the top, select Site Roles > ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2Fdownloads.intercomcdn.com%2Fi%2Fo%2Fq5re5q6g%2F1486864216%2F277b2e030a75bc121e797c7e25ce%2FScreenshot%2B2024-03-22%2Bat%2B4_23_32%25E2%2580%25AFPM.png%3Fexpires%3D1745388000%26signature%3Dc5ea8dc5447153487d53de044a1f8fc725b88835f62f18c593501fefb1bd89a7%26req%3DdSQvEMF4mYNeX%252FMW3Hu4gXAxpVuZ5zRQ%252FodVmahtVdlNZtLLHAi5VFdI8YUR%250AyQ%253D%253D%250A&width=300&dpr=4&quality=100&sign=91688ed6&sv=2)Manage Roles. 1. Set the needed permissions. 2. Click Save. Sites[](https://help.verkada.com/new-alarms/roles-and-permissions-for-new-alarms#sites) 1. In Verkada Command, go to All Products > Admin ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2Fdownloads.intercomcdn.com%2Fi%2Fo%2Fq5re5q6g%2F1486870999%2F45308fafc2d4613daa8b2e50f802%2FScreenshot%2B2024-04-11%2Bat%2B10_49_58%25E2%2580%25AFAM.png%3Fexpires%3D1745388000%26signature%3Dadc8ee4008a88dbed98588be5a71a05c30176d978fc19ff1720bfa8b1e7e126a%26req%3DdSQvEMF5nYhWUPMW3Hu4gRH6C4wj8sPMsy1omMhZz9LkqOm09%252BcWpkMJ0rXo%250AQw%253D%253D%250A&width=300&dpr=4&quality=100&sign=20d08960&sv=2). 2. In the left navigation, select Sites. 3. Select a site to manage and in the right pane, click Manage ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2Fdownloads.intercomcdn.com%2Fi%2Fo%2Fq5re5q6g%2F1488246368%2Fbf7c63026a4cdc5df11d7fd82b70%2FScreenshot%2B2024-05-28%2Bat%2B1_46_52%25E2%2580%25AFPM.png%3Fexpires%3D1745336100%26signature%3D30f0e56e79f7643579d19ff8598288c5309b284873fb48c3b4617141ea1f15d4%26req%3DdSQvHst6m4JZUfMU3HP0gIO0EZvU2SLz7CF6adrhjpOi88R2b4o%253D%250A&width=300&dpr=4&quality=100&sign=be78b69f&sv=2). 1. In the top right, click Add to add a new user or group. 2. Select an existing user or group to edit their permissions. * * * ### [](https://help.verkada.com/new-alarms/roles-and-permissions-for-new-alarms#common-alarm-permission-configurations) Common Alarm permission configurations **Scenario** **Role Configuration** User requires full administrative control of the alarm site. ​For example, a Security Director, Facilities Manager. Site Admin User can view alarm incidents for investigation and arm or disarm the system through Command (web or mobile), but cannot modify the site configuration. ​ ​For example, a SOC team member. Site Viewer + Arm/Disarm User can only arm and disarm the site through Command (web or mobile) and has no access to the alarm site or other products within it. For example, a guard, janitor, or contractor. No access + Arm/Disarm Last updated 23 hours ago Was this helpful? --- # Create a Command Organization | Command | Verkada Help Verkada’s web software is Command. You need Command to interact with and monitor all of your Verkada devices. [](https://help.verkada.com/command/create-a-command-organization#create-a-command-account) Create a Command Account ------------------------------------------------------------------------------------------------------------------------- 1 **Navigate to the** [**Command**](https://command.verkada.com/) **home page.** 2 **Click Create a New Organization.** 3 **Enter your email and click Continue.** 4 **Enter your organization name and select a region to create your organization in.** 5 **Click Next to continue.** 6 **An organization short name will be automatically generated.** **Note:** You can edit the short name to anything not already used by another Command account. 7 **Click Next to continue.** 8 **Select a data residency region for your organization.** 9 **Click Next to continue.** 10 **Enter the following user information:** a. First Name b. Last Name c. Phone (optional) d. Create Password e. Confirm Password 11 **Click Submit to create your organization.** * * * ### [](https://help.verkada.com/command/create-a-command-organization#verify-your-email-address) Verify your email address You will need to verify your email address before you can access your Command account 1 **You will be brought to an overview page after you create your organization.** 2 **Click Next, and you will be prompted to check your inbox for a verification email.** 3 **From the email, click Verify Email.** 4 **A new web page will open confirming the email verification.** 5 **Click Continue to log in to your Command account.** * * * **Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=vme3YdOdhsE) . Last updated 22 hours ago Was this helpful? --- # Verkada Command System Requirements | Command | Verkada Help You can use [Verkada Command](https://www.verkada.com/command/#overview) to interact with and monitor all of your Verkada devices. Command allows the ability to review video from cameras, monitor alarms and device events, configure your devices, and administrate your organization. [](https://help.verkada.com/command/verkada-command-system-requirements#guidelines-for-using-verkada-command) Guidelines for using Verkada Command ------------------------------------------------------------------------------------------------------------------------------------------------------- To make sure your use of Verkada Command is secure and efficient, there are certain minimum system requirements and recommendations to consider and to ensure an optimal experience with Verkada Command. We recommend regularly checking to make sure your setup meets or exceeds all of these criteria. ### [](https://help.verkada.com/command/verkada-command-system-requirements#recommended-compatible-browsers) Recommended compatible browsers Command is compatible with the latest versions of these browsers: * Google Chrome * Safari * Microsoft Edge * Mozilla Firefox Ensure hardware acceleration is enabled for chromium-based browsers for best performance. Other browsers might be able to load Command fully or partially, but this is the list of recommended browsers for an optimal experience. ### [](https://help.verkada.com/command/verkada-command-system-requirements#recommended-compatible-operating-systems) Recommended compatible operating systems * **Windows**: Windows 10 or later * **Mac**: MacOS 10.12 (Monterrey) or later For newer Apple Mac models using the M series processors, all will be compatible with Command. ### [](https://help.verkada.com/command/verkada-command-system-requirements#required-endpoints-and-ports) Required endpoints and ports To allow Command to load from a computer, you should allowlist the parent domain `*.verkada.com` for TCP port 443 in any filtering device between the computer and your Internet Service Provider (ISP). We recommend allowlisting these domains: Copy verkada.com *.verkada.com *.*.verkada.com *.command.verkada.com For logging purposes, which help us improve the Command experience, we recommend allowlisting these domains: Copy *.datadoghq.com *.browser-intake-datadoghq.com Verkada devices have their own set of [required network settings](https://help.verkada.com/command/required-network-settings) , and certain functions in Command, such as [local streaming](https://help.verkada.com/verkada-cameras/live-streaming/local-streaming-on-verkada-cameras) require communication between the computer and the Verkada device. Last updated 1 day ago Was this helpful? --- # Quick Reference Guide for Verkada Intercom | Intercom | Verkada Help [](https://help.verkada.com/intercom/quick-reference-guide-for-verkada-intercom#hardware-installation) Hardware installation --------------------------------------------------------------------------------------------------------------------------------- * [Intercom datasheets](https://www.verkada.com/docs/?product=intercom&contentType=datasheet) * [Intercom setup guides](https://www.verkada.com/docs/?product=intercom&contentType=setupGuide) * [Intercom Deployment Best Practices Guide](https://help.verkada.com/intercom/configuration-and-setup/intercom-deployment-best-practices-guide) * [Mount a TD52](https://help.verkada.com/intercom/hardware-and-installation/mount-a-td52) [](https://help.verkada.com/intercom/quick-reference-guide-for-verkada-intercom#configuration-and-setup) Configuration and Setup ------------------------------------------------------------------------------------------------------------------------------------- * [Get Started with Verkada Intercom](https://help.verkada.com/intercom/get-started-with-verkada-intercom) * [Intercom Network Settings](https://help.verkada.com/intercom/intercom-network-settings) * [Roles and Permissions for Intercom](https://help.verkada.com/intercom/roles-and-permissions-for-intercom) * [Create and Use Shared Call Flows](https://help.verkada.com/intercom/configuration-and-setup/create-and-use-shared-call-flows) * [Add a Desk Station](https://help.verkada.com/intercom/configuration-and-setup/add-a-desk-station) * [Add and Configure Receivers in Intercom](https://help.verkada.com/intercom/configuration-and-setup/add-and-configure-receivers-in-intercom) [](https://help.verkada.com/intercom/quick-reference-guide-for-verkada-intercom#troubleshooting) Troubleshooting --------------------------------------------------------------------------------------------------------------------- * [Loss of Network Connection for Intercom](https://help.verkada.com/intercom/troubleshooting/loss-of-network-connection-for-intercom) Follow [our blog](https://www.verkada.com/blog/) for all our latest features and announcements! Last updated 1 day ago Was this helpful? --- # Configuration and Setup | Connectivity | Verkada Help [Enable Historical GPS Data on GC31-E Gateways](https://help.verkada.com/connectivity/configuration-and-setup/enable-historical-gps-data-on-gc31-e-gateways) [Wi-Fi Network Management for GW31-E](https://help.verkada.com/connectivity/configuration-and-setup/wi-fi-network-management-for-gw31-e) [Add Wi-Fi Gateway to Command](https://help.verkada.com/connectivity/configuration-and-setup/add-wi-fi-gateway-to-command) [Wi-Fi Gateway Status LEDs](https://help.verkada.com/connectivity/configuration-and-setup/wi-fi-gateway-status-leds) [Switch Carriers on the Cellular Gateway](https://help.verkada.com/connectivity/configuration-and-setup/switch-carriers-on-the-cellular-gateway) [Use a PoE Switch with Outdoor Gateways](https://help.verkada.com/connectivity/configuration-and-setup/use-a-poe-switch-with-outdoor-gateways) [Enable IPsec Site-to-Site VPN](https://help.verkada.com/connectivity/configuration-and-setup/enable-ipsec-site-to-site-vpn) [Set up Dynamic DNS for Cellular Gateways](https://help.verkada.com/connectivity/configuration-and-setup/set-up-dynamic-dns-for-cellular-gateways) [Power Options for Outdoor Gateways](https://help.verkada.com/connectivity/configuration-and-setup/power-options-for-outdoor-gateways) [Aiming a Directional Antenna for the Cellular Gateway](https://help.verkada.com/connectivity/configuration-and-setup/aiming-a-directional-antenna-for-the-cellular-gateway) [Use Cellular Gateways for WAN Failover](https://help.verkada.com/connectivity/configuration-and-setup/use-cellular-gateways-for-wan-failover) [Cellular Gateway Dual-SIM Support](https://help.verkada.com/connectivity/configuration-and-setup/cellular-gateway-dual-sim-support) [Cellular Gateway Status LEDs](https://help.verkada.com/connectivity/configuration-and-setup/cellular-gateway-status-leds) [Access the Cellular Gateway Local Server Page](https://help.verkada.com/connectivity/configuration-and-setup/access-the-cellular-gateway-local-server-page) [Add Cellular Gateway to Command](https://help.verkada.com/connectivity/configuration-and-setup/add-cellular-gateway-to-command) Last updated 1 month ago Was this helpful? --- # Alarms Specifications | New Alarms | Verkada Help [Verkada New Alarms Monitoring Certificate](https://help.verkada.com/new-alarms/alarms-specifications/verkada-new-alarms-monitoring-certificate) [Verkada Alarms Monitoring Certificate](https://help.verkada.com/new-alarms/alarms-specifications/verkada-alarms-monitoring-certificate) [Alarms Licensing](https://help.verkada.com/new-alarms/alarms-specifications/alarms-licensing) [Verkada Monitoring Phone Numbers](https://help.verkada.com/new-alarms/alarms-specifications/verkada-monitoring-phone-numbers) [Alarms Devices Bandwidth Usage](https://help.verkada.com/new-alarms/alarms-specifications/alarms-devices-bandwidth-usage) [Alarms Network Settings](https://help.verkada.com/new-alarms/alarms-specifications/alarms-network-settings) Last updated 1 month ago Was this helpful? --- # Hardware Installation | New Alarms | Verkada Help [Daisy Chain Multiple BE32s](https://help.verkada.com/new-alarms/hardware-installation/daisy-chain-multiple-be32s) [Set up the WH32](https://help.verkada.com/new-alarms/hardware-installation/set-up-the-wh32) [Set up the WH52](https://help.verkada.com/new-alarms/hardware-installation/set-up-the-wh52) [Wireless Installations FAQ](https://help.verkada.com/new-alarms/hardware-installation/wireless-installations-faq) [Calculate How Many Batteries are Needed for the BP52](https://help.verkada.com/new-alarms/hardware-installation/calculate-how-many-batteries-are-needed-for-the-bp52) [Set Up Universal Transmitter Mode on a BR31](https://help.verkada.com/new-alarms/hardware-installation/set-up-universal-transmitter-mode-on-a-br31) [Set up a BK22](https://help.verkada.com/new-alarms/hardware-installation/set-up-a-bk22) Last updated 1 month ago Was this helpful? --- # Get Started with Verkada Access Control | Access Control | Verkada Help Verkada’s access control solution enables you to manage access user permissions and monitor entry points with features such as remote unlock and real-time alerts. You need Org Admin and/or Access Site Admin [permissions](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) for your Verkada Command organization to complete these actions. ### [](https://help.verkada.com/access-control/get-started-with-verkada-access-control#what-you-need) What you need * DHCP-enabled network * Cat5 or Cat6 cabling [](https://help.verkada.com/access-control/get-started-with-verkada-access-control#create-a-site) Create a site -------------------------------------------------------------------------------------------------------------------- Sites are the logical way of grouping and managing devices within your Command organization. Site-level permissions make managing and viewing your devices easier. See [Manage Your Sites and Subsites](https://help.verkada.com/verkada-cameras/configuration-and-setup/manage-sites-and-subsites) for more information on site creation and management. [](https://help.verkada.com/access-control/get-started-with-verkada-access-control#add-an-access-controller) Add an access controller ------------------------------------------------------------------------------------------------------------------------------------------ At least one access controller needs to be added to Command before you can see the **Access** tab in the **All Products** menu. Access controllers can be added from the **Devices** page. See [Add an Access Controller to Command](https://help.verkada.com/access-control/configuration-and-setup/add-an-access-controller-to-command) for more information. ### [](https://help.verkada.com/access-control/get-started-with-verkada-access-control#configure-a-door) Configure a door Doors are the configuration and components connected to a Verkada access controller cassette, including a lock, reader, door position indicator (DPI), and request to exit (REX). See [Configure a Door in Command](https://help.verkada.com/access-control/configuration-and-setup/configure-a-door-in-command) for more information on configuring door ports. ### [](https://help.verkada.com/access-control/get-started-with-verkada-access-control#configure-an-aux-output) Configure an AUX output The AUX port on an access controller is used to connect external devices, such as exit buttons, to enhance the functionality of your access control system. See [Configure an AUX Output on an Access Controller](https://help.verkada.com/access-control/configuration-and-setup/configure-an-aux-output-on-an-access-controller) for more information on configuring an AUX port. [](https://help.verkada.com/access-control/get-started-with-verkada-access-control#add-access-users) Add access users -------------------------------------------------------------------------------------------------------------------------- You need to add access users and assign them access credentials before they can unlock a door in your organization. We currently support badge-in, remote unlock, Bluetooth unlock, and web unlock credentials. See [Add a User to the Verkada Access System](https://help.verkada.com/access-control/configuration-and-setup/add-a-user-to-the-verkada-access-system) for more information. #### [](https://help.verkada.com/access-control/get-started-with-verkada-access-control#access-groups) Access groups Access groups are used to group together users who need to have the same permissions to access a door. You cannot badge into a door unless you are in an access group with at least one [access level](https://help.verkada.com/access-control/get-started-with-verkada-access-control#h_b1fa994097) associated. See [Add and Modify Access Groups](https://help.verkada.com/access-control/configuration-and-setup/add-and-modify-access-groups) for more information. #### [](https://help.verkada.com/access-control/get-started-with-verkada-access-control#access-levels) Access levels Access levels are schedules that define when users in an access group can access a door. A door needs to be assigned to an access level, and the access level needs to be assigned to an [access group](https://help.verkada.com/access-control/get-started-with-verkada-access-control#h_b1fa994097) . See [Add and Modify Access Levels](https://help.verkada.com/access-control/configuration-and-setup/add-and-modify-access-levels) for more information. [](https://help.verkada.com/access-control/get-started-with-verkada-access-control#licensing) Licensing ------------------------------------------------------------------------------------------------------------ Every access controlled door you manage in Command needs a license. Verkada licensing is applied for each Command organization, and the licenses co-term on a single expiration date. Your licenses may have been automatically added if you claimed your devices via order number. Otherwise, manually add the licenses from the Admin page. See [Manage Your Licenses](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses) for more information on adding and managing licenses. [](https://help.verkada.com/access-control/get-started-with-verkada-access-control#connect-your-access-controller) Connect your access controller ------------------------------------------------------------------------------------------------------------------------------------------------------ While Verkada access controllers are considered low-voltage devices that do not require a certified electrician to install, we strongly recommend you work with a system integrator or other professional for installation. Refer to the door controller’s [setup guide](https://www.verkada.com/docs/?product=accessControl&contentType=setupGuide) for mounting and wiring instructions. #### [](https://help.verkada.com/access-control/get-started-with-verkada-access-control#power-and-network) Power and network Most Verkada access controllers are powered via AC power and connect to your network via Ethernet. The one-door controllers can be powered via PoE or DC power. See the controller’s [datasheet](https://www.verkada.com/docs/?product=accessControl&contentType=datasheet) for the power and network requirements of your specific access controller model. [](https://help.verkada.com/access-control/get-started-with-verkada-access-control#check-network-settings) Check network settings -------------------------------------------------------------------------------------------------------------------------------------- Verkada access controllers are designed to be plug-and-play. However, if your environment includes a firewall with custom rules and policies, you may need to make some configuration changes to get your access controllers connected to the cloud. See [Access Control Network Settings](https://help.verkada.com/access-control/access-control-network-settings) for more information. [](https://help.verkada.com/access-control/get-started-with-verkada-access-control#configure-alerts) Configure alerts -------------------------------------------------------------------------------------------------------------------------- Verkada Command allows you to receive push, email, and SMS alerts for events generated in your organization. The ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F134288481-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FaaHs5RfKqv9Z49mi02cC%252Fuploads%252Fgit-blob-91bd70c6d63692bdc09cfe2b790499421775da49%252F05283db7c21547b9b9a924fe0723bd14f6720315.png%3Falt%3Dmedia&width=300&dpr=4&quality=100&sign=b3179c5e&sv=2) in the bottom left of Command takes you to the **Alerts** page where you can set up and manage alerts. Access events include door events, controller events, lockdown triggered events, and more. See [Configure Access Control Event Alerts](https://help.verkada.com/access-control/alerts-and-events/configure-access-control-event-alerts) for more information about access events and creating alerts. Last updated 1 day ago Was this helpful? --- # Get Started with Verkada Command | Command | Verkada Help [](https://help.verkada.com/command/get-started-with-verkada-command#create-a-command-account) Create a Command account ---------------------------------------------------------------------------------------------------------------------------- Verkada’s web software is called Command. Command is the platform used to interact with and monitor all of your Verkada devices. See [Create a Command Account](https://help.verkada.com/command/create-a-command-organization) for more information. [](https://help.verkada.com/command/get-started-with-verkada-command#organization-settings) Organization settings ---------------------------------------------------------------------------------------------------------------------- Org Admins will have access to the **Admin** page, where they can manage org-wide settings and configurations. These include managing users, accessing the audit log, licensing, and support access. See [Manage Your Admin Page Settings](https://help.verkada.com/command/organization-wide-settings/manage-your-admin-page-settings) for more information. [](https://help.verkada.com/command/get-started-with-verkada-command#add-devices) Add devices -------------------------------------------------------------------------------------------------- Org Admins need to add devices to Command before you can access and manage them. Add devices from the **Devices** page or directly from the site for some product lines. See [Add a Device to Your Command Account](https://help.verkada.com/verkada-cameras/configuration-and-setup/add-a-device-to-your-command-organization) for more information. [](https://help.verkada.com/command/get-started-with-verkada-command#licensing) Licensing ---------------------------------------------------------------------------------------------- Most Verkada devices managed in Command will need a license. Licenses are managed from the [Manage Licenses](https://command.verkada.com/admin/org-settings/license-manager?tab=productLicenses) page. Verkada licensing is applied for each Command organization, and the licenses co-term to a single expiration date. Your licenses may have been automatically added if you claimed your devices via order number. Otherwise, manually add the licenses from the Admin page. See [Manage Your Licenses](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses) for more information on adding and managing licenses. [](https://help.verkada.com/command/get-started-with-verkada-command#add-users) Add users ---------------------------------------------------------------------------------------------- Your Verkada Command software license includes unlimited users. See [Manage Users in Your Organization](https://help.verkada.com/command/users-and-permissions/manage-users-in-your-organization) for more information. #### [](https://help.verkada.com/command/get-started-with-verkada-command#permissions) Permissions Assign different permission levels to users in your organization based on your organization’s security needs. Permissions can be assigned at the org level and the site level for each product line to give each user the exact amount of access they need. See [Roles and Permissions for Command](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) for more information. #### [](https://help.verkada.com/command/get-started-with-verkada-command#single-sign-on-sso) Single Sign-On (SSO) SSO allows you to log in using a third-party authentication service, such as Okta, Microsoft Entra ID, G Suite, etc. This method provides a single point of management for authentication across multiple applications, including Verkada Command. See [Single Sign-On (SSO)](https://help.verkada.com/command/single-sign-on-sso) for more information. Verkada recommends enabling OIDC instead of SAML when available. #### [](https://help.verkada.com/command/get-started-with-verkada-command#scim) SCIM SCIM allows you to sync users and groups from your IdP management software Verkada Command. This enables you to manage users and permission groups easily. See our [SCIM/SSO](https://help.verkada.com/command/third-party-user-provisioning) section of the knowledge base for more information. * * * **Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=QwSngXrWUoc) . Last updated 1 day ago Was this helpful? --- # Third-Party User Provisioning | Command | Verkada Help [Google Workspace User Provisioning](https://help.verkada.com/command/third-party-user-provisioning/google-workspace-user-provisioning) [Okta SCIM Integration](https://help.verkada.com/command/third-party-user-provisioning/okta-scim-integration) [Microsoft Entra ID SCIM Integration](https://help.verkada.com/command/third-party-user-provisioning/microsoft-entra-id-scim-integration) [Create or Refresh an Organization's SCIM Token](https://help.verkada.com/command/third-party-user-provisioning/create-or-refresh-an-organizations-scim-token) Last updated 29 days ago Was this helpful? --- # Organization-Wide Settings | Command | Verkada Help [Mobile App Version Support and Update Requirements](https://help.verkada.com/command/organization-wide-settings/mobile-app-version-support-and-update-requirements) [Personalized Subdomain URLs for Your Verkada Organization](https://help.verkada.com/command/organization-wide-settings/personalized-subdomain-urls-for-your-verkada-organization) [Buildings and Floors](https://help.verkada.com/command/organization-wide-settings/buildings-and-floors) [Feature Manager](https://help.verkada.com/command/organization-wide-settings/feature-manager) [Verkada Command API](https://help.verkada.com/command/organization-wide-settings/verkada-command-api) [Delete an Organization](https://help.verkada.com/command/organization-wide-settings/delete-an-organization) [Legacy Audit Logs](https://help.verkada.com/command/organization-wide-settings/legacy-audit-logs) [Manage Your Admin Page Settings](https://help.verkada.com/command/organization-wide-settings/manage-your-admin-page-settings) [Create a Floorplan](https://help.verkada.com/command/organization-wide-settings/create-a-floorplan) [Manage and View Audit Logs](https://help.verkada.com/command/organization-wide-settings/manage-and-view-audit-logs) Last updated 16 days ago Was this helpful? --- # Roles and Permissions for Guest | Guest | Verkada Help This article describes the set of roles and associated permissions for Verkada Guest. For more information on roles and permissions for other Verkada product lines, see [Roles and Permissions for Command](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) . * **Site-level roles** determine the access a user or group has to devices in the site. * **Org-level roles** allow users or groups to manage permissions and devices at a global level. * **Permissions** are set using roles, which define the level of access users and groups have to devices and settings within an organization and its sites. * * * ### [](https://help.verkada.com/guest/roles-and-permissions-for-guest#permissions-considerations) Permissions considerations * Subsites inherit permissions from all parent sites, including the ultimate parent. * Users can belong to multiple groups. When roles conflict, the user receives the **highest role** granted directly or through any group. * Group-assigned roles can be manually upgraded but not downgraded. Remove the user from the group with the higher role to downgrade their access. * * * [](https://help.verkada.com/guest/roles-and-permissions-for-guest#site-level-roles) Site-level roles --------------------------------------------------------------------------------------------------------- Site-level roles can be assigned to individual users or groups and are specific to a particular site. Subsites inherit the permissions from the parent sites above them. At a high level, these are the permissions granted to each Guest user: ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1436127735-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FZyuELZr7uIcXX3WnjX0N%252Fuploads%252Fgit-blob-1da0e5a6bae0e4466bcdc4703f3bc0230bdc52b9%252F6654bcf38f2ee2449738e300ec093aaca9dd4038.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=d02603be&sv=2) Site Viewer[](https://help.verkada.com/guest/roles-and-permissions-for-guest#site-viewer) * View guest logs and analytics. * Sign out users and print badges. * View and open doors (if the user has the appropriate [access control permissions](https://help.verkada.com/access-control/configuration-and-setup/assign-a-user-access-to-a-door) ). * View context camera footage (if the user has the appropriate [camera permissions](https://help.verkada.com/verkada-cameras/configuration-and-setup/roles-and-permissions-for-cameras) ). Site Admin[](https://help.verkada.com/guest/roles-and-permissions-for-guest#site-admin) * Manage employees from site-specific employee lists. * Edit site-specific Guest Settings. * Add/edit cameras (only if the user has at least a Live-Only Viewer role for Cameras). * Add/edit doors (only if the user is an [Access Site Admin](https://help.verkada.com/access-control/roles-and-permissions-for-access-control) ). * View guest logs and analytics. * Sign out users and print badges. * View and open doors (if the user has the appropriate [access control permissions](https://help.verkada.com/access-control/configuration-and-setup/assign-a-user-access-to-a-door) ). * View context camera footage (if the user has the appropriate [camera permissions](https://help.verkada.com/verkada-cameras/configuration-and-setup/roles-and-permissions-for-cameras) ). [](https://help.verkada.com/guest/roles-and-permissions-for-guest#org-level-roles) Org-level roles ------------------------------------------------------------------------------------------------------- Org Admin[](https://help.verkada.com/guest/roles-and-permissions-for-guest#org-admin) * Assign/remove Workplace Site Admin role. * Assign/remove Workplace Site Viewer role. * Import and modify sites. * Manage employees from site-specific and organization-level employee lists. * Edit site-specific and organization-level Guest Settings. * Add/edit cameras (if the user is at least a Live-Only Viewer for the cameras in the site). * Add/edit doors (only if the user is an [Access Site Admin](https://help.verkada.com/access-control/roles-and-permissions-for-access-control) ). * View guest logs and analytics. * Sign out users and print badges. * View and open doors (if the user has the appropriate [access control permissions](https://help.verkada.com/access-control/configuration-and-setup/assign-a-user-access-to-a-door) ). * View context camera footage (if the user has the appropriate [camera permissions](https://help.verkada.com/verkada-cameras/configuration-and-setup/roles-and-permissions-for-cameras) ). * * * [](https://help.verkada.com/guest/roles-and-permissions-for-guest#set-permissions) Set permissions ------------------------------------------------------------------------------------------------------- You can set site permissions for existing users and groups by managing user roles, groups, or sites. Users[](https://help.verkada.com/guest/roles-and-permissions-for-guest#users) In Verkada Command, go to All Products > Admin .Under Org Settings, select Users.Select a user.At the top right, click Manage Roles.a. Set the needed permissions. b. Click Save. Groups[](https://help.verkada.com/guest/roles-and-permissions-for-guest#groups) In Verkada Command, go to All Products > Admin .Under Org Settings, select Groups.Select a group.At the top, select Site Roles > Manage Roles.a. Set the needed permissions. b. Click Save. Sites[](https://help.verkada.com/guest/roles-and-permissions-for-guest#sites) In Verkada Command, go to All Products > Admin .In the left navigation, select Sites.Select a site to manage and in the right pane, click Manage .a. In the top right, click Add to add a new user or group. b. Select an existing user or group to edit their permissions. * * * [](https://help.verkada.com/guest/roles-and-permissions-for-guest#faq) FAQ ------------------------------------------------------------------------------- How do I grant Mailroom permissions but not Guest permissions, or vice versa?[](https://help.verkada.com/guest/roles-and-permissions-for-guest#how-do-i-grant-mailroom-permissions-but-not-guest-permissions-or-vice-versa) To separate these permissions, make your Mailroom site and Guest site different sites entirely. Guest and Mailroom sites that are imported from the same site will share roles given to users. Learn more about [Roles and Permissions for Mailroom](https://help.verkada.com/mailroom/roles-and-permissions-for-mailroom) . Can a Guest user get access to my cameras if they have "No Access" to the site in Command?[](https://help.verkada.com/guest/roles-and-permissions-for-guest#can-a-guest-user-get-access-to-my-cameras-if-they-have-no-access-to-the-site-in-command) Guest users must at least have the Live-Only Viewer role for the cameras in the site to view the camera feeds in Guest. What are the minimum permissions needed to see the Guest tab under All Products in Command?[](https://help.verkada.com/guest/roles-and-permissions-for-guest#what-are-the-minimum-permissions-needed-to-see-the-guest-tab-under-all-products-in-command) Users must be at least a Site Viewer for 1 site to see the Guest tab under **All Products**. What is the best role I should grant to my front desk receptionist?[](https://help.verkada.com/guest/roles-and-permissions-for-guest#what-is-the-best-role-i-should-grant-to-my-front-desk-receptionist) It depends on the specific permissions you want to grant. In most scenarios, receptionists only need to be Site Viewers. * * * **Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=byXR4aAmjfU) . Last updated 1 day ago Was this helpful? --- # Quick Reference Guide for Verkada Access Control | Access Control | Verkada Help [](https://help.verkada.com/access-control/quick-reference-guide-for-verkada-access-control#hardware-installation) Hardware installation --------------------------------------------------------------------------------------------------------------------------------------------- * [Access control datasheets](https://www.verkada.com/docs/?product=accessControl&contentType=datasheet) * [Access control setup guides](https://www.verkada.com/docs/?product=accessControl&contentType=setupGuide) * [Access Control Deployment Best Practices](https://help.verkada.com/access-control/hardware-installation/access-control-deployment-best-practices) * [Recommended Wires for Access Controllers](https://help.verkada.com/access-control/hardware-installation/recommended-wires-for-access-controllers) * [Wire a Door to a Verkada Access Controller](https://help.verkada.com/access-control/hardware-installation/wire-a-door-to-a-verkada-access-controller) [](https://help.verkada.com/access-control/quick-reference-guide-for-verkada-access-control#configuration-and-setup) Configuration and Setup ------------------------------------------------------------------------------------------------------------------------------------------------- * [Add an Access Controller to Command](https://help.verkada.com/access-control/configuration-and-setup/add-an-access-controller-to-command) * [Add a Door to an Access Controller](https://help.verkada.com/access-control/configuration-and-setup/add-a-door-to-an-access-controller) * [Configure a Door in Command](https://help.verkada.com/access-control/configuration-and-setup/configure-a-door-in-command) * [Add a User to the Verkada Access System](https://help.verkada.com/access-control/configuration-and-setup/add-a-user-to-the-verkada-access-system) * [Add and Modify Access Groups](https://help.verkada.com/access-control/configuration-and-setup/add-and-modify-access-groups) * [Add and Modify Access Levels](https://help.verkada.com/access-control/configuration-and-setup/add-and-modify-access-levels) * [Access Control Subsites](https://help.verkada.com/access-control/configuration-and-setup/access-control-subsites) * [Bluetooth Unlock](https://help.verkada.com/access-control/configuration-and-setup/bluetooth-unlock) * [Emergency Lockdown](https://help.verkada.com/access-control/configuration-and-setup/emergency-lockdown) [](https://help.verkada.com/access-control/quick-reference-guide-for-verkada-access-control#events-and-alerts) Events and Alerts ------------------------------------------------------------------------------------------------------------------------------------- * [Configure Access Control Event Alerts](https://help.verkada.com/access-control/alerts-and-events/configure-access-control-event-alerts) * [Manage Alerts Across Verkada Products](https://help.verkada.com/verkada-cameras/events-and-alerts/manage-alerts-across-verkada-products) [](https://help.verkada.com/access-control/quick-reference-guide-for-verkada-access-control#troubleshooting) Troubleshooting --------------------------------------------------------------------------------------------------------------------------------- * [Access Control Hardware Checks](https://help.verkada.com/access-control/troubleshooting/access-control-hardware-checks) * [Restart an Access Controller](https://help.verkada.com/access-control/troubleshooting/restart-an-access-controller) * [Troubleshoot an Immediate Door Relock](https://help.verkada.com/access-control/troubleshooting/troubleshoot-an-immediate-door-relock) * [Verkada Access Offline Operation](https://help.verkada.com/access-control/troubleshooting/verkada-access-offline-operation) Follow [our blog](https://www.verkada.com/blog/) for all our latest features and announcements! Last updated 1 day ago Was this helpful? --- # Sharing Video | Verkada Cameras | Verkada Help [Create Contacts and Manage Access](https://help.verkada.com/verkada-cameras/sharing-video/create-contacts-and-manage-access) [Share Archives](https://help.verkada.com/verkada-cameras/sharing-video/share-archives) [Share Multiple Cameras](https://help.verkada.com/verkada-cameras/sharing-video/share-multiple-cameras) [Share a Camera's Live Stream](https://help.verkada.com/verkada-cameras/sharing-video/share-a-cameras-live-stream) [Resize Embedded Video Streams](https://help.verkada.com/verkada-cameras/sharing-video/resize-embedded-video-streams) [Embed a Camera's Live Stream on a Website](https://help.verkada.com/verkada-cameras/sharing-video/embed-a-cameras-live-stream-on-a-website) Last updated 1 month ago Was this helpful? --- # Data Protection and Security | Command | Verkada Help [Data Storage & Processing Locations](https://help.verkada.com/command/data-protection-and-security/data-storage-processing-locations) [Passwordless authentication](https://help.verkada.com/command/data-protection-and-security/passwordless-authentication) [Passkeys for Login](https://help.verkada.com/command/data-protection-and-security/passkeys-for-login) [Session Management](https://help.verkada.com/command/data-protection-and-security/session-management) [Restricted Devices](https://help.verkada.com/command/data-protection-and-security/restricted-devices) [Privacy and Security Disclosure](https://help.verkada.com/command/data-protection-and-security/privacy-and-security-disclosure) [Privacy and Security Checklist](https://help.verkada.com/command/data-protection-and-security/privacy-and-security-checklist) [Verkada Bug Bounty Program](https://help.verkada.com/command/data-protection-and-security/verkada-bug-bounty-program) [Enable Data Sharing with Verkada](https://help.verkada.com/command/data-protection-and-security/enable-data-sharing-with-verkada) [Set a Default or Camera-Specific Location for Image and Video Data Storage and Processing](https://help.verkada.com/command/data-protection-and-security/set-a-default-or-camera-specific-location-for-image-and-video-data-storage-and-processing) Last updated 1 month ago Was this helpful? --- # Guest Network Settings | Guest | Verkada Help This article outlines the required network settings that your [Verkada Guest](https://docs.verkada.com/docs/verkada-guest-quick-start-guide.pdf) tablets and phones need to be able to communicate with the printer through the LAN and speak with [Verkada Command](https://help.verkada.com/command/get-started-with-verkada-command) . For more information on the required network settings for other Verkada product lines see [Required Network Settings](https://help.verkada.com/command/required-network-settings) . **Note**: Verkada devices are incompatible with LANs that require proxy servers or Secure Socket Layer (SSL)/Transport Layer Security (TLS) inspection. If either is in use, a bypass for all Verkada devices must be implemented for Verkada devices to communicate with Verkada Command. [](https://help.verkada.com/guest/guest-network-settings#ip-address) IP address ------------------------------------------------------------------------------------ Guest tablets and phones must be assigned an IPv4 address to communicate on the LAN and to Verkada Command. Guest devices use Dynamic Host Configuration Protocol (DHCP) and User Datagram Protocol (UDP) to obtain their IP addresses and network configurations. If you require your Guest device to have a specific IP address, create a DHCP reservation using the device’s Media Access Control (MAC) address (found on the device’s label). [](https://help.verkada.com/guest/guest-network-settings#domain-name-system) Domain Name System ---------------------------------------------------------------------------------------------------- Guest tablets and phones use the DNS server to resolve Verkada’s fully qualified domain names (FQDN) to IP addresses to communicate with them. Your DHCP server tells the Guest device where the DNS server is on the network and the Guest device communicates using UDP port 53. **Note**: DNS over HTTPS (DoH) is currently not supported. [](https://help.verkada.com/guest/guest-network-settings#firewall-settings) Firewall settings -------------------------------------------------------------------------------------------------- Guest tablets and phones require access to many endpoints to ensure they can communicate with Command and all features will be accessible. Many customers may want to allow the Guest devices to communicate with the general required endpoints. These are the general domains to allow, **applicable for all organization-regions**: Copy 34.216.15.26 - UDP/123 34.203.250.0/23 - UDP/10000-20000 35.156.191.128/25 - UDP/10000-20000 52.215.127.0/24 - UDP/10000-20000 54.65.63.192/26 - UDP/10000-20000 54.169.127.128/26 - UDP/10000-20000 54.171.127.192/26 - UDP/10000-20000 54.172.60.0/23 - UDP/10000-20000 54.244.51.0/24 - UDP/1024-65535 168.86.128.0/18 - UDP/10000 - 60000 54.252.254.64/26 - UDP/10000-20000 177.71.206.192/26 - UDP/10000-20000 *.verkada.com - UDP/123 + TCP+UDP/443 If you prefer a more granular allowlist, you can add IP addresses, full FQDNs, and wildcard domains to your firewall rules based on the region where your devices are located. Your region is selected when you [create an organization](https://help.verkada.com/command/get-started-with-verkada-command) in Command. ### [](https://help.verkada.com/guest/guest-network-settings#region-united-states) **Region: United States** Copy 34.216.15.26 - UDP/123 3.235.111.128/25 - UDP/10000-60000 + TCP+UDP/443 + UDP/3478 34.203.250.0/23 - UDP/10000-60000 + TCP+UDP/443 + UDP/3478 34.203.254.0/24 - UDP/10000-60000 + TCP+UDP/443 + UDP/3478 34.216.110.128/27 - UDP/10000-60000 + TCP+UDP/443 + UDP/3478 35.156.191.128/25 - UDP/10000-20000 44.234.69.0/25 - UDP/10000-60000 + TCP+UDP/443 + UDP/3478 52.215.127.0/24 - UDP/10000-20000 54.65.63.192/26 - UDP/10000-20000 54.169.127.128/26 - UDP/10000-20000 54.171.127.192/26 - UDP/10000-20000 54.172.60.0/23 - UDP/10000-60000 + TCP+UDP/443 + UDP/3478 54.244.51.0/24 - UDP/10000-60000 + TCP+UDP/443 + UDP/3478 168.86.128.0/18 - UDP/10000 - 60000 54.252.254.64/26 - UDP/10000-20000 177.71.206.192/26 - UDP/10000-20000 vdoorman.command.verkada.com - TCP/443 vdoormansocket.command.verkada.com -TCP/443 vdoorman.prod1.command.verkada.com - TCP/443 verkada-guest-management-public-us-west-2-prod1.s3.amazonaws.com TCP/443 verkada-guest-management-us-west-2-prod1.s3.amazonaws.com TCP/443 verkada-guest-management-customer-upload-files-us-west-2-prod1.s3.amazonaws.com - TCP/443 baltazar.microblink.com - TCP/443 ping.microblink.com - TCP/443 us1.vss.twilio.com - TCP/443 us2.vss.twilio.com - TCP/443 *.twilio.com - TCP+UDP/443 + UDP/3478 *.twiliocdn.com - TCP+UDP/443 + UDP/3478 sdkgw.us1.twilio.com - TCP/443 ### [](https://help.verkada.com/guest/guest-network-settings#region-europe) **Region: Europe** Copy 34.216.15.26 - UDP/123 34.203.250.0/23 - UDP/10000-20000 35.156.191.128/25 - UDP/10000-20000 52.215.127.0/24 - UDP/10000-20000 54.65.63.192/26 - UDP/10000-20000 54.169.127.128/26 - UDP/10000-20000 54.171.127.192/26 - UDP/10000-20000 54.172.60.0/23 - UDP/10000-20000 54.244.51.0/24 - UDP/1024-65535 54.252.254.64/26 - UDP/10000-20000 177.71.206.192/26 - UDP/10000-20000 vdoorman.command.verkada.com - TCP/443 vdoormansocket.command.verkada.com -TCP/443 vdoorman.prod2.command.verkada.com - TCP/443 verkada-guest-management-public-us-west-2-prod2.s3.amazonaws.com TCP/443 verkada-guest-management-us-west-2-prod2.s3.amazonaws.com TCP/443 verkada-guest-management-customer-upload-files-us-west-2-prod2.s3.amazonaws.com - TCP/443 ### [](https://help.verkada.com/guest/guest-network-settings#region-australia) **Region: Australia** Copy 34.216.15.26 - UDP/123 34.203.250.0/23 - UDP/10000-20000 35.156.191.128/25 - UDP/10000-20000 52.215.127.0/24 - UDP/10000-20000 54.65.63.192/26 - UDP/10000-20000 54.169.127.128/26 - UDP/10000-20000 54.171.127.192/26 - UDP/10000-20000 54.172.60.0/23 - UDP/10000-20000 54.244.51.0/24 - UDP/1024-65535 168.86.128.0/18 - UDP/10000 - 60000 54.252.254.64/26 - UDP/10000-20000 177.71.206.192/26 - UDP/10000-20000 vdoormansocket.command.verkada.com -TCP/443 vdoorman.command.verkada.com - TCP/443 vdoorman.prod-ap-syd.command.verkada.com - TCP/443 verkada-guest-management-public-us-west-2-prod-ap-syd.s3.amazonaws.com - TCP/443 verkada-guest-management-us-west-2-prod-ap-syd.s3.amazonaws.com - TCP/443 verkada-guest-management-customer-upload-files-us-west-2-prod-ap-syd.s3.amazonaws.com - TCP/443 Use the [Verkada Network Tester](https://network-tester.support.verkada.com/) to verify your devices can connect to Verkada Command. Select your region and the **Guest** product type to run the check. The following endpoints must be allowed on your network for the test to work: * speed.cloudflare.com * network-tester.support.verkada.com Last updated 22 hours ago Was this helpful? --- # Hardware Installation | Verkada Cameras | Verkada Help [Camera Mount Matrix](https://help.verkada.com/verkada-cameras/hardware-installation/camera-mount-matrix) ### [](https://help.verkada.com/verkada-cameras/hardware-installation#advanced-installation) Advanced Installation [Use Handheld Controllers with the PTZ](https://help.verkada.com/verkada-cameras/hardware-installation/advanced-installation/use-handheld-controllers-with-the-ptz) [Configure Static IP Addresses for Cameras](https://help.verkada.com/verkada-cameras/hardware-installation/advanced-installation/configure-static-ip-addresses-for-cameras) [Enterprise Bandwidth Manager](https://help.verkada.com/verkada-cameras/hardware-installation/advanced-installation/enterprise-bandwidth-manager) [Disconnect and Reconnect the CM41-S Video Cable](https://help.verkada.com/verkada-cameras/hardware-installation/advanced-installation/disconnect-and-reconnect-the-cm41-s-video-cable) [Set Up Verkada with ZScaler](https://help.verkada.com/verkada-cameras/hardware-installation/advanced-installation/set-up-verkada-with-zscaler) [Use External IR Illuminators with Verkada Cameras](https://help.verkada.com/verkada-cameras/hardware-installation/advanced-installation/use-external-ir-illuminators-with-verkada-cameras) [Use Verkada Cameras over Fiber](https://help.verkada.com/verkada-cameras/hardware-installation/advanced-installation/use-verkada-cameras-over-fiber) [Connect a Verkada Camera Using a Wi-Fi Bridge](https://help.verkada.com/verkada-cameras/hardware-installation/advanced-installation/connect-a-verkada-camera-using-a-wi-fi-bridge) [Connect a Verkada Camera via a Wireless Bridge/Point-to-Point Connection](https://help.verkada.com/verkada-cameras/hardware-installation/advanced-installation/connect-a-verkada-camera-via-a-wireless-bridgepoint-to-point-connection) [Power a Verkada Camera with a Solar Panel](https://help.verkada.com/verkada-cameras/hardware-installation/advanced-installation/power-a-verkada-camera-with-a-solar-panel) [Power a Verkada Camera over Coax](https://help.verkada.com/verkada-cameras/hardware-installation/advanced-installation/power-a-verkada-camera-over-coax) [Use a Camera on a Cradlepoint Connection](https://help.verkada.com/verkada-cameras/hardware-installation/advanced-installation/use-a-camera-on-a-cradlepoint-connection) Last updated 1 month ago Was this helpful? --- # Historical Playback | Verkada Cameras | Verkada Help [History Player Search and Unified Timeline](https://help.verkada.com/verkada-cameras/historical-playback/history-player-search-and-unified-timeline) [Authenticate Verkada Video Footage](https://help.verkada.com/verkada-cameras/historical-playback/authenticate-verkada-video-footage) [Extended Cloud Backup Licensing](https://help.verkada.com/verkada-cameras/historical-playback/extended-cloud-backup-licensing) [View Historical Footage](https://help.verkada.com/verkada-cameras/historical-playback/view-historical-footage) [Take a Screenshot of Video Feed](https://help.verkada.com/verkada-cameras/historical-playback/take-a-screenshot-of-video-feed) [Use the Timelapse Feature](https://help.verkada.com/verkada-cameras/historical-playback/use-the-timelapse-feature) [Add Cameras to a Multicamera View](https://help.verkada.com/verkada-cameras/historical-playback/add-cameras-to-a-multicamera-view) [Cloud Backup](https://help.verkada.com/verkada-cameras/historical-playback/cloud-backup) [Enable and Listen to Audio](https://help.verkada.com/verkada-cameras/historical-playback/enable-and-listen-to-audio) [Archive Recorded Video Footage](https://help.verkada.com/verkada-cameras/historical-playback/archive-recorded-video-footage) [Common Storage Questions](https://help.verkada.com/verkada-cameras/historical-playback/common-storage-questions) Last updated 1 month ago Was this helpful? --- # Licensing and Warranty | Command | Verkada Help [License Groups](https://help.verkada.com/command/licensing-and-warranty/license-groups) [Delete Unused Devices and Products](https://help.verkada.com/command/licensing-and-warranty/delete-unused-devices-and-products) [Calculate License Expiration Date](https://help.verkada.com/command/licensing-and-warranty/calculate-license-expiration-date) [Find and Add License Keys to Command](https://help.verkada.com/command/licensing-and-warranty/find-and-add-license-keys-to-command) [Manage Your Licenses](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses) [Verkada Product Warranty](https://help.verkada.com/command/licensing-and-warranty/verkada-product-warranty) Last updated 1 month ago Was this helpful? --- # Intercom Network Settings | Intercom | Verkada Help This article outlines the required network settings that your Verkada [Intercom](https://docs.verkada.com/docs/video-intercom-overview.pdf) needs to communicate with [Verkada Command](https://help.verkada.com/command/get-started-with-verkada-command) . For more information on the required network settings for other Verkada product lines see [Required Network Settings](https://help.verkada.com/command/required-network-settings) . Verkada devices are incompatible with LANs that require proxy servers or Secure Socket Layer (SSL)/Transport Layer Security (TLS) inspection. If either is in use, a bypass for all Verkada devices must be implemented for Verkada devices to communicate with Verkada Command. [](https://help.verkada.com/intercom/intercom-network-settings#status-led) Status LED ------------------------------------------------------------------------------------------ A flashing blue [status LED](https://help.verkada.com/intercom/configuration-and-setup/td52-status-leds) on the top of the intercom indicates the intercom is not communicating with Command. If you see this behavior, check that the network is set up correctly with the intercom’s requirements. If the problem persists, contact [Verkada Support](https://help.verkada.com/command/need-help/contact-verkada-support) . [](https://help.verkada.com/intercom/intercom-network-settings#ip-address) IP address ------------------------------------------------------------------------------------------ Intercoms must be assigned an IPv4 address to communicate on the LAN and to Verkada Command. Intercoms use Dynamic Host Configuration Protocol (DHCP) and User Datagram Protocol (UDP) to obtain their IP addresses and network configurations. If you require your intercom to have a specific IP address, create a DHCP reservation using the device’s Media Access Control (MAC) address (found on the device’s label). Verkada intercoms respond to ICMP ping requests. [](https://help.verkada.com/intercom/intercom-network-settings#domain-name-system) Domain Name System ---------------------------------------------------------------------------------------------------------- Intercoms use the DNS server to resolve Verkada’s fully qualified domain names (FQDN) to IP addresses to communicate with them. Your DHCP server tells the intercom where the DNS server is on the network and the intercom communicates using UDP port 53. DNS over HTTPS (DoH) is currently not supported. [](https://help.verkada.com/intercom/intercom-network-settings#power) Power -------------------------------------------------------------------------------- Intercoms are powered through Power over Ethernet (PoE). This means the network switch needs to provide power to the intercom, or a PoE injector needs to be utilized. For specifics on power requirements, see the [Intercom datasheet](https://docs.verkada.com/docs/video-intercom-overview.pdf) . [](https://help.verkada.com/intercom/intercom-network-settings#firewall-settings) Firewall settings -------------------------------------------------------------------------------------------------------- Intercoms require access to many endpoints to ensure they can communicate with Command and all features will be accessible. Many customers may want to allow the intercoms to communicate with the general required endpoints. These are the general domains to allow, **applicable for all organization-regions**: **Mandatory:** Copy *.amazonaws.com - TCP+UDP/443, UDP/1024 to 65535 *.twilio.com - TCP+UDP/443, 5060, 5061 *.verkada.com - TCP+UDP/443, UDP/123 *:4100 - TCP/UDP on LAN 34.216.15.26 - UDP/123 35.166.49.153 - TCP+UDP/443, UDP/123 168.86.128.0/18 - UDP/1024 to 65535 time.cloudflare.com - TCP/4460 + UDP/123 *.livekit.cloud - TCP/443, UDP/50000 to 60000 *.turn.livekit.cloud - TCP/443, UDP/50000 to 60000 *.host.livekit.cloud - UDP/3478, UDP/50000 to 60000 LiveKit enables high quality, low latency video and audio streaming with Verkada intercoms. If you prefer a more granular allowlist, you can add IP addresses, full FQDNs, and wildcard domains to your firewall rules based on the region where your devices are located. Your region is selected when you [create an organization](https://help.verkada.com/command/get-started-with-verkada-command) in Command. United States Europe Australia **Standard Verkada Endpoints** Copy api.control.verkada.com - TCP+UDP/443 api.global-prod.control.verkada.com - TCP+UDP/443 api-ga.control.verkada.com - TCP+UDP 443 device.pyramid.verkada.com - TCP+UDP/443 firmware.control.verkada.com - TCP+UDP/443 update.control.verkada.com - TCP+UDP/443 user.pyramid.verkada.com - TCP+UDP/443 vconductor.global-prod.command.verkada.com - TCP+UDP/443 **NTP Endpoints** Copy 34.216.15.26 - UDP/123 35.166.49.153 - UDP/123 + TCP+UDP/443 time.control.verkada.com - UDP/123 time.cloudflare.com - TCP/4460 time.cloudflare.com - UDP/123 **Streaming Endpoints** Copy *:4100 - TCP/UDP on LAN (only required for local streaming) *.us-west-2.compute.amazonaws.com UDP/1024 to 65535 (webRTC) index.control.verkada.com - TCP+UDP/443 relay.control.verkada.com - TCP+UDP/443 relay.global-prod.control.verkada.com - TCP+UDP/443 **Calling Endpoints** Copy 143.223.88.0/21 — TCP/443, TCP/7881, UDP/3478, UDP/50000-60000 161.115.160.0/19 — TCP/443, TCP/7881, UDP/3478, UDP/50000-60000 168.86.128.0/18 - UDP 1024 to 65535 chunderm.gll.twilio.com - TCP 443† ers.twilio.com - TCP 443† eventgw.twilio.com - TCP 443† verkada-erik-sip.sip.twilio.com - TCP+UDP 5060, 5061 verkada-erik-sip.sip.us1.twilio.com - TCP+UDP 5060, 5061 verkada.sip.us1.twilio.com - TCP+UDP 5060, 5061 verkada-vinter-audio-files-prod1.s3.amazonaws.com - TCP+UDP 443 **Access Control Endpoints** Copy access.control.verkada.com - TCP+UDP/443 vcerberus.command.verkada.com - TCP+UDP/443 **Cloud Backup Endpoints** Copy s3.ap-southeast-2.amazonaws.com - TCP/443‡ s3.ca-central-1.amazonaws.com - TCP/443‡ s3.us-west-2.amazonaws.com - TCP/443‡ **Desk Station Endpoints** Copy 17.249.0.0/16 17.252.0.0/16 17.57.144.0/22 17.188.128.0/18 17.188.20.0/23 **Standard Verkada Endpoints** Copy api.global-prod.control.verkada.com - TCP+UDP/443 api.prod2.control.verkada.com - TCP+UDP/443 api-ga.control.verkada.com - TCP+UDP 443 update.control.verkada.com - TCP+UDP/443 vconductor.global-prod.command.verkada.com - TCP+UDP/443 vconductor.prod2.command.verkada.com - TCP+UDP/443 **NTP Endpoints** Copy 35.166.49.153 - UDP/123 + TCP+UDP/443 time.control.verkada.com - UDP/123 time.cloudflare.com - TCP/4460 time.cloudflare.com - UDP/123 **Streaming Endpoints** Copy *:4100 - TCP/UDP on LAN (only required for local streaming) *.eu-west-1.compute.amazonaws.com UDP/1024 to 65535 (webRTC) index.prod2.control.verkada.com - TCP+UDP/443 relay.global-prod.control.verkada.com - TCP+UDP/443 relay.prod2.control.verkada.com - TCP+UDP/443 **Calling Endpoints** Copy 168.86.128.0/18 - UDP 1024 to 65535 chunderm.gll.twilio.com - TCP 443† ers.twilio.com - TCP 443† eventgw.twilio.com - TCP 443† verkada-prod2.sip.twilio.com - TCP+UDP 5060, 5061 verkada-prod2.sip.us1.twilio.com - TCP+UDP 5060, 5061 verkada-vinter-audio-files-prod2.s3.amazonaws.com - TCP+UDP 443 LiveKit Full FQDNs[](https://help.verkada.com/intercom/intercom-network-settings#livekit-full-fqdns) Copy verkada-intercom-prod2-wrhsid3a.dblr1a.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.dblr1b.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.dfra1a.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.dfra1b.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.dsfo3a.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.dsfo3b.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.dsgp1a.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.dsgp1b.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.dsyd1a.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.dsyd1b.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.oashburn1a.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.oashburn1b.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.ochicago1a.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.ochicago1b.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.odubai1a.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.odubai1b.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.ojohannesburg1a.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.ojohannesburg1b.production.livekit.cloud-TCP/44 verkada-intercom-prod2-wrhsid3a.olondon1a.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.olondon1b.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.omarseille1a.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.omarseille1b.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.osaopaulo1a.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.osaopaulo1b.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.osingapore1a.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.osingapore1b.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.ophoenix1a.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.ophoenix1b.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.otokyo1a.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.otokyo1b.production.livekit.cloud-TCP/443 verkada-intercom-prod2-wrhsid3a.sfo3.production.livekit.cloud-TCP/443 dblr1a.turn.livekit.cloud-TCP/443 dblr1b.turn.livekit.cloud-TCP/443 dfra1a.turn.livekit.cloud-TCP/443 dfra1b.turn.livekit.cloud-TCP/443 dsfo3a.turn.livekit.cloud-TCP/443 dsfo3b.turn.livekit.cloud-TCP/443 dsgp1a.turn.livekit.cloud-TCP/443 dsgp1b.turn.livekit.cloud-TCP/443 dsyd1a.turn.livekit.cloud-TCP/443 dsyd1b.turn.livekit.cloud-TCP/443 oashburn1a.turn.livekit.cloud-TCP/443 oashburn1b.turn.livekit.cloud-TCP/443 ochicago1a.turn.livekit.cloud-TCP/443 ochicago1b.turn.livekit.cloud-TCP/443 odubai1a.turn.livekit.cloud-TCP/443 odubai1b.turn.livekit.cloud-TCP/443 ojohannesburg1a.turn.livekit.cloud-TCP/443 ojohannesburg1b.turn.livekit.cloud-TCP/443 olondon1a.turn.livekit.cloud-TCP/443 olondon1b.turn.livekit.cloud-TCP/443 omarseille1a.turn.livekit.cloud-TCP/443 omarseille1b.turn.livekit.cloud-TCP/443 ophoenix1a.turn.livekit.cloud-TCP/443 ophoenix1b.turn.livekit.cloud-TCP/443 osaopaulo1a.turn.livekit.cloud-TCP/443 osaopaulo1b.turn.livekit.cloud-TCP/443 osingapore1a.turn.livekit.cloud-TCP/443 osingapore1b.turn.livekit.cloud-TCP/443 otokyo1a.turn.livekit.cloud-TCP/443 otokyo1b.turn.livekit.cloud-TCP/443 sfo3.turn.livekit.cloud-TCP/443 **Access Control Endpoints** Copy access.prod2.command.verkada.com - TCP+UDP/443 vcerberus.command.verkada.com - TCP+UDP/443 **Cloud Backup Endpoints** Copy s3.eu-west-1.amazonaws.com - TCP/443‡ **Desk Station Endpoints** Copy 17.249.0.0/16 17.252.0.0/16 17.57.144.0/22 17.188.128.0/18 17.188.20.0/23 **Standard Verkada Endpoints** Copy api.global-prod.control.verkada.com - TCP+UDP/443 api.prod-ap-syd.control.verkada.com - TCP+UDP/443 api-ga.control.verkada.com - TCP+UDP 443 update.control.verkada.com - TCP+UDP/443 vconductor.global-prod.command.verkada.com - TCP+UDP/443 vconductor.prod-ap-syd.command.verkada.com - TCP+UDP/443 **NTP Endpoints** Copy 35.166.49.153 - UDP/123 + TCP+UDP/443 time.control.verkada.com - UDP/123 time.cloudflare.com - TCP/4460 time.cloudflare.com - UDP/123 **Streaming Endpoints** Copy *:4100 - TCP/UDP on LAN (only required for local streaming) *.eu-west-1.compute.amazonaws.com - UDP/1024 to 65535(webRTC) index.prod-ap-syd.control.verkada.com - TCP+UDP/443 relay.global-prod.control.verkada.com - TCP+UDP/443 relay.prod-ap-syd.control.verkada.com - TCP+UDP/443 **Calling Endpoints** Copy 168.86.128.0/18 - UDP 1024 to 65535 chunderm.gll.twilio.com - TCP 443† ers.twilio.com - TCP 443† eventgw.twilio.com - TCP 443† verkada-prod-ap-syd.sip.twilio.com - TCP+UDP 5060, 5061 verkada-prod-ap-syd.sip.us1.twilio.com - TCP+UDP 5060, 5061 verkada-vinter-audio-files-prod-ap-syd.s3.amazonaws.com - TCP+UDP 443 LiveKit Full FQDNs[](https://help.verkada.com/intercom/intercom-network-settings#livekit-full-fqdns-1) Copy verkada-intercom-prod-ap-syd-7tmwkpxi.dblr1a.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.dblr1b.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.dfra1a.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.dfra1b.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.dsfo3a.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.dsfo3b.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.dsgp1a.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.dsgp1b.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.dsyd1a.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.dsyd1b.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.oashburn1a.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.oashburn1b.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.ochicago1a.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.ochicago1b.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.odubai1a.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.odubai1b.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.ojohannesburg1a.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.ojohannesburg1b.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.olondon1a.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.olondon1b.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.omarseille1a.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.omarseille1b.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.osaopaulo1a.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.osaopaulo1b.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.osingapore1a.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.osingapore1b.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.ophoenix1a.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.ophoenix1b.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.otokyo1a.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.otokyo1b.production.livekit.cloud-TCP/443 verkada-intercom-prod-ap-syd-7tmwkpxi.sfo3.production.livekit.cloud-TCP/443 dblr1a.turn.livekit.cloud-TCP/443 dblr1b.turn.livekit.cloud-TCP/443 dfra1a.turn.livekit.cloud-TCP/443 dfra1b.turn.livekit.cloud-TCP/443 dsfo3a.turn.livekit.cloud-TCP/443 dsfo3b.turn.livekit.cloud-TCP/443 dsgp1a.turn.livekit.cloud-TCP/443 dsgp1b.turn.livekit.cloud-TCP/443 dsyd1a.turn.livekit.cloud-TCP/443 dsyd1b.turn.livekit.cloud-TCP/443 oashburn1a.turn.livekit.cloud-TCP/443 oashburn1b.turn.livekit.cloud-TCP/443 ochicago1a.turn.livekit.cloud-TCP/443 ochicago1b.turn.livekit.cloud-TCP/443 odubai1a.turn.livekit.cloud-TCP/443 odubai1b.turn.livekit.cloud-TCP/443 ojohannesburg1a.turn.livekit.cloud-TCP/443 ojohannesburg1b.turn.livekit.cloud-TCP/443 olondon1a.turn.livekit.cloud-TCP/443 olondon1b.turn.livekit.cloud-TCP/443 omarseille1a.turn.livekit.cloud-TCP/443 omarseille1b.turn.livekit.cloud-TCP/443 ophoenix1a.turn.livekit.cloud-TCP/443 ophoenix1b.turn.livekit.cloud-TCP/443 osaopaulo1a.turn.livekit.cloud-TCP/443 osaopaulo1b.turn.livekit.cloud-TCP/443 osingapore1a.turn.livekit.cloud-TCP/443 osingapore1b.turn.livekit.cloud-TCP/443 otokyo1a.turn.livekit.cloud-TCP/443 otokyo1b.turn.livekit.cloud-TCP/443 sfo3.turn.livekit.cloud-TCP/443 **Access Control Endpoints** Copy access.prod-ap-syd.command.verkada.com - TCP+UDP/443 vcerberus.command.verkada.com - TCP+UDP/443 **Cloud Backup Endpoints** Copy s3.eu-west-1.amazonaws.com - TCP/443‡ **Desk Station Endpoints** Copy 17.249.0.0/16 17.252.0.0/16 17.57.144.0/22 17.188.128.0/18 17.188.20.0/23 **Footnotes**: †required for Desk Stations and Verkada Pass ‡required for cloud backup Use the [Verkada Network Tester](https://network-tester.support.verkada.com/) to verify your devices can connect to Verkada Command. Select your region and the **Intercom** product type to run the check. The following endpoints must be allowed on your network for the test to work: * speed.cloudflare.com * network-tester.support.verkada.com **Revisions** September 2024: * Added LiveKit endpoints for high-quality video and audio streams. Last updated 0 minutes ago Was this helpful? --- # Camera Specifications | Verkada Cameras | Verkada Help [Camera Network Settings](https://help.verkada.com/verkada-cameras/camera-specifications/camera-network-settings) [Variable Bitrates for PTZ Cameras](https://help.verkada.com/verkada-cameras/camera-specifications/variable-bitrates-for-ptz-cameras) [Camera Power Requirements](https://help.verkada.com/verkada-cameras/camera-specifications/camera-power-requirements) [Camera Environmental Ratings—IK and IP](https://help.verkada.com/verkada-cameras/camera-specifications/camera-environmental-ratingsik-and-ip) [Camera Stats](https://help.verkada.com/verkada-cameras/camera-specifications/camera-stats) [Camera LED Status Indicators](https://help.verkada.com/verkada-cameras/camera-specifications/camera-led-status-indicators) [Camera Video Resolution](https://help.verkada.com/verkada-cameras/camera-specifications/camera-video-resolution) [Bandwidth Consumption & Uplink Requirements for Video](https://help.verkada.com/verkada-cameras/camera-specifications/bandwidth-consumption-uplink-requirements-for-video) Last updated 1 month ago Was this helpful? --- # Live Streaming | Verkada Cameras | Verkada Help [Grids](https://help.verkada.com/verkada-cameras/live-streaming/grids) [Modify High Quality Video Bitrates](https://help.verkada.com/verkada-cameras/live-streaming/modify-high-quality-video-bitrates) [Camera High Efficiency Video Encoding (HEVC)](https://help.verkada.com/verkada-cameras/live-streaming/camera-high-efficiency-video-encoding-hevc) [Live Viewers](https://help.verkada.com/verkada-cameras/live-streaming/live-viewers) [Low-Latency RTSP Streaming](https://help.verkada.com/verkada-cameras/live-streaming/low-latency-rtsp-streaming) [Change Fisheye View Modes](https://help.verkada.com/verkada-cameras/live-streaming/change-fisheye-view-modes) [Local Streaming on Verkada Cameras](https://help.verkada.com/verkada-cameras/live-streaming/local-streaming-on-verkada-cameras) [Manage Camera Video Quality](https://help.verkada.com/verkada-cameras/live-streaming/manage-camera-video-quality) [Cuadrículas](https://help.verkada.com/verkada-cameras/live-streaming/cuadriculas) [Digital Zoom](https://help.verkada.com/verkada-cameras/live-streaming/digital-zoom) Last updated 1 month ago Was this helpful? --- # Required Network Settings | Command | Verkada Help Verkada devices need to communicate with [Verkada Command](https://help.verkada.com/command/get-started-with-verkada-command) , and they use the network they are connected to to do this. In most cases, minimal updates to your network settings are needed. Additional configuration may be required for complex or highly secure networks. Use the [Verkada Network Tester](https://network-tester.support.verkada.com/) to verify your devices can connect to Verkada Command. Select your region and product type to run the check. The following endpoints must be allowed on your network for the test to work: * speed.cloudflare.com * network-tester.support.verkada.com * * * [](https://help.verkada.com/command/required-network-settings#device-specific-network-settings) Device-specific network settings ------------------------------------------------------------------------------------------------------------------------------------- Each device type has required domains to allow them to properly operate on the network. Select a product from the list below for more information on its required network settings. * [Access Control Network Settings](https://help.verkada.com/access-control/access-control-network-settings) * [Air Quality Sensor Network Settings](https://help.verkada.com/air-quality/air-quality-sensor-network-settings) * [Alarms Network Settings](https://help.verkada.com/new-alarms/alarms-specifications/alarms-network-settings) * [Camera Network Settings](https://help.verkada.com/verkada-cameras/camera-specifications/camera-network-settings) * [Classic Alarms Network Settings](https://help.verkada.com/classic-alarms/classic-alarms-network-settings) * [Command Connector Network Settings](https://help.verkada.com/command-connector/command-connector-network-settings) * [Gateway Network Settings](https://help.verkada.com/connectivity/gateways-network-settings) * [Guest Network Settings](https://help.verkada.com/guest/guest-network-settings) * [Intercom Network Settings](https://help.verkada.com/intercom/intercom-network-settings) * [Mailroom Network Settings](https://help.verkada.com/mailroom/mailroom-network-settings) * [Viewing Station Network Settings](https://help.verkada.com/viewing-station/viewing-station-network-settings) Some firewalls do not allow wildcards (\*), so you may need to allow each endpoint individually. [](https://help.verkada.com/command/required-network-settings#compatibility) Compatibility ----------------------------------------------------------------------------------------------- Verkada devices are incompatible with local area networks (LANs) that require proxy servers or Secure Socket Layer (SSL)/Transport Layer Security (TLS) inspection. If either is in use, a bypass for all Verkada devices must be implemented for your Verkada devices to communicate with Verkada Command. [](https://help.verkada.com/command/required-network-settings#ip-address) IP address ----------------------------------------------------------------------------------------- Verkada devices must be assigned an IPv4 address to communicate on the LAN and to Verkada Command through the internet. By default, all Verkada devices use Dynamic Host Configuration Protocol (DHCP) and User Datagram Protocol (UDP) to obtain their IP addresses and network configurations. If you require your device to have a specific IP address, create a DHCP reservation using the device’s Media Access Control (MAC) address (found on the device’s label). You can also set up [static IP addresses](https://help.verkada.com/verkada-cameras/hardware-installation/advanced-installation/configure-static-ip-addresses-for-cameras) in Command for cameras. [](https://help.verkada.com/command/required-network-settings#domain-name-system) Domain Name System --------------------------------------------------------------------------------------------------------- Verkada devices use the Domain Name System (DNS) server to resolve Verkada’s fully qualified domain names (FQDN) to IP addresses to communicate with them. Your DHCP server tells the Verkada device where the DNS server is on the network and the device communicates using UDP port 53. **Note**: DNS over HTTPS (DoH) is currently not supported. [](https://help.verkada.com/command/required-network-settings#power) Power ------------------------------------------------------------------------------- Most Verkada devices are powered through Power over Ethernet (PoE). You can use the product [datasheets](https://www.verkada.com/docs/?contentType=datasheet) to figure out the power requirements for your Verkada devices. These are the most common power requirements: * IEE 802.3af, Type 1 PoE * IEEE 802.3at, Type 2 PoE+ * IEEE 802.3bt, Type 3 PoE++ * 100–240 VAC, 50/60 Hz Last updated 1 day ago Was this helpful? --- # Integrations | Command | Verkada Help [Set up Verkada Alerts for Slack](https://help.verkada.com/command/integrations/set-up-verkada-alerts-for-slack) [Set up Verkada Alerts for Microsoft Teams](https://help.verkada.com/command/integrations/set-up-verkada-alerts-for-microsoft-teams) [Set up the Verkada + Fusus camera integration](https://help.verkada.com/command/integrations/set-up-the-verkada-fusus-camera-integration) [Set up the Verkada + Fusus LPR Integration](https://help.verkada.com/command/integrations/set-up-the-verkada-fusus-lpr-integration) [Set up the Axon Evidence integration in Command](https://help.verkada.com/command/integrations/set-up-the-axon-evidence-integration-in-command) [Set up the Verkada + HiveWatch Integration](https://help.verkada.com/command/integrations/set-up-the-verkada-hivewatch-integration) [Set up the Auror integration in Command](https://help.verkada.com/command/integrations/set-up-the-auror-integration-in-command) [Initiate InformaCast Notifications with Verkada Device Alerts](https://help.verkada.com/command/integrations/initiate-informacast-notifications-with-verkada-device-alerts) Last updated 1 month ago Was this helpful? --- # Need Help? | Command | Verkada Help [Locate Customer ID](https://help.verkada.com/command/need-help/locate-customer-id) [Verkada Splunk Integration](https://help.verkada.com/command/need-help/verkada-splunk-integration) [Enable Support Access](https://help.verkada.com/command/need-help/enable-support-access) [Clear Your Browser Cache](https://help.verkada.com/command/need-help/clear-your-browser-cache) [Contact Verkada Support](https://help.verkada.com/command/need-help/contact-verkada-support) [Network Port Speeds](https://help.verkada.com/command/need-help/network-port-speeds) Last updated 1 month ago Was this helpful? --- # Maintenance for Your Camera | Verkada Cameras | Verkada Help [Verkada Dome Camera Maintenance](https://help.verkada.com/verkada-cameras/maintenance-for-your-camera/verkada-dome-camera-maintenance) [Clean Your Verkada Dome Camera](https://help.verkada.com/verkada-cameras/maintenance-for-your-camera/clean-your-verkada-dome-camera) [Waterproof Outdoor Cameras](https://help.verkada.com/verkada-cameras/maintenance-for-your-camera/waterproof-outdoor-cameras) Last updated 1 month ago Was this helpful? --- # Configuration and Setup | Intercom | Verkada Help [Two-Person Unlock](https://help.verkada.com/intercom/configuration-and-setup/two-person-unlock) [Pair Intercoms with Viewing Station](https://help.verkada.com/intercom/configuration-and-setup/pair-intercoms-with-viewing-station) [Boost Volume with Intercom Audio Overdrive](https://help.verkada.com/intercom/configuration-and-setup/boost-volume-with-intercom-audio-overdrive) [Grant Temporary Access with Visit Keys](https://help.verkada.com/intercom/configuration-and-setup/grant-temporary-access-with-visit-keys) [Set up TD63 Keypad Directory](https://help.verkada.com/intercom/configuration-and-setup/set-up-td63-keypad-directory) [Schedule Intercom Firmware Upgrades](https://help.verkada.com/intercom/configuration-and-setup/schedule-intercom-firmware-upgrades) [License Plates of Interest In Intercom Calls](https://help.verkada.com/intercom/configuration-and-setup/license-plates-of-interest-in-intercom-calls) [E911 Calling with Intercoms (U.S Only)](https://help.verkada.com/intercom/configuration-and-setup/e911-calling-with-intercoms-us-only) [Unique Phone Number for Intercoms (U.S Only)](https://help.verkada.com/intercom/configuration-and-setup/unique-phone-number-for-intercoms-us-only) [Configure a SIP Fallback Extension](https://help.verkada.com/intercom/configuration-and-setup/configure-a-sip-fallback-extension) [Configure an Intercom as an Emergency Phone](https://help.verkada.com/intercom/configuration-and-setup/configure-an-intercom-as-an-emergency-phone) [Configure Second-Generation Video Intercoms](https://help.verkada.com/intercom/configuration-and-setup/configure-second-generation-video-intercoms) [Intercom Reader Settings](https://help.verkada.com/intercom/configuration-and-setup/intercom-reader-settings) [Freepbx Configuration for Verkada Intercoms](https://help.verkada.com/intercom/configuration-and-setup/freepbx-configuration-for-verkada-intercoms) [Intercom Interoperability Manual](https://help.verkada.com/intercom/configuration-and-setup/intercom-interoperability-manual) [Ring Central Configuration for Verkada Intercoms](https://help.verkada.com/intercom/configuration-and-setup/ring-central-configuration-for-verkada-intercoms) [Create and Use Shared Call Flows](https://help.verkada.com/intercom/configuration-and-setup/create-and-use-shared-call-flows) [Intercom Deployment Best Practices Guide](https://help.verkada.com/intercom/configuration-and-setup/intercom-deployment-best-practices-guide) [Intercom Teams Integration](https://help.verkada.com/intercom/configuration-and-setup/intercom-teams-integration) [Set Up a 4-Wire Doorbell Chime for Verkada Intercom](https://help.verkada.com/intercom/configuration-and-setup/set-up-a-4-wire-doorbell-chime-for-verkada-intercom) [Wire a Doorbell Chime to an Intercom](https://help.verkada.com/intercom/configuration-and-setup/wire-a-doorbell-chime-to-an-intercom) [Integrate Verkada Intercoms with SIP](https://help.verkada.com/intercom/configuration-and-setup/integrate-verkada-intercoms-with-sip) [Upload Audio Messages to Intercom](https://help.verkada.com/intercom/configuration-and-setup/upload-audio-messages-to-intercom) [SIP Integration: Cisco Unified CM](https://help.verkada.com/intercom/configuration-and-setup/sip-integration-cisco-unified-cm) [Configure a Video Intercom as a 1-Door AC](https://help.verkada.com/intercom/configuration-and-setup/configure-a-video-intercom-as-a-1-door-ac) [Add and Configure Receivers in Intercom](https://help.verkada.com/intercom/configuration-and-setup/add-and-configure-receivers-in-intercom) [TD52 Status LEDs](https://help.verkada.com/intercom/configuration-and-setup/td52-status-leds) [Make Your First Call with TD52](https://help.verkada.com/intercom/configuration-and-setup/make-your-first-call-with-td52) [Add a Desk Station](https://help.verkada.com/intercom/configuration-and-setup/add-a-desk-station) [Configure a TD52](https://help.verkada.com/intercom/configuration-and-setup/configure-a-td52) [Add an Intercom to Your Site](https://help.verkada.com/intercom/configuration-and-setup/add-an-intercom-to-your-site) [Wire a Video Intercom](https://help.verkada.com/intercom/configuration-and-setup/wire-a-video-intercom) Last updated 16 days ago Was this helpful? --- # Users and Permissions | Command | Verkada Help [Directories for User & Group Management](https://help.verkada.com/command/users-and-permissions/directories-for-user-group-management) [Manage Temporary Users](https://help.verkada.com/command/users-and-permissions/manage-temporary-users) [Customize Roles and Permissions](https://help.verkada.com/command/users-and-permissions/customize-roles-and-permissions) [Control User Login](https://help.verkada.com/command/users-and-permissions/control-user-login) [Manage Key Contacts in Your Organization](https://help.verkada.com/command/users-and-permissions/manage-key-contacts-in-your-organization) [Login Links](https://help.verkada.com/command/users-and-permissions/login-links) [Switch Organizations in Command](https://help.verkada.com/command/users-and-permissions/switch-organizations-in-command) [Verify Your Verkada Command Account](https://help.verkada.com/command/users-and-permissions/verify-your-verkada-command-account) [Roles and Permissions for Command](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) [Enable 2FA for Your Command Account](https://help.verkada.com/command/users-and-permissions/enable-2fa-for-your-command-account) [Manage Command Groups](https://help.verkada.com/command/users-and-permissions/manage-command-groups) [Verkada Command Account FAQ](https://help.verkada.com/command/users-and-permissions/verkada-command-account-faq) [Manage Users in Your Organization](https://help.verkada.com/command/users-and-permissions/manage-users-in-your-organization) Last updated 1 month ago Was this helpful? --- # Get Started with Verkada Security Cameras | Verkada Cameras | Verkada Help Verkada security cameras offer comprehensive video surveillance solutions and deliver reliable monitoring capabilities for enhanced safety and security. You need Org Admin and/or Site Admin [permissions](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) for your Verkada Command organization to complete these actions. ### [](https://help.verkada.com/verkada-cameras/get-started-with-verkada-security-cameras#what-you-need) What you need * PoE-enabled switch or PoE injector * DHCP-enabled network * Cat5 or Cat6 cabling [](https://help.verkada.com/verkada-cameras/get-started-with-verkada-security-cameras#create-a-site) Create a site ----------------------------------------------------------------------------------------------------------------------- Sites are the logical way of grouping and managing devices within your Command organization. Site-level permissions make managing and viewing your devices easier. See [Manage Your Sites and Subsites](https://help.verkada.com/verkada-cameras/configuration-and-setup/manage-sites-and-subsites) for more information on site creation and management. [](https://help.verkada.com/verkada-cameras/get-started-with-verkada-security-cameras#add-a-camera) Add a camera --------------------------------------------------------------------------------------------------------------------- Cameras can be added from the **Devices** page or directly from a site. You can see a camera’s video stream once you’ve added it to Command and connected it to the internet. See [Add a Device to Your Command Account](https://help.verkada.com/verkada-cameras/configuration-and-setup/add-a-device-to-your-command-organization) for more information. Only footage recorded after a camera is added to Command will be accessible. Please ensure that the camera is successfully added to Command before you connect the camera. If you cannot add a camera, contact [Verkada Support](https://help.verkada.com/command/need-help/contact-verkada-support) . ### [](https://help.verkada.com/verkada-cameras/get-started-with-verkada-security-cameras#configure-settings) Configure settings You can edit general settings from a camera’s settings page to make the camera more recognizable, such as changing the name and location. You can also enable more advanced settings, such as cloud backup, audio, etc., to better suit your security needs. See [View and Edit Camera Settings](https://help.verkada.com/verkada-cameras/configuration-and-setup/view-and-edit-camera-settings) for more information on configuring camera settings. #### [](https://help.verkada.com/verkada-cameras/get-started-with-verkada-security-cameras#analytics) Analytics Most Verkada cameras support people, face, and vehicle analytics. Analytics need to be enabled in the camera’s settings before the results populate on the camera page and before you can set up most motion-based alerts. See [People Analytics](https://help.verkada.com/verkada-cameras/analytics-and-detection/people-analytics) and [Vehicle Analytics](https://help.verkada.com/verkada-cameras/analytics-and-detection/vehicle-analytics) for more information. [](https://help.verkada.com/verkada-cameras/get-started-with-verkada-security-cameras#licensing) Licensing --------------------------------------------------------------------------------------------------------------- Every camera you manage in Command needs a license. Verkada licensing is applied for each Command organization, and the licenses co-term to a single expiration date. Your licenses may have been automatically added if you claimed your devices via order number. Otherwise, manually add the licenses from the Admin page. See [Manage Your Licenses](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses) for more information on adding and managing licenses. [](https://help.verkada.com/verkada-cameras/get-started-with-verkada-security-cameras#connect-your-camera) Connect your camera ----------------------------------------------------------------------------------------------------------------------------------- While Verkada cameras are considered low-voltage devices that do not require a certified electrician to install, we strongly recommend you work with a system integrator or other professional for installation. Refer to the camera’s [setup guide](https://www.verkada.com/docs/?product=videoSecurity&contentType=setupGuide) for mounting instructions. #### [](https://help.verkada.com/verkada-cameras/get-started-with-verkada-security-cameras#power-and-network) Power and network Verkada cameras use Power over Ethernet (PoE) for power and communication over the LAN. In most cases, cameras will need to connect directly to a standard switch. PoE injectors can be used when a PoE switch is not available. See [Camera Power Requirements](https://help.verkada.com/verkada-cameras/camera-specifications/camera-power-requirements) for the power requirements of your specific camera model. #### [](https://help.verkada.com/verkada-cameras/get-started-with-verkada-security-cameras#firmware-updates) Firmware updates Your camera will run an automatic firmware update once connected to the internet indicated by a flashing orange LED on the front of the camera. This typically takes about 3–5 minutes; see [Camera LED Status Indicators](https://help.verkada.com/verkada-cameras/camera-specifications/camera-led-status-indicators) for troubleshooting steps if the LED does not turn solid blue within this time. [](https://help.verkada.com/verkada-cameras/get-started-with-verkada-security-cameras#check-network-settings) Check network settings ----------------------------------------------------------------------------------------------------------------------------------------- Verkada cameras are designed to be plug-and-play. However, if your environment includes a firewall with custom rules and policies, you may need to make some configuration changes to get your cameras connected to the cloud. See [Camera Network Settings](https://help.verkada.com/verkada-cameras/camera-specifications/camera-network-settings) for more information. #### [](https://help.verkada.com/verkada-cameras/get-started-with-verkada-security-cameras#review-your-available-bandwidth) Review your available bandwidth Your internet speed requirements will depend on the number of cameras at your location. While Verkada cameras store video data locally in on-camera storage, they require an internet connection to send metadata to the cloud. Viewing video through the cloud, archiving video, or using other advanced features will increase bandwidth usage. See [Bandwidth Consumption & Uplink Requirements](https://help.verkada.com/verkada-cameras/camera-specifications/bandwidth-consumption-uplink-requirements-for-video) for the bandwidth requirements of your specific camera model. [](https://help.verkada.com/verkada-cameras/get-started-with-verkada-security-cameras#configure-alerts) Configure alerts ----------------------------------------------------------------------------------------------------------------------------- Verkada Command allows you to receive push, email, and SMS alerts for events generated in your organization. The ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1795869993-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FylYKicREo6JpuOJH4teK%252Fuploads%252Fgit-blob-91bd70c6d63692bdc09cfe2b790499421775da49%252F05283db7c21547b9b9a924fe0723bd14f6720315.png%3Falt%3Dmedia&width=300&dpr=4&quality=100&sign=8793c1e0&sv=2) in the bottom left of Command takes you to the **Alerts** page where you can set up and manage alerts. Camera events include motion detection, loitering detection, online status, and more. See [Events and Alerts](https://help.verkada.com/verkada-cameras/events-and-alerts) and [Configure Camera Event Alerts](https://help.verkada.com/verkada-cameras/events-and-alerts/create-camera-event-alerts) for more information on camera events and creating alerts. Last updated 1 day ago Was this helpful? --- # Analytics and Detection | Verkada Cameras | Verkada Help [Device Stats Dashboard](https://help.verkada.com/verkada-cameras/analytics-and-detection/device-stats-dashboard) [Occupancy Trends](https://help.verkada.com/verkada-cameras/analytics-and-detection/occupancy-trends) [Detect People Count](https://help.verkada.com/verkada-cameras/analytics-and-detection/detect-people-count) [People and Face Search on Mobile Apps](https://help.verkada.com/verkada-cameras/analytics-and-detection/people-and-face-search-on-mobile-apps) [License Plate Recognition Overview & FAQ](https://help.verkada.com/verkada-cameras/analytics-and-detection/license-plate-recognition-overview-faq) [People and Vehicle History Search](https://help.verkada.com/verkada-cameras/analytics-and-detection/people-and-vehicle-history-search) [View Live Motion on Floor Plans](https://help.verkada.com/verkada-cameras/analytics-and-detection/view-live-motion-on-floor-plans) [Vehicle Analytics](https://help.verkada.com/verkada-cameras/analytics-and-detection/vehicle-analytics) [People Analytics](https://help.verkada.com/verkada-cameras/analytics-and-detection/people-analytics) [People and Vehicle Motion Search](https://help.verkada.com/verkada-cameras/analytics-and-detection/people-and-vehicle-motion-search) Last updated 1 month ago Was this helpful? --- # Quick Reference Guide for Verkada Command | Command | Verkada Help [](https://help.verkada.com/command/quick-reference-guide-for-verkada-command#account-setup) Account Setup --------------------------------------------------------------------------------------------------------------- * [Get Started with Verkada Command](https://help.verkada.com/command/get-started-with-verkada-command) * [Required Network Settings](https://help.verkada.com/command/required-network-settings) * [Verkada Command System Requirements](https://help.verkada.com/command/verkada-command-system-requirements) * [Verify Your Verkada Command Account](https://help.verkada.com/command/users-and-permissions/verify-your-verkada-command-account) * [Switch Organizations in Command](https://help.verkada.com/command/users-and-permissions/switch-organizations-in-command) [](https://help.verkada.com/command/quick-reference-guide-for-verkada-command#users-and-permissions) Users and Permissions ------------------------------------------------------------------------------------------------------------------------------- * [Roles and Permissions for Command](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) * [Customize Roles and Permissions](https://help.verkada.com/command/users-and-permissions/customize-roles-and-permissions) * [Manage Users in Your Organization](https://help.verkada.com/command/users-and-permissions/manage-users-in-your-organization) * [Manage Temporary Users](https://help.verkada.com/command/users-and-permissions/manage-temporary-users) * [Magic Link Login](https://help.verkada.com/command/users-and-permissions/login-links) [](https://help.verkada.com/command/quick-reference-guide-for-verkada-command#organization-settings) Organization Settings ------------------------------------------------------------------------------------------------------------------------------- * [Manage Your Admin Page Settings](https://help.verkada.com/command/organization-wide-settings/manage-your-admin-page-settings) * [Manage and View Audit Logs](https://help.verkada.com/command/organization-wide-settings/manage-and-view-audit-logs) * [Feature Manager](https://help.verkada.com/command/organization-wide-settings/feature-manager) * [Partner Tools](https://help.verkada.com/command/site-planner-amp-partner-tools/partner-tools/partner-tools) [](https://help.verkada.com/command/quick-reference-guide-for-verkada-command#authentication) Authentication ----------------------------------------------------------------------------------------------------------------- * [Authentication and Provisioning Overview](https://help.verkada.com/command/single-sign-on-sso/authentication-and-provisioning-overview) * [Activate 2FA for Your Command Account](https://help.verkada.com/command/users-and-permissions/enable-2fa-for-your-command-account) * [Enable SAML for Your Command Account](https://help.verkada.com/command/single-sign-on-sso/saml/enable-saml-for-your-command-account) * [Microsoft Entra ID SAML Integration](https://help.verkada.com/command/single-sign-on-sso/saml/microsoft-entra-id-saml-integration) * [Okta SAML Integration](https://help.verkada.com/command/single-sign-on-sso/saml/okta-saml-integration) * [Microsoft Entra ID SCIM Integration](https://help.verkada.com/command/third-party-user-provisioning/microsoft-entra-id-scim-integration) * [Okta SCIM Integration](https://help.verkada.com/command/third-party-user-provisioning/okta-scim-integration) * [Create or Refresh an Org’s SCIM Token](https://help.verkada.com/command/third-party-user-provisioning/create-or-refresh-an-organizations-scim-token) [](https://help.verkada.com/command/quick-reference-guide-for-verkada-command#data-protection-and-security) **Data Protection and Security** ------------------------------------------------------------------------------------------------------------------------------------------------- * [Set a Default or Camera-Specific Location for Image and Video Data](https://help.verkada.com/command/data-protection-and-security/set-a-default-or-camera-specific-location-for-image-and-video-data-storage-and-processing) * [Privacy and Security Checklist](https://help.verkada.com/command/data-protection-and-security/privacy-and-security-checklist) * [Enable Data Sharing with Verkada](https://help.verkada.com/command/data-protection-and-security/enable-data-sharing-with-verkada) [](https://help.verkada.com/command/quick-reference-guide-for-verkada-command#troubleshooting) Troubleshooting ------------------------------------------------------------------------------------------------------------------- * [Contact Verkada Support](https://help.verkada.com/command/need-help/contact-verkada-support) * [Enable Support Access](https://help.verkada.com/command/need-help/enable-support-access) * [Clear Your Browser Cache](https://help.verkada.com/command/need-help/clear-your-browser-cache) Follow [our blog](https://www.verkada.com/blog/) for all our latest features and announcements! Last updated 22 hours ago Was this helpful? --- # Hardware Installation | Access Control | Verkada Help [Connect a 3rd Party Reader to a Verkada Access Controller with OSDP](https://help.verkada.com/access-control/hardware-installation/connect-a-3rd-party-reader-to-a-verkada-access-controller-with-osdp) [AD Series Wired Lock Setup](https://help.verkada.com/access-control/hardware-installation/ad-series-wired-lock-setup) [Mount an AC12](https://help.verkada.com/access-control/hardware-installation/mount-an-ac12) [PoE Passthrough on the AC12](https://help.verkada.com/access-control/hardware-installation/poe-passthrough-on-the-ac12) [Set Up an In/Out Door with Two Readers](https://help.verkada.com/access-control/hardware-installation/set-up-an-inout-door-with-two-readers) [Wire a Door to a Verkada Access Controller](https://help.verkada.com/access-control/hardware-installation/wire-a-door-to-a-verkada-access-controller) [Install the Fire Alarm Interface](https://help.verkada.com/access-control/hardware-installation/install-the-fire-alarm-interface) [Find an AC62's Serial Number and MAC Address](https://help.verkada.com/access-control/hardware-installation/find-an-ac62s-serial-number-and-mac-address) [Integrate External Power with the AC41 in EMEA](https://help.verkada.com/access-control/hardware-installation/integrate-external-power-with-the-ac41-in-emea) [Fire Alarm Control Panel with AC41](https://help.verkada.com/access-control/hardware-installation/fire-alarm-control-panel-with-ac41) [AX11 Elevator Installation](https://help.verkada.com/access-control/hardware-installation/ax11-elevator-installation) [Access Control Deployment Best Practices](https://help.verkada.com/access-control/hardware-installation/access-control-deployment-best-practices) [Supported Card Formats](https://help.verkada.com/access-control/hardware-installation/supported-card-formats) [Badge Reader Support](https://help.verkada.com/access-control/hardware-installation/badge-reader-support) [Set Up Access Control for a Man Trap](https://help.verkada.com/access-control/hardware-installation/set-up-access-control-for-a-man-trap) [Battery Backup for the AC41 Door Controller](https://help.verkada.com/access-control/hardware-installation/battery-backup-for-the-ac41-door-controller) [Find a Serial Number and MAC Address](https://help.verkada.com/access-control/hardware-installation/find-a-serial-number-and-mac-address) [Recommended Wires for Access Controllers](https://help.verkada.com/access-control/hardware-installation/recommended-wires-for-access-controllers) ### [](https://help.verkada.com/access-control/hardware-installation#wireless-locks) Wireless locks [Verkada Wireless Lock Command Setup](https://help.verkada.com/access-control/hardware-installation/wireless-locks/verkada-wireless-lock-command-setup) [Verkada Wireless Lock LED Patterns](https://help.verkada.com/access-control/hardware-installation/wireless-locks/verkada-wireless-lock-led-patterns) [Verkada Wireless Lock FAQ](https://help.verkada.com/access-control/hardware-installation/wireless-locks/verkada-wireless-lock-faq) [Wiring Best Practices for Third-Party Wireless Locks](https://help.verkada.com/access-control/hardware-installation/wireless-locks/wiring-best-practices-for-third-party-wireless-locks) [ENGAGE Wireless Lock Offline Integration](https://help.verkada.com/access-control/hardware-installation/wireless-locks/engage-wireless-lock-offline-integration) [Set Up Assa Abloy Aperio Wireless Locks](https://help.verkada.com/access-control/hardware-installation/wireless-locks/set-up-assa-abloy-aperio-wireless-locks) [Set Up Schlage Control Wireless Locks](https://help.verkada.com/access-control/hardware-installation/wireless-locks/set-up-schlage-control-wireless-locks) [Use the Wireless Lock Internal Push Button](https://help.verkada.com/access-control/hardware-installation/wireless-locks/use-the-wireless-lock-internal-push-button) [ENGAGE Wireless Lock Online Integration](https://help.verkada.com/access-control/hardware-installation/wireless-locks/engage-wireless-lock-online-integration) [AD Series Wireless Lock Setup](https://help.verkada.com/access-control/hardware-installation/wireless-locks/ad-series-wireless-lock-setup) Last updated 15 days ago Was this helpful? --- # Configuration and Setup | New Alarms | Verkada Help [Self Monitored Response Level](https://help.verkada.com/new-alarms/configuration-and-setup/self-monitored-response-level) [Configure Door Held Open (DHO) Alarm Triggers for Wired and Wireless Door Sensors](https://help.verkada.com/new-alarms/configuration-and-setup/configure-door-held-open-dho-alarm-triggers-for-wired-and-wireless-door-sensors) [Bulk Assign Sensors to an Alarm Sites](https://help.verkada.com/new-alarms/configuration-and-setup/bulk-assign-sensors-to-an-alarm-sites) [Configure Silent and Duress Alarm Responses](https://help.verkada.com/new-alarms/configuration-and-setup/configure-silent-and-duress-alarm-responses) [Walk Test for Sensor Partitions](https://help.verkada.com/new-alarms/configuration-and-setup/walk-test-for-sensor-partitions) [Configure AI-Powered Deterrence](https://help.verkada.com/new-alarms/configuration-and-setup/configure-ai-powered-deterrence) [Disarm Behavior After Alarm Resolution in New Alarms](https://help.verkada.com/new-alarms/configuration-and-setup/disarm-behavior-after-alarm-resolution-in-new-alarms) [BP32 Alarm Panel Configurations and Battery Backup Estimator](https://help.verkada.com/new-alarms/configuration-and-setup/bp32-alarm-panel-configurations-and-battery-backup-estimator) [Smart Schedule in New Alarms](https://help.verkada.com/new-alarms/configuration-and-setup/smart-schedule-in-new-alarms) [Save the Verkada Alarms Monitoring Phone Number for New Alarms](https://help.verkada.com/new-alarms/configuration-and-setup/save-the-verkada-alarms-monitoring-phone-number-for-new-alarms) [Best Practices for Camera Triggers to Reduce False Alarms in New Alarms](https://help.verkada.com/new-alarms/configuration-and-setup/best-practices-for-camera-triggers-to-reduce-false-alarms-in-new-alarms) [PSAP Override in New alarms](https://help.verkada.com/new-alarms/configuration-and-setup/psap-override-in-new-alarms) [Verkada Monitoring Phone Numbers - Canada](https://help.verkada.com/new-alarms/configuration-and-setup/verkada-monitoring-phone-numbers-canada) [Configure Doors as Alarm Triggers](https://help.verkada.com/new-alarms/configuration-and-setup/configure-doors-as-alarm-triggers) [Configure the BZ32](https://help.verkada.com/new-alarms/configuration-and-setup/configure-the-bz32) [BR33 Panic Button Configuration](https://help.verkada.com/new-alarms/configuration-and-setup/br33-panic-button-configuration) [Configure Camera Alarm Trigger Events for New Alarms](https://help.verkada.com/new-alarms/configuration-and-setup/configure-camera-alarm-trigger-events-for-new-alarms) [External Response Contacts for New Alarms](https://help.verkada.com/new-alarms/configuration-and-setup/external-response-contacts-for-new-alarms) [Configure an Alarm Response](https://help.verkada.com/new-alarms/configuration-and-setup/configure-an-alarm-response) [Set Up the BZ11 Horn Speaker](https://help.verkada.com/new-alarms/configuration-and-setup/set-up-the-bz11-horn-speaker) [Configure New Alarms Site Settings](https://help.verkada.com/new-alarms/configuration-and-setup/configure-new-alarms-site-settings) [Configure Partitions](https://help.verkada.com/new-alarms/configuration-and-setup/configure-partitions) [Agent Talk Down](https://help.verkada.com/new-alarms/configuration-and-setup/agent-talk-down) [Alarm Sites](https://help.verkada.com/new-alarms/configuration-and-setup/alarm-sites) [Supervised Wiring](https://help.verkada.com/new-alarms/configuration-and-setup/supervised-wiring) [Wireless Alarms Devices](https://help.verkada.com/new-alarms/configuration-and-setup/wireless-alarms-devices) [Supported Cameras for Video Alarms](https://help.verkada.com/new-alarms/configuration-and-setup/supported-cameras-for-video-alarms) Last updated 15 days ago Was this helpful? --- # Events and Alerts | Verkada Cameras | Verkada Help [Occlusion Alerts](https://help.verkada.com/verkada-cameras/events-and-alerts/occlusion-alerts) [Smart Trends Dashboards](https://help.verkada.com/verkada-cameras/events-and-alerts/smart-trends-dashboards) [Activity Detection Alerts](https://help.verkada.com/verkada-cameras/events-and-alerts/activity-detection-alerts) [Industry Alerts](https://help.verkada.com/verkada-cameras/events-and-alerts/industry-alerts) [Helix Alerts](https://help.verkada.com/verkada-cameras/events-and-alerts/helix-alerts) [Camera Storage Error Alerts](https://help.verkada.com/verkada-cameras/events-and-alerts/camera-storage-error-alerts) [Create Camera Event Alerts](https://help.verkada.com/verkada-cameras/events-and-alerts/create-camera-event-alerts) [Manage Alerts Across Verkada Products](https://help.verkada.com/verkada-cameras/events-and-alerts/manage-alerts-across-verkada-products) [Helix API Integration](https://help.verkada.com/verkada-cameras/events-and-alerts/helix-api-integration) [Create Alerts Across Verkada Products](https://help.verkada.com/verkada-cameras/events-and-alerts/create-alerts-across-verkada-products) [Share Event Alerts](https://help.verkada.com/verkada-cameras/events-and-alerts/share-event-alerts) [Optimize Your Alerts](https://help.verkada.com/verkada-cameras/events-and-alerts/optimize-your-alerts) [Person of Interest Alerts](https://help.verkada.com/verkada-cameras/events-and-alerts/person-of-interest-alerts) [Tamper Alerts](https://help.verkada.com/verkada-cameras/events-and-alerts/tamper-alerts) [Camera Status Alerts](https://help.verkada.com/verkada-cameras/events-and-alerts/camera-status-alerts) [License Plate of Interest Alerts](https://help.verkada.com/verkada-cameras/events-and-alerts/license-plate-of-interest-alerts) [Crowd Alerts](https://help.verkada.com/verkada-cameras/events-and-alerts/crowd-alerts) [Motion Alerts](https://help.verkada.com/verkada-cameras/events-and-alerts/motion-alerts) Last updated 22 days ago Was this helpful? --- # Troubleshooting | Verkada Cameras | Verkada Help [Verkada Troubleshooting Overview for Installers](https://help.verkada.com/verkada-cameras/troubleshooting/verkada-troubleshooting-overview-for-installers) [Troubleshooting Guide for PTZ Cameras](https://help.verkada.com/verkada-cameras/troubleshooting/troubleshooting-guide-for-ptz-cameras) [Network Troubleshooting - Internet Sharing](https://help.verkada.com/verkada-cameras/troubleshooting/network-troubleshooting-internet-sharing) [Troubleshoot Banding on Camera Feed](https://help.verkada.com/verkada-cameras/troubleshooting/troubleshoot-banding-on-camera-feed) [Troubleshooting Buffering and Latency](https://help.verkada.com/verkada-cameras/troubleshooting/troubleshooting-buffering-and-latency) [Troubleshoot Offline Camera](https://help.verkada.com/verkada-cameras/troubleshooting/troubleshoot-offline-camera) [Fix a Non-Loading Embed](https://help.verkada.com/verkada-cameras/troubleshooting/fix-a-non-loading-embed) [Resolve Issues with Night Mode](https://help.verkada.com/verkada-cameras/troubleshooting/resolve-issues-with-night-mode) [Update Time Zone for a Camera](https://help.verkada.com/verkada-cameras/troubleshooting/update-time-zone-for-a-camera) [Resolve Issues with Missing Cameras](https://help.verkada.com/verkada-cameras/troubleshooting/resolve-issues-with-missing-cameras) [Loss of Network Connection for Cameras](https://help.verkada.com/verkada-cameras/troubleshooting/loss-of-network-connection-for-cameras) Last updated 1 month ago Was this helpful? --- # Single Sign-On (SSO) | Command | Verkada Help [Authentication and Provisioning Overview](https://help.verkada.com/command/single-sign-on-sso/authentication-and-provisioning-overview) ### [](https://help.verkada.com/command/single-sign-on-sso#oidc) OIDC [OIDC Based SSO for Google Workspace](https://help.verkada.com/command/single-sign-on-sso/oidc/oidc-based-sso-for-google-workspace) [OIDC Based SSO for Azure Entra](https://help.verkada.com/command/single-sign-on-sso/oidc/oidc-based-sso-for-azure-entra) [Enable Enterprise Controlled Encryption (ECE)](https://help.verkada.com/command/single-sign-on-sso/oidc/enable-enterprise-controlled-encryption-ece) [OIDC based SSO for Okta](https://help.verkada.com/command/single-sign-on-sso/oidc/oidc-based-sso-for-okta) ### [](https://help.verkada.com/command/single-sign-on-sso#saml) SAML [JumpCloud SAML Integration](https://help.verkada.com/command/single-sign-on-sso/saml/jumpcloud-saml-integration) [Enable SAML for Your Command Account](https://help.verkada.com/command/single-sign-on-sso/saml/enable-saml-for-your-command-account) [Okta SAML Integration](https://help.verkada.com/command/single-sign-on-sso/saml/okta-saml-integration) [AD FS SAML Integration](https://help.verkada.com/command/single-sign-on-sso/saml/ad-fs-saml-integration) [Google Workspace SAML Integration](https://help.verkada.com/command/single-sign-on-sso/saml/google-workspace-saml-integration) [Microsoft Entra ID SAML Integration](https://help.verkada.com/command/single-sign-on-sso/saml/microsoft-entra-id-saml-integration) [OneLogin SAML Integration](https://help.verkada.com/command/single-sign-on-sso/saml/onelogin-saml-integration) Last updated 1 month ago Was this helpful? --- # Roles and Permissions for Access Control | Access Control | Verkada Help As of November 14, 2024, access control permissions have changed. Users with legacy access control roles will maintain their permissions until they are updated to the current roles detailed in this article. See [Legacy Access Control Roles](https://help.verkada.com/access-control/configuration-and-setup/legacy-access-control-roles) for more information. This article describes the set of roles and associated permissions for [Verkada Access Control](https://www.verkada.com/access-control/) . For more information on roles and permissions for other Verkada product lines, see [Roles and Permissions for Command](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) . * * * ### [](https://help.verkada.com/access-control/roles-and-permissions-for-access-control#permissions-considerations) Permissions considerations * Subsites inherit permissions from all parent sites, including the ultimate parent. * Users can belong to multiple groups. When roles conflict, the user receives the **highest role** granted directly or through any group. * Group-assigned roles can be manually upgraded but not downgraded. Remove the user from the group with the higher role to downgrade their access. Permissions for access control are set at both the organizational level and the site level. There are two org-level roles and one site-level role that define a user’s permissions to view and manage access control permissions and devices: Access control roles are granted to users independently of one another. * * * [](https://help.verkada.com/access-control/roles-and-permissions-for-access-control#org-level-roles) Org-level roles ------------------------------------------------------------------------------------------------------------------------- Access System[](https://help.verkada.com/access-control/roles-and-permissions-for-access-control#access-system) The Access System role grants permissions to manage org-wide access control settings for all sites. At a high level, these are the permissions granted to each level of Access System roles: ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F134288481-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FaaHs5RfKqv9Z49mi02cC%252Fuploads%252Fgit-blob-026c6834aecc908f93e2907aee7e53e3f68659b3%252F56ea0081a973d9d23dcb78d339155c52a617757e.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=20f7bd0c&sv=2) None Does **not** have permission to manage org-wide access control settings for an organization. Access System Manager A user or group with Access System Manager can: * View, add, delete, and edit door schedules and door exceptions. * View, add, delete, and edit access exceptions. Access System Admin A user or group with Access User Admin can: * Do everything that an Access System Manager can do. * Inherits [Access Site Admin](https://help.verkada.com/access-control/roles-and-permissions-for-access-control) permissions for **all sites**. * Grant [Access System Role](https://help.verkada.com/access-control/roles-and-permissions-for-access-control) and [Access Site Role](https://help.verkada.com/access-control/roles-and-permissions-for-access-control) permissions for any site. * Configure org-wide access settings, such as Bluetooth unlock. * Add, edit, and delete badge templates. * Edit and delete buildings, floors, and add floorplans to floors. * View the descriptions of and delete saved event reports created by other users. * [Enable support access](https://help.verkada.com/command/need-help/enable-support-access) to Command for Organization. Access User Management[](https://help.verkada.com/access-control/roles-and-permissions-for-access-control#access-user-management) The Access User Management role grants permissions to manage access users, credentials, and access groups. At a high level, these are the permissions granted to each level of Access User Management roles: ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F134288481-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FaaHs5RfKqv9Z49mi02cC%252Fuploads%252Fgit-blob-74df2d3ae83b53f3ac26d4ae01e4a6f1198977b0%252Ff727908be1d9ea009b2f181222054529b96e723a.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=20180c31&sv=2) None Does **not** have permission to manage an organization’s access users or groups. Access Credential Manager A user or group with Access Credential Manager can: * View all access users. * Add, edit, and delete credentials for access users. * Add and delete profile pictures for access users. * Print user badges. * Configure Pass app settings for access users. * Grant and suspend access for access users, including editing a user’s start and end date for temporary access. Access User Manager A user or group with Access User Manager can: * Do everything that an Access Credential Manager can do. * Add and edit access users (not synced via SCIM), including updating all user profile information. * Add and remove users from existing access groups (not synced via SCIM). Access User Admin A user or group with Access User Admin can: * Do everything an Access User Manager can do. * Grant [Access User Management Role](https://help.verkada.com/access-control/roles-and-permissions-for-access-control) permissions for the organization. * Delete access users (not synced via SCIM). * Add, edit, and delete access groups (not synced via SCIM). * [Enable support access](https://help.verkada.com/command/need-help/enable-support-access) to Command for Organization. [](https://help.verkada.com/access-control/roles-and-permissions-for-access-control#site-level-role) Site-level role ------------------------------------------------------------------------------------------------------------------------- Access Site[](https://help.verkada.com/access-control/roles-and-permissions-for-access-control#access-site) The Access Site role grants permissions to manage access control settings, devices, and door access. At a high level, these are the permissions granted to each level of Access Site roles: ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F134288481-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FaaHs5RfKqv9Z49mi02cC%252Fuploads%252Fgit-blob-e0599d6030595af7ba548a13720d2efe19b87faf%252F2752516270ba07c3cb2bb4d617bebf13ff731520.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=5b56c9dc&sv=2) None Does **not** have permission to manage a site’s access control settings or devices. Access Site Viewer A user or group with Access Site Viewer permissions for a site can: * View any door in the site. * Unlock doors from Command for doors the user has access to. * View a floorplan that has doors from the site added. * View live and historical access events for the site. * Run, save, export, and distribute reports of historical access events. * Add and edit alerts based on access events. * Run and end roll call reports from existing roll call templates and mark people as safe or missing on an active roll call report. Access Site Manager A user or group with Access Site Manager permissions for a site can: * Do everything an Access Site Viewer can do. * Unlock any door in the site from Command. * Override the schedule for any door in the site from Command. * Change a door’s schedule to another preexisting schedule. * Apply or remove preexisting door exceptions. * Add, configure, and delete access levels. * View live and historical access events. * Run, save, export, and distribute reports of historical access events. * Create, configure, and delete roll call templates. * View areas and clear anti-passback violations. Access Site Admin A user or group with Access Site Admin permissions for a site can: * Do everything an Access Site Manager can do. * Grant [Access Site Role](https://help.verkada.com/access-control/roles-and-permissions-for-access-control) permissions for the site. * Add, configure, and delete access control devices. * Add, configure, and delete doors, AUX inputs, and AUX outputs. * Add, configure, and delete lockdowns. * Configure areas and anti-passback (APB) settings. * Manage site-level access settings for the site, such as Bluetooth unlock and scheduled firmware updates. * [Enable support access](https://help.verkada.com/command/need-help/enable-support-access) to Command for Organization. * * * [](https://help.verkada.com/access-control/roles-and-permissions-for-access-control#set-permissions) Set permissions ------------------------------------------------------------------------------------------------------------------------- Users[](https://help.verkada.com/access-control/roles-and-permissions-for-access-control#users) **Org-level** In Verkada Command, go to All Products > Admin .Under Org Settings, select Users.Select your user.On the left side panel, next to Access Control Roles, click Edit.a. Grant the necessary org-level access control roles. b. Click Apply Changes. **Site-level** In Verkada Command, go to All Products > Admin .Under Org Settings, select Users.Select your user.At the top right, click Manage Roles.a. From the Access Site Role dropdown, select the permission level for the needed sites. b. Click Save. Groups[](https://help.verkada.com/access-control/roles-and-permissions-for-access-control#groups) **Org-level** In Verkada Command, go to All Products > Admin .Under Org Settings, select Groups.Select your group.On the left side panel, next to Access Control Roles, click Edit.a. Grant the necessary org-level access control roles. b. Click Apply Changes. **Site-level** In Verkada Command, go to All Products > Admin .Under Org Settings, select Groups.Select your group.At the top, click Site Roles.a. At the top right, click Manage Roles. b. From the Access Site Role dropdown, select the permission level for the needed sites c. Click Save. * * * ### [](https://help.verkada.com/access-control/roles-and-permissions-for-access-control#common-access-control-permission-configurations) Common access control permission configurations **Scenario** **Role Configuration** User needs total control over all access control system settings, devices, and users. ​ For example, a Security Director. Access System Admin Access User Admin User needs to be able to create and edit door schedules or exceptions applied to doors in one or more sites. For example, a security team member. Access System Manager User is responsible for onboarding new users by printing badges and adding them to access groups. ​ For example, an HR staff member. Access User Manager User is only responsible for adding credential info and printing badges for new users, such as SCIM-synced users. ​ For example, an HR staff member. [Access Credential Manager](https://help.verkada.com/access-control/roles-and-permissions-for-access-control) User needs to manage all site-specific access control settings but should **not** be able to edit user or access group settings (granted by User Management Roles). ​ For example, an office General Manager. Access Site Admin User needs to manage which access groups have access to doors for a particular site but should **not** be able to edit other access control settings for the site. ​ For example, an office facilities staff member. [Access Site Manager](https://help.verkada.com/access-control/roles-and-permissions-for-access-control) User only needs to view and unlock certain doors for a particular site. ​ For example, a front desk receptionist. [Access Site Viewer](https://help.verkada.com/access-control/roles-and-permissions-for-access-control) * * * **Revisions** 11/14/2024: * Added the new Access System, Access User Management, and Access Site roles. * Removed the legacy Access Control Admin, Access Control Manager, and Access Site Admin roles. See [Legacy Access Control Roles](https://help.verkada.com/access-control/configuration-and-setup/legacy-access-control-roles) for more information. **Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=akeui7lbme0) . Last updated 22 hours ago Was this helpful? --- # Alarms Network Settings | New Alarms | Verkada Help This article is a guide for new Alarms. Refer to this [article](https://help.verkada.com/classic-alarms/classic-alarms-network-settings) if you have classic Alarms. See [New Alarms vs Classic Alarms](https://help.verkada.com/new-alarms/new-alarms-vs-classic-alarms) if you are unsure which version of Alarms you have. * * * This article outlines the required network settings that your Verkada Alarms devices need to communicate with [Verkada Command](https://help.verkada.com/command/get-started-with-verkada-command) . For more information on the required network settings for other Verkada product lines see [Required Network Settings](https://help.verkada.com/command/required-network-settings) . Verkada devices are incompatible with LANs that require proxy servers or Secure Socket Layer (SSL)/Transport Layer Security (TLS) inspection. If either is in use, a bypass for all Verkada devices must be implemented for Verkada devices to communicate with Verkada Command. [](https://help.verkada.com/new-alarms/alarms-specifications/alarms-network-settings#ip-address) IP address ---------------------------------------------------------------------------------------------------------------- Alarms devices must be assigned an IPv4 address to communicate on the LAN and to Verkada Command. Alarms devices use Dynamic Host Configuration Protocol (DHCP) and User Datagram Protocol (UDP) to obtain their IP addresses and network configurations. If you require your Alarm device to have a specific IP address, create a DHCP reservation using the device’s Media Access Control (MAC) address (found on the device’s label). [](https://help.verkada.com/new-alarms/alarms-specifications/alarms-network-settings#domain-name-system) Domain Name System -------------------------------------------------------------------------------------------------------------------------------- Alarms devices use the DNS server to resolve Verkada’s fully qualified domain names (FQDN) to IP addresses to communicate with them. Your DHCP server tells the Alarms device where the DNS server is on the network and the Alarms device communicates using UDP port 53. DNS over HTTPS (DoH) is currently not supported. [](https://help.verkada.com/new-alarms/alarms-specifications/alarms-network-settings#firewall-settings) Firewall settings ------------------------------------------------------------------------------------------------------------------------------ Alarms devices require access to many endpoints to ensure they can communicate with Command and all features will be accessible. Many customers may want to allow the devices to communicate with the general required endpoints. These are the general domains to allow, **applicable for all organization-regions**: Copy 34.216.15.26 - UDP/123 *.verkada.com - UDP/123 + TCP+UDP/443 *.appcenter.ms - TCP/443 global.turn.twilio.com - TCP/443 time.cloudflare.com - TCP/4460 time.cloudflare.com - UDP/123 If your firewall does not allow wildcard masking, or you prefer to have the entire FQDN of the endpoint in your firewall rules, you can add the domains to your allowlist based on the region your devices are in. **Region: United States** Copy 34.216.15.26 - UDP/123 api.control.verkada.com - TCP+UDP/443 api.global-prod.control.verkada.com - TCP+UDP/443 firmware.control.verkada.com - TCP+UDP/443 index.control.verkada.com - TCP+UDP/443 relay.control.verkada.com - TCP+UDP/443 relay.global-prod.control.verkada.com - TCP+UDP/443 time.control.verkada.com - UDP/123 update.control.verkada.com - TCP+UDP/443 vconductor.command.verkada.com - TCP+UDP/443 vconductor.global-prod.command.verkada.com - TCP+UDP/443 vprotect.control.verkada.com - TCP+UDP/443 *.appcenter.ms - TCP/443 global.turn.twilio.com - TCP/443 BZ11s in **all regions** require these endpoints: Copy global.stun.twilio.com - UDP/3478 global.turn.twilio.com - UDP/3478 **WH52 / BK22** Copy 224.0.0.251 UDP/5353 BP52_IP TCP/UDP 5607 BP52_IP TCP/UDP 5606 Use the [Verkada Network Tester](https://network-tester.support.verkada.com/) to verify your devices can connect to Verkada Command. Select your region and the **Alarms** product type to run the check. The following endpoints must be allowed on your network for the test to work: * speed.cloudflare.com * network-tester.support.verkada.com Last updated 23 hours ago Was this helpful? --- # New Alarms vs. Classic Alarms | New Alarms | Verkada Help Verkada Alarms was redesigned in 2024 for greater ease of install, reliability, and user experience. The new Verkada Alarms consists of new hardware and software, which operate independently from the classic version of Alarms. The key difference between new and classic Alarms is the system architecture. Classic Alarms uses a multi-hub design where each device independently communicates with the cloud. New Alarms employs a single-brain architecture, centralizing cloud communication through the alarm panel and connecting all devices locally via low-voltage wiring. This setup minimizes device offline risks, improves system uptime, supports offline arm/disarm, and simplifies the **reuse of existing sensors and wiring**, avoiding a full system overhaul. * * * [](https://help.verkada.com/new-alarms/new-alarms-vs-classic-alarms#hardware-compatibility-list) Hardware compatibility list --------------------------------------------------------------------------------------------------------------------------------- Because of the different architectures, new Alarms hardware is **not compatible** with classic Alarms hardware. Only some intrusion sensors and the BZ11 horn are compatible with both new and classic Alarms. See the full hardware compatibility list below: **Hardware Model** **Description** **Compatible with New Alarms** **Compatible with Classic Alarms** BP52 Alarm Panel ✔️ BK22 Alarm Keypad ✔️ BE32 Alarm Expander ✔️ ACC-CEL-LTE-2 Cellular Backup Communicator for BP52 ✔️ WH32 Wireless Repeater ✔️ WH52 Wireless Hub ✔️ ACC-VBX-200WH Backup Battery for BP52 ✔️ ACC-VBX-ENC Dual Battery Enclosure for BP52 ✔️ BR11 Wired Motion Sensor ✔️ ✔️ BR12 Wired Surface Mount Door Sensor ✔️ ✔️ BR13 Wired Recessed Door Sensor ✔️ ✔️ BR31 Wireless Door Sensor ✔️ ✔️ BR32 Wireless Motion Sensor ✔️ ✔️ BR33 Mounted Panic Button ✔️ ✔️ BR34 Wireless Glass Break Sensor (Classic) ✔️ BR35 Wireless Water leak Sensor ✔️ ✔️ BZ11 Horn Speaker ✔️ ✔️ BZ32 Wireless Siren Strobe ✔️ BP41 Alarm Panel (Classic) ✔️ BK11 Alarm Keypad (Classic) ✔️ BK21 Alarm Keypad (Classic) ✔️ BC51 Alarm Console (Classic) ✔️ BC82 Alarm Console (Classic) ✔️ BH61 Wireless Hub (Classic) ✔️ BX21 Wireless Relay (Classic) ✔️ ACC-CEL-LTE Cellular Backup Communicator (Classic) ✔️ ACC-CON-STD-1 Alarm Console Stand (Classic) ✔️ See [Supported Cameras for Video Alarms](https://help.verkada.com/new-alarms/configuration-and-setup/supported-cameras-for-video-alarms) for a list of camera models compatible as triggers for new and classic Alarms. * * * [](https://help.verkada.com/new-alarms/new-alarms-vs-classic-alarms#license-compatibility-list) License compatibility list ------------------------------------------------------------------------------------------------------------------------------- New and classic Alarms also have different licenses. Only the BZ11 horn license is compatible with both new and classic Alarms. **License** **Description** **Compatible with New Alarms** **Compatible with Classic Alarms** LIC-BX-MB Basic Alarms License for 1 Site ✔️ LIC-BX-MA Advanced Video Alarms License for 1 Site ✔️ LIC-BX-CEL Cellular Backup License for ACC-CEL-LTE-2 ✔️ LIC-BB Basic Alarms License for 1 Address ✔️ LIC-BA Standard Alarms License for 1 Address ✔️ LIC-BV Premium Alarms License for 1 Address ✔️ LIC-CEL Cellular Backup License for ACC-CEL-LTE ✔️ LIC-BZ Horn License for BZ11 ✔️ ✔️ Last updated 17 hours ago Was this helpful? --- # Quick Reference Guide for Verkada Cameras | Verkada Cameras | Verkada Help [](https://help.verkada.com/verkada-cameras/quick-reference-guide-for-verkada-cameras#hardware-installation) Hardware Installation --------------------------------------------------------------------------------------------------------------------------------------- * [Camera datasheets](https://www.verkada.com/docs/?product=videoSecurity&contentType=datasheet) * [Camera setup guides](https://www.verkada.com/docs/?product=videoSecurity&contentType=setupGuide) * [Bandwidth Consumption](https://help.verkada.com/verkada-cameras/camera-specifications/bandwidth-consumption-uplink-requirements-for-video) * [Use External IR Illuminators with Verkada Cameras](https://help.verkada.com/verkada-cameras/hardware-installation/advanced-installation/use-external-ir-illuminators-with-verkada-cameras) [](https://help.verkada.com/verkada-cameras/quick-reference-guide-for-verkada-cameras#configuration-and-setup) Configuration and Setup ------------------------------------------------------------------------------------------------------------------------------------------- * [Add a Device to Your Command Account](https://help.verkada.com/verkada-cameras/configuration-and-setup/add-a-device-to-your-command-organization) * [Camera Network Settings](https://help.verkada.com/verkada-cameras/camera-specifications/camera-network-settings) * [Roles and Permissions for Cameras](https://help.verkada.com/verkada-cameras/configuration-and-setup/roles-and-permissions-for-cameras) * [Manage Your Sites and Subsites](https://help.verkada.com/verkada-cameras/configuration-and-setup/manage-sites-and-subsites) * [View and Edit Camera Settings](https://help.verkada.com/verkada-cameras/configuration-and-setup/view-and-edit-camera-settings) * [Find a Camera’s Serial Number and MAC Address](https://help.verkada.com/verkada-cameras/configuration-and-setup/find-a-cameras-serial-number-and-mac-address) * [Configure Static IP Addresses for Cameras](https://help.verkada.com/verkada-cameras/hardware-installation/advanced-installation/configure-static-ip-addresses-for-cameras) * [Enterprise Bandwidth Manager](https://help.verkada.com/verkada-cameras/hardware-installation/advanced-installation/enterprise-bandwidth-manager) * [Enable Cloud Backup](https://help.verkada.com/verkada-cameras/historical-playback/cloud-backup) [](https://help.verkada.com/verkada-cameras/quick-reference-guide-for-verkada-cameras#streaming) Streaming --------------------------------------------------------------------------------------------------------------- * [Share a Camera’s Live Stream](https://help.verkada.com/verkada-cameras/sharing-video/share-a-cameras-live-stream) * [Share Multiple Cameras](https://help.verkada.com/verkada-cameras/sharing-video/share-multiple-cameras) * [Share Archives](https://help.verkada.com/verkada-cameras/sharing-video/share-archives) [](https://help.verkada.com/verkada-cameras/quick-reference-guide-for-verkada-cameras#events-and-alerts) Events and Alerts ------------------------------------------------------------------------------------------------------------------------------- * [Configure Camera Event Alerts](https://help.verkada.com/verkada-cameras/events-and-alerts/create-camera-event-alerts) * [Manage Alerts Across Verkada Products](https://help.verkada.com/verkada-cameras/events-and-alerts/manage-alerts-across-verkada-products) * [Target and Minimize Your Alerts](https://help.verkada.com/verkada-cameras/events-and-alerts/optimize-your-alerts) * [Sharing Events](https://help.verkada.com/verkada-cameras/events-and-alerts/share-event-alerts) [](https://help.verkada.com/verkada-cameras/quick-reference-guide-for-verkada-cameras#troubleshooting) Troubleshooting --------------------------------------------------------------------------------------------------------------------------- * [Loss of Network Connection for Cameras](https://help.verkada.com/verkada-cameras/troubleshooting/loss-of-network-connection-for-cameras) * [Troubleshoot Offline Camera](https://help.verkada.com/verkada-cameras/troubleshooting/troubleshoot-offline-camera) * [Resolve Issues with Missing Cameras](https://help.verkada.com/verkada-cameras/troubleshooting/resolve-issues-with-missing-cameras) * [Troubleshooting Buffering and Latency](https://help.verkada.com/verkada-cameras/troubleshooting/troubleshooting-buffering-and-latency) * [Resolve Issues with Night Mode](https://help.verkada.com/verkada-cameras/troubleshooting/resolve-issues-with-night-mode) * [Contact Verkada Support](https://help.verkada.com/command/need-help/contact-verkada-support) [](https://help.verkada.com/verkada-cameras/quick-reference-guide-for-verkada-cameras#maintenance) Maintenance ------------------------------------------------------------------------------------------------------------------- * [Clean Your Verkada Dome Camera](https://help.verkada.com/verkada-cameras/maintenance-for-your-camera/clean-your-verkada-dome-camera) * [Verkada Dome Camera Maintenance](https://help.verkada.com/verkada-cameras/maintenance-for-your-camera/verkada-dome-camera-maintenance) * [Waterproof Outdoor Cameras](https://help.verkada.com/verkada-cameras/maintenance-for-your-camera/waterproof-outdoor-cameras) Follow [our blog](https://www.verkada.com/blog/) for all our latest features and announcements! Last updated 1 day ago Was this helpful? --- # Site Planner & Partner Tools | Command | Verkada Help ### [](https://help.verkada.com/command/site-planner-amp-partner-tools#site-planner) Site Planner [Take Site Plan Image Snapshot](https://help.verkada.com/command/site-planner-amp-partner-tools/site-planner/take-site-plan-image-snapshot) [Create Site Plan Walls & Barriers](https://help.verkada.com/command/site-planner-amp-partner-tools/site-planner/create-site-plan-walls-barriers) [Use Site Plan Keyboard Shortcuts](https://help.verkada.com/command/site-planner-amp-partner-tools/site-planner/use-site-plan-keyboard-shortcuts) [Configure Site Planner User Preferences](https://help.verkada.com/command/site-planner-amp-partner-tools/site-planner/configure-site-planner-user-preferences) [Change Site Plan Visibility Options](https://help.verkada.com/command/site-planner-amp-partner-tools/site-planner/change-site-plan-visibility-options) [Export your Bill of Materials](https://help.verkada.com/command/site-planner-amp-partner-tools/site-planner/export-your-bill-of-materials) [Duplicate a Site Plan](https://help.verkada.com/command/site-planner-amp-partner-tools/site-planner/duplicate-a-site-plan) [Share your Site Plan Projects](https://help.verkada.com/command/site-planner-amp-partner-tools/site-planner/share-your-site-plan-projects) [Add Site Planner Locations and Sites](https://help.verkada.com/command/site-planner-amp-partner-tools/site-planner/add-site-planner-locations-and-sites) [Add Products to your Site Plan](https://help.verkada.com/command/site-planner-amp-partner-tools/site-planner/add-products-to-your-site-plan) [Create Site Plan Project](https://help.verkada.com/command/site-planner-amp-partner-tools/site-planner/create-site-plan-project) [Site Planner Homepage Overview](https://help.verkada.com/command/site-planner-amp-partner-tools/site-planner/site-planner-homepage-overview) ### [](https://help.verkada.com/command/site-planner-amp-partner-tools#partner-tools) Partner Tools [Verkada Best Practice Partner Installation Guide](https://help.verkada.com/command/site-planner-amp-partner-tools/partner-tools/verkada-best-practice-partner-installation-guide) [Partner Tools](https://help.verkada.com/command/site-planner-amp-partner-tools/partner-tools/partner-tools) Last updated 16 days ago Was this helpful? --- # Configuration and Setup | Guest | Verkada Help [Send Custom Messages to Guests](https://help.verkada.com/guest/configuration-and-setup/send-custom-messages-to-guests) [Manage Data Retention in Guest](https://help.verkada.com/guest/configuration-and-setup/manage-data-retention-in-guest) [Connect People Lists to Guest](https://help.verkada.com/guest/configuration-and-setup/connect-people-lists-to-guest) [Manage Student Lists](https://help.verkada.com/guest/configuration-and-setup/manage-student-lists) [Deny List Face Match](https://help.verkada.com/guest/configuration-and-setup/deny-list-face-match) [Control Guest Type Visibility](https://help.verkada.com/guest/configuration-and-setup/control-guest-type-visibility) [Manage QR Codes for Mobile Sign-In](https://help.verkada.com/guest/configuration-and-setup/manage-qr-codes-for-mobile-sign-in) [Export Guest Logs](https://help.verkada.com/guest/configuration-and-setup/export-guest-logs) [Identity Document Verification](https://help.verkada.com/guest/configuration-and-setup/identity-document-verification) [Hosts with Guest Types](https://help.verkada.com/guest/configuration-and-setup/hosts-with-guest-types) [Manage Host Lists in Guest](https://help.verkada.com/guest/configuration-and-setup/manage-host-lists-in-guest) [Meraki Wi-Fi Integration for Guest](https://help.verkada.com/guest/configuration-and-setup/meraki-wi-fi-integration-for-guest) [Manage Visitor Access Control Privileges](https://help.verkada.com/guest/configuration-and-setup/manage-visitor-access-control-privileges) [Door Access for Guests](https://help.verkada.com/guest/configuration-and-setup/door-access-for-guests) [Review Security Screening Results](https://help.verkada.com/guest/configuration-and-setup/review-security-screening-results) [Security Screening Settings](https://help.verkada.com/guest/configuration-and-setup/security-screening-settings) [School Guest Types](https://help.verkada.com/guest/configuration-and-setup/school-guest-types) [Face Pass for Guest](https://help.verkada.com/guest/configuration-and-setup/face-pass-for-guest) [Design a Visitor Badge in Guest](https://help.verkada.com/guest/configuration-and-setup/design-a-visitor-badge-in-guest) [Guest Questionnaires](https://help.verkada.com/guest/configuration-and-setup/guest-questionnaires) [Pin Guest Check-in Steps and Configure Guest Passes](https://help.verkada.com/guest/configuration-and-setup/pin-guest-check-in-steps-and-configure-guest-passes) [Approved Lists for Guest](https://help.verkada.com/guest/configuration-and-setup/approved-lists-for-guest) [Configure Guest Types](https://help.verkada.com/guest/configuration-and-setup/configure-guest-types) [Set up a Guest Tablet](https://help.verkada.com/guest/configuration-and-setup/set-up-a-guest-tablet) [Guest Documents](https://help.verkada.com/guest/configuration-and-setup/guest-documents) [View and Edit Guest Settings](https://help.verkada.com/guest/configuration-and-setup/view-and-edit-guest-settings) [Guest Sites](https://help.verkada.com/guest/configuration-and-setup/guest-sites) [Guest App Integrations](https://help.verkada.com/guest/configuration-and-setup/guest-app-integrations) [Customize Guest Deny Lists](https://help.verkada.com/guest/configuration-and-setup/customize-guest-deny-lists) [Manage Multiple Languages for Guest](https://help.verkada.com/guest/configuration-and-setup/manage-multiple-languages-for-guest) [Guest Employee Portal](https://help.verkada.com/guest/configuration-and-setup/guest-employee-portal) [Guest Security Screening](https://help.verkada.com/guest/configuration-and-setup/guest-security-screening) [Add Cameras and Doors in Verkada Guest](https://help.verkada.com/guest/configuration-and-setup/add-cameras-and-doors-in-verkada-guest) ### [](https://help.verkada.com/guest/configuration-and-setup#printers) Printers [Connect a Brother Printer with Bluetooth](https://help.verkada.com/guest/configuration-and-setup/printers/connect-a-brother-printer-with-bluetooth) [Connect a Printer to Verkada Guest using an IP Connection](https://help.verkada.com/guest/configuration-and-setup/printers/connect-a-printer-to-verkada-guest-using-an-ip-connection) [Connect a Brother Printer with AirPrint for Guest](https://help.verkada.com/guest/configuration-and-setup/printers/connect-a-brother-printer-with-airprint-for-guest) [Two-Tone Printing for the Brother Printer](https://help.verkada.com/guest/configuration-and-setup/printers/two-tone-printing-for-the-brother-printer) [Epson Printer Setup Guide](https://help.verkada.com/guest/configuration-and-setup/printers/epson-printer-setup-guide) [Brother Printer Setup Guide](https://help.verkada.com/guest/configuration-and-setup/printers/brother-printer-setup-guide) ### [](https://help.verkada.com/guest/configuration-and-setup#school-integrations) School Integrations [Integrate ClassLink with Verkada Guest](https://help.verkada.com/guest/configuration-and-setup/school-integrations/integrate-classlink-with-verkada-guest) [Integrate Clever with Verkada Guest](https://help.verkada.com/guest/configuration-and-setup/school-integrations/integrate-clever-with-verkada-guest) ### [](https://help.verkada.com/guest/configuration-and-setup#guest-events) Guest Events [Sign in Invited Guests at an Intercom](https://help.verkada.com/guest/configuration-and-setup/guest-events/sign-in-invited-guests-at-an-intercom) [Verkada Guest Google Calendar Add-on](https://help.verkada.com/guest/configuration-and-setup/guest-events/verkada-guest-google-calendar-add-on) [RSVP Links for Guest](https://help.verkada.com/guest/configuration-and-setup/guest-events/rsvp-links-for-guest) [Guest Events](https://help.verkada.com/guest/configuration-and-setup/guest-events/guest-events) [Create Guest Events with Calendar Shortcuts](https://help.verkada.com/guest/configuration-and-setup/guest-events/create-guest-events-with-calendar-shortcuts) [Manage Events from the Employee Portal](https://help.verkada.com/guest/configuration-and-setup/guest-events/manage-events-from-the-employee-portal) Last updated 15 days ago Was this helpful? --- # Camera Network Settings | Verkada Cameras | Verkada Help This article outlines the required network settings that your Verkada camera needs to communicate with [Verkada Command](https://help.verkada.com/command/get-started-with-verkada-command) . For more information on the required network settings for other Verkada product lines see [Required Network Settings](https://help.verkada.com/command/required-network-settings) . Verkada devices are incompatible with LANs that require proxy servers or Secure Socket Layer (SSL)/Transport Layer Security (TLS) inspection. If either is in use, a bypass for all Verkada devices must be implemented for Verkada devices to communicate with Verkada Command. [](https://help.verkada.com/verkada-cameras/camera-specifications/camera-network-settings#status-led) Status LED --------------------------------------------------------------------------------------------------------------------- A blinking blue status LED or an alternating blue and amber status LED on the front of the physical camera indicates that the camera is not communicating with Command. See [Camera LED Status Indicators](https://help.verkada.com/verkada-cameras/camera-specifications/camera-led-status-indicators) for more information. If you see this behavior, verify that the network is configured according to the camera’s requirements. If the issue persists, contact [Verkada Support](https://help.verkada.com/command/need-help/contact-verkada-support) . If the camera is offline and still has power, it will continue to record. Once the camera is reconnected to Command, the video will be available. Once a camera comes online, it can take a few hours for the video footage to sync, and the duration depends largely on how long the camera has been offline. [](https://help.verkada.com/verkada-cameras/camera-specifications/camera-network-settings#ip-address) IP address --------------------------------------------------------------------------------------------------------------------- Cameras must be assigned an IPv4 address to communicate on the LAN and to Verkada Command. Cameras use Dynamic Host Configuration Protocol (DHCP) and User Datagram Protocol (UDP) to obtain their IP addresses and network configurations. If you require your camera to have a specific IP address, create a DHCP reservation using the device’s Media Access Control (MAC) address (found on the device’s label). [](https://help.verkada.com/verkada-cameras/camera-specifications/camera-network-settings#domain-name-system) Domain Name System ------------------------------------------------------------------------------------------------------------------------------------- Cameras use the DNS server to resolve Verkada’s fully qualified domain names (FQDN) to IP addresses to communicate with them. Your DHCP server tells the camera where the DNS server is on the network and the camera communicates using UDP port 53. DNS over HTTPS (DoH) is currently not supported. [](https://help.verkada.com/verkada-cameras/camera-specifications/camera-network-settings#power) Power ----------------------------------------------------------------------------------------------------------- Cameras are powered through Power over Ethernet (PoE). This means the network switch needs to provide power to the camera, or a PoE injector needs to be utilized. For specifics on power requirements, see the [camera’s datasheet](https://www.verkada.com/docs/?product=videoSecurity&contentType=datasheet) . [](https://help.verkada.com/verkada-cameras/camera-specifications/camera-network-settings#firewall-settings) Firewall settings ----------------------------------------------------------------------------------------------------------------------------------- Verkada cameras require access to many endpoints to ensure they can communicate with Command and all features will be accessible. Many customers may want to allow the cameras to communicate with the general required endpoints. These are the general domains to allow, **applicable for all organization-regions**: Copy *:4100 - TCP/UDP on local network *.verkada.com - UDP/123 + TCP+UDP/443 time.cloudflare.com - TCP/4460 + UDP/123 *.amazonaws.com - TCP+UDP/443 If you prefer a more granular allowlist, you can add both full FQDNs and wildcard domains to your firewall rules based on the region where your devices are located. Your region is selected when you [create an organization](https://help.verkada.com/command/get-started-with-verkada-command) in Command. ### [](https://help.verkada.com/verkada-cameras/camera-specifications/camera-network-settings#region-united-states) Region: United States Copy *:4100 - TCP/UDP on local network (for local streaming) api.control.verkada.com - TCP+UDP/443 api-ga.control.verkada.com - TCP+UDP/443 api.global-prod.control.verkada.com - TCP+UDP/443 firmware.control.verkada.com - TCP+UDP/443 index.control.verkada.com - TCP+UDP/443 relay.control.verkada.com - TCP+UDP/443 relay.global-prod.control.verkada.com - TCP+UDP/443 time.control.verkada.com - UDP/123 update.control.verkada.com - TCP+UDP/443 vconductor.global-prod.command.verkada.com - TCP+UDP/443 *.vnetcap.control.verkada.com - TCP/443 *.vstream.vnetcap.control.verkada.com - TCP/443 *.vsubmit.vnetcap.control.verkada.com - TCP/443 *.vprovision.vnetcap.control.verkada.com - TCP/443 *.vproxy.vnetcap.control.verkada.com - TCP/443 *.kinesisvideo.us-west-2.amazonaws.com - TCP+UDP/443 s3.ap-southeast-2.amazonaws.com - TCP/443†* s3.ca-central-1.amazonaws.com - TCP/443†* s3.eu-west-1.amazonaws.com - TCP/443†* s3.us-west-2.amazonaws.com - TCP/443† time.cloudflare.com - TCP/4460 + UDP/123 ### [](https://help.verkada.com/verkada-cameras/camera-specifications/camera-network-settings#region-europe) Region: Europe Copy *:4100 - TCP/UDP on local network (for local streaming) api-ga.control.verkada.com - TCP+UDP/443 api.global-prod.control.verkada.com - TCP+UDP/443 api.prod2.control.verkada.com - TCP+UDP/443 index.prod2.control.verkada.com - TCP+UDP/443 relay.global-prod.control.verkada.com - TCP+UDP/443 relay.prod2.control.verkada.com - TCP+UDP/443 time.cloudflare.com - TCP/4460 + UDP/123 time.control.verkada.com - UDP/123 update.control.verkada.com - TCP+UDP/443 vconductor.global-prod.command.verkada.com - TCP+UDP/443 vconductor.prod2.command.verkada.com - TCP+UDP/443 *.kinesisvideo.eu-west-1.amazonaws.com - TCP+UDP/443 s3.eu-west-1.amazonaws.com - TCP/443† ### [](https://help.verkada.com/verkada-cameras/camera-specifications/camera-network-settings#region-australia) Region: Australia Copy *:4100 - TCP/UDP on LAN (for local streaming) api-ga.control.verkada.com - TCP+UDP/443 api.global-prod.control.verkada.com - TCP+UDP/443 api.prod-ap-syd.control.verkada.com - TCP+UDP/443 index.prod.ap.syd.control.verkada.com - TCP+UDP/443 relay.global-prod.control.verkada.com - TCP+UDP/443 relay.prod-ap-syd.control.verkada.com - TCP+UDP/443 time.cloudflare.com - TCP/4460 + UDP/123 time.control.verkada.com - UDP/123 update.control.verkada.com - TCP+UDP/443 vconductor.global-prod.command.verkada.com - TCP+UDP/443 vconductor.prod.ap.syd.command.verkada.com - TCP+UDP/443 *.kinesisvideo.ap-southeast-2.amazonaws.com - TCP+UDP/443 s3.ap-southeast-2.amazonaws.com - TCP/443† * * * **Footnotes:** * †Required for cloud backup. * \*Only required if your [data storage location](https://help.verkada.com/command/data-protection-and-security/set-a-default-or-camera-specific-location-for-image-and-video-data-storage-and-processing) is set outside the United States. Use the [Verkada Network Tester](https://network-tester.support.verkada.com/) to verify your devices can connect to Verkada Command. Select your region and the **Cameras** product type to run the check. The following endpoints must be allowed on your network for the test to work: * speed.cloudflare.com * network-tester.support.verkada.com **Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=5pRUeH_bhw0) . Last updated 1 day ago Was this helpful? --- # Configuration and Setup | Verkada Cameras | Verkada Help [Configure External Contacts](https://help.verkada.com/verkada-cameras/configuration-and-setup/configure-external-contacts) [Verkada Operations User Guide](https://help.verkada.com/verkada-cameras/configuration-and-setup/verkada-operations-user-guide) [Door Shortcuts](https://help.verkada.com/verkada-cameras/configuration-and-setup/door-shortcuts) [Camera Smart Lists](https://help.verkada.com/verkada-cameras/configuration-and-setup/camera-smart-lists) [Camera Replacement](https://help.verkada.com/verkada-cameras/configuration-and-setup/camera-replacement) [Configure Port-based Device Authentication for Cameras](https://help.verkada.com/verkada-cameras/configuration-and-setup/configure-port-based-device-authentication-for-cameras) [Remove Enterprise Controlled Encryption](https://help.verkada.com/verkada-cameras/configuration-and-setup/remove-enterprise-controlled-encryption) [Enterprise Controlled Encryption Device & Feature Compatibility](https://help.verkada.com/verkada-cameras/configuration-and-setup/enterprise-controlled-encryption-device-feature-compatibility) [Create a Person of Interest](https://help.verkada.com/verkada-cameras/configuration-and-setup/create-a-person-of-interest) [Selective Face Blur for Archives](https://help.verkada.com/verkada-cameras/configuration-and-setup/selective-face-blur-for-archives) [Set up Contextual Triggers for a PTZ Camera](https://help.verkada.com/verkada-cameras/configuration-and-setup/set-up-contextual-triggers-for-a-ptz-camera) [Camera Shortcuts](https://help.verkada.com/verkada-cameras/configuration-and-setup/camera-shortcuts) [Roles and Permissions for Cameras](https://help.verkada.com/verkada-cameras/configuration-and-setup/roles-and-permissions-for-cameras) [Use LLDP with Cameras](https://help.verkada.com/verkada-cameras/configuration-and-setup/use-lldp-with-cameras) [Incident Management](https://help.verkada.com/verkada-cameras/configuration-and-setup/incident-management) [Set Up Sentry Mode on a PTZ camera](https://help.verkada.com/verkada-cameras/configuration-and-setup/set-up-sentry-mode-on-a-ptz-camera) [Camera Notes](https://help.verkada.com/verkada-cameras/configuration-and-setup/camera-notes) [People Heat Maps for Floor Plans](https://help.verkada.com/verkada-cameras/configuration-and-setup/people-heat-maps-for-floor-plans) [Optimize Low Bandwidth Mode](https://help.verkada.com/verkada-cameras/configuration-and-setup/optimize-low-bandwidth-mode) [Enable Wi-Fi on Select Verkada Cameras](https://help.verkada.com/verkada-cameras/configuration-and-setup/enable-wi-fi-on-select-verkada-cameras) [Camera Deployment](https://help.verkada.com/verkada-cameras/configuration-and-setup/camera-deployment) [Wide Dynamic Range](https://help.verkada.com/verkada-cameras/configuration-and-setup/wide-dynamic-range) [Privacy Regions](https://help.verkada.com/verkada-cameras/configuration-and-setup/privacy-regions) [Configure License Plate Recognition](https://help.verkada.com/verkada-cameras/configuration-and-setup/configure-license-plate-recognition) [Navigate the Command Mobile App](https://help.verkada.com/verkada-cameras/configuration-and-setup/navigate-the-command-mobile-app) [Enable Face Blur on Verkada Cameras](https://help.verkada.com/verkada-cameras/configuration-and-setup/enable-face-blur-on-verkada-cameras) [Find a Camera's Serial Number and MAC Address](https://help.verkada.com/verkada-cameras/configuration-and-setup/find-a-cameras-serial-number-and-mac-address) [Calibrate Cameras for Floorplan Heat Maps](https://help.verkada.com/verkada-cameras/configuration-and-setup/calibrate-cameras-for-floorplan-heat-maps) [Devices Page Overview](https://help.verkada.com/verkada-cameras/configuration-and-setup/devices-page-overview) [Delete a Camera](https://help.verkada.com/verkada-cameras/configuration-and-setup/delete-a-camera) [Use Optical Zoom and Auto Focus](https://help.verkada.com/verkada-cameras/configuration-and-setup/use-optical-zoom-and-auto-focus) [Change the Location of a Camera](https://help.verkada.com/verkada-cameras/configuration-and-setup/change-the-location-of-a-camera) [View and Edit Camera Settings](https://help.verkada.com/verkada-cameras/configuration-and-setup/view-and-edit-camera-settings) [Change a Camera's Orientation](https://help.verkada.com/verkada-cameras/configuration-and-setup/change-a-cameras-orientation) [Manage Sites and Subsites](https://help.verkada.com/verkada-cameras/configuration-and-setup/manage-sites-and-subsites) [Schedule Camera Firmware Updates](https://help.verkada.com/verkada-cameras/configuration-and-setup/schedule-camera-firmware-updates) [Add a Device to Your Command Organization](https://help.verkada.com/verkada-cameras/configuration-and-setup/add-a-device-to-your-command-organization) Last updated 1 month ago Was this helpful? --- # End-of-Sale Product Updates | Command | Verkada Help [End-of-Sale Announcement for CH52-E](https://help.verkada.com/command/end-of-sale-product-updates/end-of-sale-announcement-for-ch52-e) [End-of-Sale Announcement for CD42-F & CD52-F](https://help.verkada.com/command/end-of-sale-product-updates/end-of-sale-announcement-for-cd42-f-cd52-f) [End-of-Sale Announcement for ACCX-TBL-2](https://help.verkada.com/command/end-of-sale-product-updates/end-of-sale-announcement-for-accx-tbl-2) [End-of-Sale Announcement for CF81-E](https://help.verkada.com/command/end-of-sale-product-updates/end-of-sale-announcement-for-cf81-e) [End-of-Sale Announcement for CD42 & CD52](https://help.verkada.com/command/end-of-sale-product-updates/end-of-sale-announcement-for-cd42-cd52) [End-of-Sale Announcement for AD33](https://help.verkada.com/command/end-of-sale-product-updates/end-of-sale-announcement-for-ad33) [End-of-Sale Announcement for CD62](https://help.verkada.com/command/end-of-sale-product-updates/end-of-sale-announcement-for-cd62) [End-of-Sale Announcement for TD52](https://help.verkada.com/command/end-of-sale-product-updates/end-of-sale-announcement-for-td52) [End-of-Sale Announcement for BR34 Wireless Glass Break Sensor](https://help.verkada.com/command/end-of-sale-product-updates/end-of-sale-announcement-for-br34-wireless-glass-break-sensor) [End-of-Sale Announcement for ACCX-TBL-1](https://help.verkada.com/command/end-of-sale-product-updates/end-of-sale-announcement-for-accx-tbl-1) [End-of-Sale Announcement for CM41-S](https://help.verkada.com/command/end-of-sale-product-updates/end-of-sale-announcement-for-cm41-s) [End-of-Sale Announcement for Classic Alarms (US only)](https://help.verkada.com/command/end-of-sale-product-updates/end-of-sale-announcement-for-classic-alarms-us-only) [End-of-Sale Announcement for AC41](https://help.verkada.com/command/end-of-sale-product-updates/end-of-sale-announcement-for-ac41) [End-of-Sale Announcement for BC51](https://help.verkada.com/command/end-of-sale-product-updates/end-of-sale-announcement-for-bc51) [End-of-Sale Announcement for CM41](https://help.verkada.com/command/end-of-sale-product-updates/end-of-sale-announcement-for-cm41) [End-of-Sale Announcement for AD32](https://help.verkada.com/command/end-of-sale-product-updates/end-of-sale-announcement-for-ad32) [End-of-Sale Announcement for CB51 & CB61](https://help.verkada.com/command/end-of-sale-product-updates/end-of-sale-announcement-for-cb51-cb61) [End-of-Sale Announcement for SV11](https://help.verkada.com/command/end-of-sale-product-updates/end-of-sale-announcement-for-sv11) [End-of-Sale Announcement for D30 & CM61](https://help.verkada.com/command/end-of-sale-product-updates/end-of-sale-announcement-for-d30-cm61) [End-of-Sale Announcement for AD31](https://help.verkada.com/command/end-of-sale-product-updates/end-of-sale-announcement-for-ad31) [End-of-Sale Products & Policy Overview](https://help.verkada.com/command/end-of-sale-product-updates/end-of-sale-products-policy-overview) [End-of-Sale Announcement for CD41](https://help.verkada.com/command/end-of-sale-product-updates/end-of-sale-announcement-for-cd41) [End-of-Sale Announcement for D40 & D80](https://help.verkada.com/command/end-of-sale-product-updates/end-of-sale-announcement-for-d40-d80) [End-of-Sale Announcement for CD51 and CD61](https://help.verkada.com/command/end-of-sale-product-updates/end-of-sale-announcement-for-cd51-and-cd61) [End-of-Sale Announcement for D50](https://help.verkada.com/command/end-of-sale-product-updates/end-of-sale-announcement-for-d50) Last updated 29 days ago Was this helpful? --- # Configuration and Setup | Access Control | Verkada Help [Attendance Analytics](https://help.verkada.com/access-control/configuration-and-setup/attendance-analytics) [Manage Lockdowns and Scenarios via API](https://help.verkada.com/access-control/configuration-and-setup/manage-lockdowns-and-scenarios-via-api) [Integrate Suprema's BioStation3 Readers with Verkada Access Control](https://help.verkada.com/access-control/configuration-and-setup/integrate-supremas-biostation3-readers-with-verkada-access-control) [Visitor Access & Visit Access Type](https://help.verkada.com/access-control/configuration-and-setup/visitor-access-visit-access-type) [Verkada Integration with Atrium](https://help.verkada.com/access-control/configuration-and-setup/verkada-integration-with-atrium) [Favorite Doors in Verkada Pass App](https://help.verkada.com/access-control/configuration-and-setup/favorite-doors-in-verkada-pass-app) [Multi-factor Authentication (MFA) Codes](https://help.verkada.com/access-control/configuration-and-setup/multi-factor-authentication-mfa-codes) [Legacy Access Control Roles](https://help.verkada.com/access-control/configuration-and-setup/legacy-access-control-roles) [Credential Auto-Deactivate](https://help.verkada.com/access-control/configuration-and-setup/credential-auto-deactivate) [Mobile NFC - Add Verkada Badge to Apple Wallet](https://help.verkada.com/access-control/configuration-and-setup/mobile-nfc-add-verkada-badge-to-apple-wallet) [Mobile NFC - Command Management](https://help.verkada.com/access-control/configuration-and-setup/mobile-nfc-command-management) [Mobile NFC - Add to Android Pass App](https://help.verkada.com/access-control/configuration-and-setup/mobile-nfc-add-to-android-pass-app) [Supervised Wiring for Access Control](https://help.verkada.com/access-control/configuration-and-setup/supervised-wiring-for-access-control) [Manage Doors via API](https://help.verkada.com/access-control/configuration-and-setup/manage-doors-via-api) [Assa Abloy IN120/IN220 Setup](https://help.verkada.com/access-control/configuration-and-setup/assa-abloy-in120in220-setup) [Import Access Control Users - CSV](https://help.verkada.com/access-control/configuration-and-setup/import-access-control-users-csv) [Cross-Device Local Connections for Access Control](https://help.verkada.com/access-control/configuration-and-setup/cross-device-local-connections-for-access-control) [Import and Export Credentials with CSV Files](https://help.verkada.com/access-control/configuration-and-setup/import-and-export-credentials-with-csv-files) [Create a Person of Interest from an Access User](https://help.verkada.com/access-control/configuration-and-setup/create-a-person-of-interest-from-an-access-user) [Configure an AUX Output on an Access Controller](https://help.verkada.com/access-control/configuration-and-setup/configure-an-aux-output-on-an-access-controller) [Secure Access Control Areas with Anti-Passback](https://help.verkada.com/access-control/configuration-and-setup/secure-access-control-areas-with-anti-passback) [Configure Access Control Areas](https://help.verkada.com/access-control/configuration-and-setup/configure-access-control-areas) [Power I/O on the AC12](https://help.verkada.com/access-control/configuration-and-setup/power-io-on-the-ac12) [Keypad Pincode Formats](https://help.verkada.com/access-control/configuration-and-setup/keypad-pincode-formats) [Configure a Door with a Motor for Accessibility](https://help.verkada.com/access-control/configuration-and-setup/configure-a-door-with-a-motor-for-accessibility) [Add and View Doors on Floor Plans](https://help.verkada.com/access-control/configuration-and-setup/add-and-view-doors-on-floor-plans) [Access Control Subsites](https://help.verkada.com/access-control/configuration-and-setup/access-control-subsites) [First Person In Feature](https://help.verkada.com/access-control/configuration-and-setup/first-person-in-feature) [InformaCast Access Control Integration](https://help.verkada.com/access-control/configuration-and-setup/informacast-access-control-integration) [Roll Call Reports](https://help.verkada.com/access-control/configuration-and-setup/roll-call-reports) [Commission Access Control Cards](https://help.verkada.com/access-control/configuration-and-setup/commission-access-control-cards) [Upload Bulk Images](https://help.verkada.com/access-control/configuration-and-setup/upload-bulk-images) [Print Access Control Badges](https://help.verkada.com/access-control/configuration-and-setup/print-access-control-badges) [Remove a Card Reader](https://help.verkada.com/access-control/configuration-and-setup/remove-a-card-reader) [AX11 Event Bridge](https://help.verkada.com/access-control/configuration-and-setup/ax11-event-bridge) [Configure the AX11 IO Controller](https://help.verkada.com/access-control/configuration-and-setup/configure-the-ax11-io-controller) [Use SCIM for Access Groups](https://help.verkada.com/access-control/configuration-and-setup/use-scim-for-access-groups) [Assign a User Access to a Door](https://help.verkada.com/access-control/configuration-and-setup/assign-a-user-access-to-a-door) [Bluetooth Unlock](https://help.verkada.com/access-control/configuration-and-setup/bluetooth-unlock) [Enable Two-Factor Entry with Access Control](https://help.verkada.com/access-control/configuration-and-setup/enable-two-factor-entry-with-access-control) [Move Access Controllers to Other Sites](https://help.verkada.com/access-control/configuration-and-setup/move-access-controllers-to-other-sites) [Verkada Pass App](https://help.verkada.com/access-control/configuration-and-setup/verkada-pass-app) [Add a Camera Live Feed to a Door](https://help.verkada.com/access-control/configuration-and-setup/add-a-camera-live-feed-to-a-door) [Enable and Configure REX inputs](https://help.verkada.com/access-control/configuration-and-setup/enable-and-configure-rex-inputs) [OSDP and Wiegand](https://help.verkada.com/access-control/configuration-and-setup/osdp-and-wiegand) [Override Schedule Access to a Door](https://help.verkada.com/access-control/configuration-and-setup/override-schedule-access-to-a-door) [Unlock a Door from a 3rd-Party Intercom System or Button](https://help.verkada.com/access-control/configuration-and-setup/unlock-a-door-from-a-3rd-party-intercom-system-or-button) [Bluetooth Unlock with Geofencing](https://help.verkada.com/access-control/configuration-and-setup/bluetooth-unlock-with-geofencing) [Emergency Lockdown](https://help.verkada.com/access-control/configuration-and-setup/emergency-lockdown) [View Access Controllers in Command](https://help.verkada.com/access-control/configuration-and-setup/view-access-controllers-in-command) [Wire a Door to an AC41 Cassette](https://help.verkada.com/access-control/configuration-and-setup/wire-a-door-to-an-ac41-cassette) [Decommission an Access Controller](https://help.verkada.com/access-control/configuration-and-setup/decommission-an-access-controller) [Access Control Reports](https://help.verkada.com/access-control/configuration-and-setup/access-control-reports) [Suspend and Delete Access Users](https://help.verkada.com/access-control/configuration-and-setup/suspend-and-delete-access-users) [Move Doors between Access Controllers](https://help.verkada.com/access-control/configuration-and-setup/move-doors-between-access-controllers) [Remove a Door from Verkada Access](https://help.verkada.com/access-control/configuration-and-setup/remove-a-door-from-verkada-access) [View Access Control Doors](https://help.verkada.com/access-control/configuration-and-setup/view-access-control-doors) [Add a User to the Verkada Access System](https://help.verkada.com/access-control/configuration-and-setup/add-a-user-to-the-verkada-access-system) [Add and Modify Access Levels](https://help.verkada.com/access-control/configuration-and-setup/add-and-modify-access-levels) [Add and Modify Access Groups](https://help.verkada.com/access-control/configuration-and-setup/add-and-modify-access-groups) [Add a Door to an Access Controller](https://help.verkada.com/access-control/configuration-and-setup/add-a-door-to-an-access-controller) [Configure a Door in Command](https://help.verkada.com/access-control/configuration-and-setup/configure-a-door-in-command) [Add an Access Controller to Command](https://help.verkada.com/access-control/configuration-and-setup/add-an-access-controller-to-command) ### [](https://help.verkada.com/access-control/configuration-and-setup#scheduling) Scheduling [Door Exception Calendars](https://help.verkada.com/access-control/configuration-and-setup/scheduling/door-exception-calendars) [Double Badge to Override a Door's Schedule](https://help.verkada.com/access-control/configuration-and-setup/scheduling/double-badge-to-override-a-doors-schedule) [Schedule Firmware Updates for Access Control Hardware](https://help.verkada.com/access-control/configuration-and-setup/scheduling/schedule-firmware-updates-for-access-control-hardware) [Save Reports and Schedule Automatic Delivery](https://help.verkada.com/access-control/configuration-and-setup/scheduling/save-reports-and-schedule-automatic-delivery) [Door Schedules and Exceptions](https://help.verkada.com/access-control/configuration-and-setup/scheduling/door-schedules-and-exceptions) [Access Level Schedules and Exceptions](https://help.verkada.com/access-control/configuration-and-setup/scheduling/access-level-schedules-and-exceptions) Last updated 15 days ago Was this helpful? --- # Contact Verkada Support | Command | Verkada Help Your Verkada license includes enterprise support. Verkada Support is available 24/7 via phone or [live chat](https://help.verkada.com/command/need-help/contact-verkada-support#h_926781db34) . * * * [](https://help.verkada.com/command/need-help/contact-verkada-support#contact-verkada-support) Contact Verkada Support --------------------------------------------------------------------------------------------------------------------------- Before you contact Verkada Support, it is best to have a support token ready. See [Enable Support Access](https://help.verkada.com/command/need-help/enable-support-access) for more information on creating a support token. ### [](https://help.verkada.com/command/need-help/contact-verkada-support#command-navigation) Command navigation 1 #### [](https://help.verkada.com/command/need-help/contact-verkada-support#log-in-to-verkada-command) Log in to Verkada [Command](http://command.verkada.com/login) . 2 #### [](https://help.verkada.com/command/need-help/contact-verkada-support#at-the-bottom-left-click-greater-than-contact-us) At the bottom left, click **\>** **Contact Us**. 3 #### [](https://help.verkada.com/command/need-help/contact-verkada-support#connect-with) Connect with: * Verkada Support via live chat or phone (available 24/7). * Verkada Sales Representative via email or phone listed for your organization. ### [](https://help.verkada.com/command/need-help/contact-verkada-support#admin-page) Admin page 1 #### [](https://help.verkada.com/command/need-help/contact-verkada-support#in-verkada-command-go-to-all-products-greater-than-admin) In Verkada Command, go to **All Products** > **Admin** . 2 #### [](https://help.verkada.com/command/need-help/contact-verkada-support#in-the-left-navigation-click-support) In the left navigation, click **Support** . 3 #### [](https://help.verkada.com/command/need-help/contact-verkada-support#connect-with-1) Connect with: * Verkada Support via live chat or phone (available 24/7). * Verkada Sales Representative via email or phone listed for your organization. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F705858581-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FNRq5qDDjsYNxwNzF1bcB%252Fuploads%252Fgit-blob-f9813c257091ab5a81e3000fc80ac60c98362ada%252F8de2072e96d98dae68554fe0e3544939fc254b7e.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=14843f59&sv=2) ### [](https://help.verkada.com/command/need-help/contact-verkada-support#command-app) Command app 1 #### [](https://help.verkada.com/command/need-help/contact-verkada-support#open-your-verkada-command-app) Open your Verkada Command app. 2 #### [](https://help.verkada.com/command/need-help/contact-verkada-support#in-the-top-left-click) In the top left, click . 3 #### [](https://help.verkada.com/command/need-help/contact-verkada-support#at-the-bottom-tap-help-greater-than-live-chat) At the bottom, tap **Help > Live Chat** **.** a. Tap **Messages** to open an existing case. b. Tap **Send us a Message** to start a new chat. * * * ### [](https://help.verkada.com/command/need-help/contact-verkada-support#verkada-support-phone-numbers) Verkada Support phone numbers * North America: +1 (650) 514-2500 * Latin America: +52 55 9990 8275 * Europe: +44 (0)20 3048 6050 * Asia / Pacific: +61 (2725) 99300 Last updated 22 days ago Was this helpful? --- # Enable Support Access | Command | Verkada Help [Verkada Support](https://help.verkada.com/command/need-help/contact-verkada-support) may request access to your Verkada Command account to assist with troubleshooting. Any action taken by Verkada Support in your account is included in your [organization audit log](https://help.verkada.com/command/organization-wide-settings/manage-and-view-audit-logs) . [](https://help.verkada.com/command/need-help/enable-support-access#enable-support-access) Enable support access --------------------------------------------------------------------------------------------------------------------- Org Admins, Site Admins, and Access Site Admins can generate and share a support access token to allow Verkada Support to access their accounts. 1 **In Verkada Command, go to All Products > Admin .** 2 **In the left navigation, click Support .** 3 **Select Enable Support Access.** 4 **Toggle on Enable Support Access and configure these additional settings as needed:** a. [Access Duration](https://help.verkada.com/command/need-help/enable-support-access#h_317ed2f7e3) b. [Access Token](https://help.verkada.com/command/need-help/enable-support-access#h_31ecb633d6) c. [Enable Video and Image Access](https://help.verkada.com/command/need-help/enable-support-access#h_f0a68673bc) d. [Limit Access to Sites](https://help.verkada.com/command/need-help/enable-support-access#h_cdd8b3a3a9) ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F705858581-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FNRq5qDDjsYNxwNzF1bcB%252Fuploads%252Fgit-blob-7753a0d4f739c706e9db9dee94f38fa476caee9c%252Fed162a783425f6aa084010d700e99871eb006bdb.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=ac79573e&sv=2) **Note:** Verkada Support **does not** automatically gain access to your account when you enable an access token. You will need to open a support case and share this token with them before they can access your account. ### [](https://help.verkada.com/command/need-help/enable-support-access#access-duration) Access duration The support access duration is set to auto-expire after 24 hours by default. Admins have the option to extend access for up to 90 days. ### [](https://help.verkada.com/command/need-help/enable-support-access#access-token) Access token Access tokens are unique to each admin user account and must be provided to Verkada Support before they can access your account. **Note**: The access token grants the same permissions as the account that generated it. Verkada Support will have access to the same devices and settings that the active user has. If **Enable Video and Image Access** is toggled on, Verkada Support is able to see video and image data. ### [](https://help.verkada.com/command/need-help/enable-support-access#video-and-image-access) Video and image access Verkada Support does not have access to footage, thumbnails, archives, or audio by default. This means that Verkada Support can’t view images, video, or audio, unless you explicitly grant permission. ### [](https://help.verkada.com/command/need-help/enable-support-access#limit-access-to-sites) Limit access to sites Org Admins can select the sites they want to grant Verkada Support access to for enhanced privacy. 1 **From the Enable Support Access page, toggle on Limit Access to Sites.** 2 **Select the site(s) you want Verkada Support to be able to access.** 3 **Click Done when finished.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F705858581-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FNRq5qDDjsYNxwNzF1bcB%252Fuploads%252Fgit-blob-a02947fccf56fe433cc81d337c07965b2df348d6%252Ff005a5a41448f84af5a4b60016f5cdc1b50508e6.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=7b3102c7&sv=2) **Note:** Verkada Support will not be able to access any sites within the organization if this setting is toggled on and no sites are selected. [](https://help.verkada.com/command/need-help/enable-support-access#revoke-support-access) Revoke support access --------------------------------------------------------------------------------------------------------------------- Verkada Support will immediately lose access to your account when the access token duration expires. You can end access at any time by revoking the access token. 1 **In Verkada Command, go to All Products > Admin .** 2 **In the left navigation, click Support .** 3 **Select Enable Support Access.** 4 **Toggle off Enable Support Access.** 5 **Click Revoke to confirm.** [](https://help.verkada.com/command/need-help/enable-support-access#enable-support-access-from-the-command-app) Enable support access from the Command app --------------------------------------------------------------------------------------------------------------------------------------------------------------- 1 **Open the Verkada Command app.** 2 **In the top left, click .** 3 **In the bottom left, click Help > Support Token.** 4 **On Support Access click Enable.** 5 **Configure these settings as needed:** a. [Access Duration](https://help.verkada.com/command/need-help/enable-support-access#h_317ed2f7e3) b. [Access Token](https://help.verkada.com/command/need-help/enable-support-access#h_31ecb633d6) c. [Enable Video and Image Access](https://help.verkada.com/command/need-help/enable-support-access#h_f0a68673bc) d. [Limit Access to Sites](https://help.verkada.com/command/need-help/enable-support-access#h_cdd8b3a3a9) * * * **Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=TbR7z6Ub-fI) . Last updated 22 hours ago Was this helpful? --- # Add Cellular Gateway to Command - Government Solutions | Government Solutions | Verkada Help You need to add your gateway to a standard (non-Government Solutions) Command organization to update before you can commission it in a Government Solutions organization. You must create a [Verkada Command account](https://command.verkada.com/register) and log in with [Org Admin](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) permissions to activate and configure a gateway. * * * [](https://help.verkada.com/government-solutions/configuration-and-setup/add-cellular-gateway-to-command-government-solutions#claim-your-gateway) Claim your gateway ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 1 **Follow the steps in** [**Add Cellular Gateway to Command**](https://help.verkada.com/connectivity/configuration-and-setup/add-cellular-gateway-to-command) **to add your gateway to a standard (non-Government Solutions) Command organization.** 2 **Allow the gateway to update to the latest firmware version.** 3 **Decommission the gateway from the standard Command organization.** 4 **Follow the steps in** [**Add Cellular Gateway to Command**](https://help.verkada.com/connectivity/configuration-and-setup/add-cellular-gateway-to-command) **to add your gateway to a Government Solutions Command organization.** Last updated 1 day ago Was this helpful? --- # CJIS Support Status | Government Solutions | Verkada Help Verkada works with law enforcement and criminal justice agencies in certain states that require access to Criminal Justice Information Services (CJIS) via the National Crime Information Center (NCIC) database. To enable this access, Verkada follows FBI and state requirements that protect the security and integrity of criminal justice information (CJI). * * * [](https://help.verkada.com/government-solutions/compliance/cjis-support-status#cjis-compliance-process) CJIS compliance process ------------------------------------------------------------------------------------------------------------------------------------- The CJIS Security Policy is a detailed framework of requirements that agencies and vendors must follow to protect criminal justice information. It addresses areas such as personnel security, data encryption, and physical safeguards. To access CJI or NCIC in a given state, Verkada must comply with both FBI and state-specific CJIS requirements, including: Background checks[](https://help.verkada.com/government-solutions/compliance/cjis-support-status#background-checks) All employees with unescorted access to CJI must complete state and federal fingerprint-based background checks in each state where Verkada seeks CJI/NCIC access. Access is granted only after these checks are successfully completed and clearance is confirmed. Signed security addendum[](https://help.verkada.com/government-solutions/compliance/cjis-support-status#signed-security-addendum) Verkada signs a CJIS Security Addendum with each agency customer before enabling access to CJI/NCIC in Verkada Command. This agreement commits Verkada to maintaining a security program that meets federal requirements. State-specific requirements[](https://help.verkada.com/government-solutions/compliance/cjis-support-status#state-specific-requirements) Many states have additional requirements for customer access to CJI/NCIC. Verkada works with the CJIS Systems Officer (CSO), Terminal Agency Coordinator (TAC), and Local Agency Security Officer (LASO) in each state to meet these requirements. * * * ### [](https://help.verkada.com/government-solutions/compliance/cjis-support-status#supported-states) Supported states Verkada can support customer access to CJI/NCIC in the following states: * Arkansas\* * Arizona * California\* * Illinois\* * Kentucky\* * Maryland * Missouri * Nebraska * North Carolina\* * Pennsylvania \*Have a live NCIC integration This list will be updated as Verkada’s offering expands to more states. If you are a law enforcement agency in a state where Verkada does not currently have NCIC access, please contact [\[email protected\]](https://help.verkada.com/cdn-cgi/l/email-protection#ee8981988b9c80838b809aae988b9c858f8a8fc08d8183) . Last updated 20 hours ago Was this helpful? --- # Enable NCIC Alerts | Government Solutions | Verkada Help Data from the National Crime Information Center (NCIC) is sensitive criminal justice information and must be handled securely. For this reason, NCIC alerts are only available in Verkada’s [Government Solutions Command organizations.](https://help.verkada.com/government-solutions/get-started-with-government-solutions) * * * ### [](https://help.verkada.com/government-solutions/events-and-alerts/enable-ncic-alerts#id-1.-request-ncic-in-your-government-solutions-organization) 1\. Request NCIC in your Government Solutions organization This feature is not enabled by default and requires Verkada to support [Criminal Justice Information Services (CJIS)](https://help.verkada.com/government-solutions/compliance/cjis-support-status) compliance in the state where the data is accessed. Contact your Sales Representative or [\[email protected\]](https://help.verkada.com/cdn-cgi/l/email-protection#94f3fbe2f1e6faf9f1fae0d4e2f1e6fff5f0f5baf7fbf9) to get started. ### [](https://help.verkada.com/government-solutions/events-and-alerts/enable-ncic-alerts#id-2.-enable-ncic-in-feature-manager) 2\. Enable NCIC in Feature Manager You need Org Admin permissions to access Feature Manager. 1 **In Verkada Command, go to All Products > Admin.** 2 **Select Feature Manager.** 3 **To the right of NCIC LPR Data Integration, click the dropdown and select Enable.** This feature is only available on cameras with vehicle analytics enabled. ### [](https://help.verkada.com/government-solutions/events-and-alerts/enable-ncic-alerts#id-3.-grant-cjis-viewer-permissions) 3\. Grant CJIS viewer permissions After the feature is enabled, Org Admins must assign CJIS Viewer permissions to the appropriate personnel who are CJIS-approved. This action can only be granted on a per-user basis. 1 **In Verkada Command, go to All Products > Admin.** 2 **Select Users & Permissions > Users.** 3 **Select the user you want to edit.** 4 **At the top, click > Grant CJIS Viewer.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1400995684-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F79mFgTcvQ8N4ByjEDZUn%252Fuploads%252Fgit-blob-feb7ca527dd2cd772e6274af59fb88d75d32fda2%252Fb85fb32a890657a4e1a0dd87d0d18f798cf173a5.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=6309951d&sv=2) After the feature is enabled and users have the required permissions, you can create a new NCIC alert. * * * [](https://help.verkada.com/government-solutions/events-and-alerts/enable-ncic-alerts#configure-ncic-alerts) Configure NCIC alerts --------------------------------------------------------------------------------------------------------------------------------------- ### [](https://help.verkada.com/government-solutions/events-and-alerts/enable-ncic-alerts#create-alert-greater-than-cameras) Create Alert > Cameras 1 **On the Command homepage, left navigation, click Alerts.** 2 **At the top left, click New Alert.** 3 **On Select Event, choose Camera > License Plate Hotlist.** 4 **On Cameras:** a. Choose to receive alerts from **Sites** or **Individual Cameras**. b. Click **Done** to continue. 5 **On Select License Plate Hotlist:** a. Select **NCIC.** b. Select **Offense Reasons** to be included within the alert. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1400995684-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F79mFgTcvQ8N4ByjEDZUn%252Fuploads%252Fgit-blob-eb56981af7743065ed2edec0bbf02142c3832513%252Ff4cb7c02df0cfee81aa2cfbc7e216bfb6bb28a6a.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=bd14188d&sv=2) c. Click **Done** and continue with the alert [recipients](https://help.verkada.com/government-solutions/events-and-alerts/enable-ncic-alerts#h_b2f69ecae8) . Only License Plate Recognition (LPR) enabled cameras can be selected. ### [](https://help.verkada.com/government-solutions/events-and-alerts/enable-ncic-alerts#create-alert-greater-than-recipients) Create Alert > Recipients 1 **On Recipients, add users individually or assign the alert to a group.** 2 **Select the dropdown menu next to a user or group to choose their notification method(s). Recipients can be notified via push, SMS, or email notifications.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1400995684-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F79mFgTcvQ8N4ByjEDZUn%252Fuploads%252Fgit-blob-a30e5c666efe865b169b36f277c2ab798ad76c5d%252F3a9609d9912905edd0f35abfff403a95e0b820c8.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=fcdbb065&sv=2) 3 **(Optional) By default, you will be an alert recipient. Select the dropdown menu and click Delete to remove yourself.** 4 **Click Done and continue with the alert** [**notification schedule**](https://help.verkada.com/government-solutions/events-and-alerts/enable-ncic-alerts#h_7549527028) **.** Any recipient added to this alert will see it appear under the **Shared Alerts** section of their **Alerts** page. ### [](https://help.verkada.com/government-solutions/events-and-alerts/enable-ncic-alerts#create-alert-greater-than-notification-schedule) Create Alert > Notification Schedule 1 **On Notification Schedule, specify the days and times for the alerts to send notifications. Alerts generate 24/7 by default.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1400995684-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F79mFgTcvQ8N4ByjEDZUn%252Fuploads%252Fgit-blob-b9042c786a9dd12580abefdd20f412fe59cbac5e%252F7b61969c185d482c85ec3b7f15a687d75aee8d13.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=f0c3481&sv=2) 2 **Click Done and continue to** [**finish the alert**](https://help.verkada.com/government-solutions/events-and-alerts/enable-ncic-alerts#h_0f4aeaa90c) **.** ### [](https://help.verkada.com/government-solutions/events-and-alerts/enable-ncic-alerts#finish-the-alert) Finish the alert 1 **In the bottom right of the configuration window, click Next.** 2 **Enter a descriptive name for the alert.** 3 **Click Done to complete the setup.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1400995684-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F79mFgTcvQ8N4ByjEDZUn%252Fuploads%252Fgit-blob-75fcc30636d14fdd34cc9e376db710c1542f4ef2%252F943420792c6bfe40aee47eab735038e52669e4ac.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=2bd35cb3&sv=2) Last updated 17 hours ago Was this helpful? --- # Required Access Control Network Settings - Government Solutions | Government Solutions | Verkada Help This article outlines the required network settings that your Verkada [access controllers](https://docs.verkada.com/docs/access-controllers-series-overview.pdf) need to communicate with [Verkada Command](https://help.verkada.com/command/get-started-with-verkada-command) . For more information on the required network settings for other Verkada product lines see [Required Network Settings](https://help.verkada.com/command/required-network-settings) . Verkada devices are incompatible with LANs that require proxy servers or Secure Socket Layer (SSL)/Transport Layer Security (TLS) inspection. If either is in use, a bypass for all Verkada devices must be implemented for Verkada devices to communicate with Verkada Command. [](https://help.verkada.com/government-solutions/required-network-settings/required-access-control-network-settings-government-solutions#status-led) Status LED -------------------------------------------------------------------------------------------------------------------------------------------------------------------- At the top left of the physical access controller, if you see a flashing blue [status LED](https://help.verkada.com/access-control/troubleshooting/verkada-ac41-status-led) this indicates that the access controller is not communicating with Command. If you see this behavior: * Check that the network is set up correctly for the access controller. * See [Verkada Access Offline Operation](https://help.verkada.com/access-control/troubleshooting/verkada-access-offline-operation) to understand what the access system does when it cannot communicate with Command. If the problem persists, contact [Verkada Support](https://help.verkada.com/command/need-help/contact-verkada-support) . [](https://help.verkada.com/government-solutions/required-network-settings/required-access-control-network-settings-government-solutions#ip-address) IP address -------------------------------------------------------------------------------------------------------------------------------------------------------------------- Access controllers need an IPv4 address to communicate on the local area network (LAN) and to Command through the internet. Access controllers use Dynamic Host Configuration Protocol (DHCP), UDP ports 67 and 68, to obtain their IP addresses and network configurations. If you want to have a specific IP address on your access controller, set a DHCP reservation using the access controller’s [Media Access Control (MAC) address](https://help.verkada.com/access-control/hardware-installation/find-a-serial-number-and-mac-address) (found on the device’s label). [](https://help.verkada.com/government-solutions/required-network-settings/required-access-control-network-settings-government-solutions#domain-name-system) Domain Name System ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Access Controllers use the DNS server to resolve Verkada’s fully qualified domain names (FQDN) to IP addresses to communicate with them. Your DHCP server tells the access controller where the DNS server is on the network and the access controller communicates using UDP port 53. DNS over HTTPS (DoH) is currently not supported. [](https://help.verkada.com/government-solutions/required-network-settings/required-access-control-network-settings-government-solutions#power) Power ---------------------------------------------------------------------------------------------------------------------------------------------------------- For specifics on power requirements, see the [access controller’s datasheet](https://www.verkada.com/docs/?product=accessControl&contentType=datasheet) . [](https://help.verkada.com/government-solutions/required-network-settings/required-access-control-network-settings-government-solutions#firewall-settings) Firewall settings ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Verkada access controllers require access to many endpoints to ensure they can communicate with Command and all features will be accessible. Many customers may want to allow the access controllers to communicate with the general required endpoints. These are the general domains to allow, **applicable for all organization-regions**: Copy 34.216.15.26 - UDP/123 35.166.49.153 - UDP/123 + TCP+UDP/443 *.verkada.com - UDP/123 + TCP+UDP/443 If you prefer a more granular allowlist, you can add both IP addresses and full FQDNs to your firewall rules based on the region where your devices are located. Your region is selected when you [create an organization](https://help.verkada.com/command/get-started-with-verkada-command) in Command. ### [](https://help.verkada.com/government-solutions/required-network-settings/required-access-control-network-settings-government-solutions#region-united-states-gov) Region: United States Gov **Standard Verkada Endpoints** Copy api.control.verkada.com - TCP+UDP/443 api.global-prod.control.verkada.com - TCP+UDP/443 api-ga.control.verkada.com - TCP+UDP 443 firmware.control.verkada.com - TCP+UDP/443 update.control.verkada.com - TCP+UDP/443 vconductor.global-prod.command.verkada.com - TCP+UDP/443 api.global-prod.control.verkada.com (HTTPS/443) update.control.verkada.com (HTTPS/443) NTP: returned by DHCP client option 42, if not provided, falls back to time.nist.gov (UDP/123) Local streaming: *:4100 on LAN (HTTPS/443) RTSP: *:8554 on LAN *.kinesisvideo.us-gov-west-1.amazonaws.com (HTTPS/443) s3.us-gov-west-1.amazonaws.com (HTTPS/443) verkada-firmware.s3.us-west-2.amazonaws.com (HTTPS/443) *.prod-govus-pine.control.verkadagov.com (HTTPS/443) api.control.verkada.com (HTTPS/443) **NTP Endpoints** Copy 34.216.15.26 - UDP/123 35.166.49.153 - UDP/123 + TCP+UDP/443 time.control.verkada.com - UDP/123 time.cloudflare.com - TCP/4460 time.cloudflare.com - UDP/123 **Access Control Endpoints** Copy access.control.verkada.com - TCP+UDP/443 vcerberus.command.verkada.com - TCP+UDP/443 *.prod-govus-pine.control.verkadagov.com - TCP+UDP/443 vinnout.prod-govus-pine.command.verkadagov.com Use the [Verkada Network Tester](https://network-tester.support.verkada.com/) to verify your devices can connect to Verkada Command. Select your region and the **Access** product type to run the check. The following endpoints must be allowed on your network for the test to work: * speed.cloudflare.com * network-tester.support.verkada.com Last updated 1 day ago Was this helpful? --- # Government Solutions Licensing | Government Solutions | Verkada Help To access a Government Solutions Command organization, you must have valid Government Solutions licenses for every device in your organization. [](https://help.verkada.com/government-solutions/compliance/government-solutions-licensing#how-verkada-licensing-is-applied) How Verkada licensing is applied ------------------------------------------------------------------------------------------------------------------------------------------------------------------ Verkada licensing is applied for each Command organization, and the licenses co-term to a single expiration date. This means that all of the licenses in an organization are combined, and the expiration date for the organization is the weighted average of all the individual licenses. Learn more about how to [calculate a license expiration date](https://help.verkada.com/command/licensing-and-warranty/calculate-license-expiration-date) . See [Manage Your Licenses](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses) for information on licencing for other Verkada product lines. * * * [](https://help.verkada.com/government-solutions/compliance/government-solutions-licensing#license-requirements-by-product-family) License requirements by product family ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Refer to this table for an overview of the license requirements of each product family: **Product Family** **License requirement** Air Quality Sensors One Government Solutions license per sensor Cameras One Government Solutions license per camera Optional: One Cloud Backup License per 30-day increments on a single device’s cloud retention. Learn more about [Extended Cloud Backup Licensing](https://help.verkada.com/verkada-cameras/historical-playback/extended-cloud-backup-licensing) . Multisensor cameras One Government Solutions MLT4 camera license per CH52-E Four-Camera Multisensor Gateway One Government Solutions cellular gateway license per cellular gateway. Optional: One Government Solutions data plan license per connected camera or intercom. A four-head multisensor camera needs four data licenses. Guest One Workplace license grants you access to use one Guest iPad Viewing Station One viewing station license per viewing station * * * [](https://help.verkada.com/government-solutions/compliance/government-solutions-licensing#purchase-government-solutions-licenses) Purchase Government Solutions licenses ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Government Solutions licenses are available in 1, 3, 5, and 10-year terms. There are two types of licenses: capacity increase (CAP) and renewal (RNW). * **Capacity Increase (CAP) licenses**: Verkada CAP licenses are automatically activated when the associated Verkada hardware order is shipped. New device licenses include a 30-day extension beyond the purchased term to accommodate shipping and installation. The extension period is fixed and does not depend on when the device is installed or activated. * **Renewal (RNW) licenses:** Verkada RNW licenses extend an organization’s existing term but remain inactive until the earlier of: * The date they are claimed within a Command organization or * One year after the purchase date. If unclaimed after one year, the license automatically activates, and its term begins to run. Any license claimed beyond this one-year period results in a shortened remaining term. This policy ensures compliance with the intended service period. Licenses are usually sold with your Verkada devices, but you can also purchase them separately from your Verkada reseller or sales representative. See the latest [licensing prices](https://www.verkada.com/pricing/) . * * * [](https://help.verkada.com/government-solutions/compliance/government-solutions-licensing#renew-your-licenses) Renew your licenses ---------------------------------------------------------------------------------------------------------------------------------------- When your licenses are soon to expire, you need to renew your license to avoid losing access to Verkada Command. You can renew your license by contacting your Verkada Sales Representative or your Verkada Reseller. ### [](https://help.verkada.com/government-solutions/compliance/government-solutions-licensing#renewal-notifications-and-license-expiration) Renewal notifications and license expiration 30 days before expiry, you will expect to: * Receive an email notifying you that your licenses are about to expire. * See a banner in Command. You will lose access to Command if you haven’t renewed your license within 30 days after your expiration date. * * * [](https://help.verkada.com/government-solutions/compliance/government-solutions-licensing#licensing-overcap-policy) Licensing overcap policy -------------------------------------------------------------------------------------------------------------------------------------------------- An organization is considered to be in overcap when it has more devices commissioned than the number of licenses claimed. ### [](https://help.verkada.com/government-solutions/compliance/government-solutions-licensing#overcap-policy) Overcap policy Verkada enforces software compliance by requiring each hardware product to have a valid, claimed software license(see requirements above). The Overcap policy introduces an **Invalid** status for organizations that exceed their claimed licenses, ensuring compliance across all Verkada products. After a 90-day grace period, organizations without proper licensing lose access to critical functions, including device management and notifications. ### [](https://help.verkada.com/government-solutions/compliance/government-solutions-licensing#how-it-works) How it works Verkada will notify all Command users 90 days **before** an organization loses access, prompting them to claim additional licenses. Organization Admins will receive in-product banners and emails over 90 days to ensure they restore compliance. All devices will remain functional when access to Command is restricted. However, users will still have access to the **License Manager**, **Devices**, and **Technical Support** pages when an organization is no longer compliant. ### [](https://help.verkada.com/government-solutions/compliance/government-solutions-licensing#restore-compliance) Restore compliance Organization Admins can perform **one** of the following actions to restore compliance: * Claim any unused licensing keys. * Remove any unused devices from the organization. * Contact your Sales Representative or email [\[email protected\]](https://help.verkada.com/cdn-cgi/l/email-protection#f09c9993959e83999e97b08695829b919491de939f9d) if you believe there has been an error with the licensing implementation on your account. * * * [](https://help.verkada.com/government-solutions/compliance/government-solutions-licensing#faq) FAQ -------------------------------------------------------------------------------------------------------- What happens if I have insufficient or expired licenses?[](https://help.verkada.com/government-solutions/compliance/government-solutions-licensing#what-happens-if-i-have-insufficient-or-expired-licenses) Verkada will send you an email notification and add a banner notification to your Command Organization. You need valid licenses to use Command. If you don’t [claim your licenses](https://help.verkada.com/command/licensing-and-warranty/find-and-add-license-keys-to-command) when adding new devices or products or renew them when they expire, you will lose access to most of your Command functionality after a 30-day grace period. * For expired organizations, you have a 30-day grace period before you lose access. * For organizations with insufficient licenses, you have a 90-day grace period before you lose access. * Contact your Verkada Partner or Sales Representative to purchase additional licenses. At the end of this grace period, you will no longer have access to any of your devices or configure any settings. Alarms and Event notifications will also be disabled. You will, however, be able to delete devices and products so you get back into compliance in case you have insufficient licenses. How will I know if my licenses are soon to expire?[](https://help.verkada.com/government-solutions/compliance/government-solutions-licensing#how-will-i-know-if-my-licenses-are-soon-to-expire) 30 days before your license is set to expire, Verkada will send you an email notification and add a banner notification to your Command Organization. How do I regain full access to Command?[](https://help.verkada.com/government-solutions/compliance/government-solutions-licensing#how-do-i-regain-full-access-to-command) If your access to Command was limited due to insufficient licenses, you can: * Delete the products that are above your license cap to get back into compliance * Contact your Verkada Partner or Sales Representative to purchase additional licenses. If your access to Command was limited due to expired licenses, you can contact your Verkada Partner or Sales Representative to renew your licenses. Will my devices still record data?[](https://help.verkada.com/government-solutions/compliance/government-solutions-licensing#will-my-devices-still-record-data) As long as your Verkada devices are still connected, they will continue to record data. This data will be available when you regain access to Command (as long as you’re still within the retention period for the given device). Badges and Verkada Pass will still work as before, but you’ll be unable to change your settings via Command. What happens if I don’t return my expired trial devices?[](https://help.verkada.com/government-solutions/compliance/government-solutions-licensing#what-happens-if-i-dont-return-my-expired-trial-devices) Trialing a Verkada device is the best way to experience how our products and platform works. You can initiate a free trial for most of our devices through your Verkada Sales Rep, or your Verkada Partner. The free trial lasts for 30 days. After the 30 days are up, you’ll see a banner in Command reminding you to return or purchase your trial devices. If you don’t return the devices within 30 days of the expiry date they will stop working as expected. If you need additional time to test our trial devices and platform, you can ask your Verkada Sales Rep for an extension. Last updated 1 day ago Was this helpful? --- # Required Air Quality Sensor Network Settings - Government Solutions | Government Solutions | Verkada Help Verkada devices need to communicate with a [Government Solution Command organization](https://www.verkada.com/solutions/government-grade) via their local network. In most cases, minimal updates to your network settings are needed. Additional configuration may be required for complex or highly secure networks. See [Required Network Settings](https://help.verkada.com/command/required-network-settings) for more information on the required network settings for other Verkada product lines. * * * [](https://help.verkada.com/government-solutions/required-network-settings/required-air-quality-sensor-network-settings-government-solutions#compatibility) Compatibility ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Verkada devices are incompatible with local area networks (LANs) that require proxy servers or Secure Socket Layer (SSL)/Transport Layer Security (TLS) inspection. If either is in use, a bypass for all Verkada devices must be implemented for your Verkada devices to communicate with Verkada Command. [](https://help.verkada.com/government-solutions/required-network-settings/required-air-quality-sensor-network-settings-government-solutions#ip-address) IP address ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Verkada devices must be assigned an IPv4 address to communicate on the LAN and to Verkada Command through the internet. By default, all Verkada devices use Dynamic Host Configuration Protocol (DHCP) and User Datagram Protocol (UDP) to obtain their IP addresses and network configurations. If you require your device to have a specific IP address, create a DHCP reservation using the device’s Media Access Control (MAC) address (found on the device’s label). ​ Verkada devices may utilize path MTU discovery to determine the maximum transmission unit of the network path. Therefore, it is necessary to permit ICMP Fragmentation Needed (Type 3, Code 4) and ICMPv6 Packet Too Big (Type 2) packets. Ensure your firewall(s) are configured to permit this in the return path to your Verkada devices. [](https://help.verkada.com/government-solutions/required-network-settings/required-air-quality-sensor-network-settings-government-solutions#domain-name-system) Domain Name System ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Verkada devices use the Domain Name System (DNS) server to resolve Verkada’s fully qualified domain names (FQDN) to IP addresses to communicate with them. Your DHCP server tells the Verkada device where the DNS server is on the network, and the device communicates using UDP port 53. DNS over HTTPS (DoH) is not currently supported. [](https://help.verkada.com/government-solutions/required-network-settings/required-air-quality-sensor-network-settings-government-solutions#power) Power -------------------------------------------------------------------------------------------------------------------------------------------------------------- Most Verkada devices are powered through Power over Ethernet (PoE). You can use the product [datasheets](https://www.verkada.com/docs/?contentType=datasheet) to figure out the power requirements for your Verkada devices. These are the most common power requirements: * IEE 802.3af, Type 1 PoE * IEEE 802.3at, Type 2 PoE+ * IEEE 802.3bt, Type 3 PoE++ * * * [](https://help.verkada.com/government-solutions/required-network-settings/required-air-quality-sensor-network-settings-government-solutions#air-quality-sensors-firewall-settings) Air Quality Sensors firewall settings ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Verkada Air Quality Sensors require access to many endpoints to ensure they can communicate with Command and that all features are accessible. #### [](https://help.verkada.com/government-solutions/required-network-settings/required-air-quality-sensor-network-settings-government-solutions#region-united-states-gov) Region: United States Gov * api.prod-govus-pine.control.verkadagov.com (TCP+UDP/443) * 3.32.137.127/32 * 3.31.127.57/32 * 3.30.93.146/32 * api.control.verkada.com (TCP+UDP/443) * 35.155.73.204/32 * 54.186.237.126/32 * 35.166.49.153/32 * 35.84.130.83/32 * vsensor.prod-govus-pine.verkadagov.com (TCP+UDP/443) Last updated 23 hours ago Was this helpful? --- # Required Command Connector Network Settings - Government Solutions | Government Solutions | Verkada Help Verkada devices need to communicate with a [Government Solution Command organization](https://www.verkada.com/solutions/government-grade) via their local network. In most cases, minimal updates to your network settings are needed. Additional configuration may be required for complex or highly secure networks. See [Required Network Settings](https://help.verkada.com/command/required-network-settings) for more information on the required network settings for other Verkada product lines. * * * [](https://help.verkada.com/government-solutions/required-network-settings/required-command-connector-network-settings-government-solutions#compatibility) Compatibility ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Verkada devices are incompatible with local area networks (LANs) that require proxy servers or Secure Socket Layer (SSL)/Transport Layer Security (TLS) inspection. If either is in use, a bypass for all Verkada devices must be implemented for your Verkada devices to communicate with Verkada Command. [](https://help.verkada.com/government-solutions/required-network-settings/required-command-connector-network-settings-government-solutions#ip-address) IP address ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- Verkada devices must be assigned an IPv4 address to communicate on the LAN and to Verkada Command through the internet. By default, all Verkada devices use Dynamic Host Configuration Protocol (DHCP) and User Datagram Protocol (UDP) to obtain their IP addresses and network configurations. If you require your device to have a specific IP address, create a DHCP reservation using the device’s Media Access Control (MAC) address (found on the device’s label). You can also set up [static IP addresses](https://help.verkada.com/command-connector/configuration-and-setup/configure-static-ip-addresses-for-command-connector) in Command for Command Connector. Verkada devices may utilize path MTU discovery to determine the maximum transmission unit of the network path. Therefore, it is necessary to permit ICMP Fragmentation Needed (Type 3, Code 4) and ICMPv6 Packet Too Big (Type 2) packets. Ensure your firewall(s) are configured to permit this in the return path to your Verkada devices. [](https://help.verkada.com/government-solutions/required-network-settings/required-command-connector-network-settings-government-solutions#domain-name-system) Domain Name System --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Verkada devices use the Domain Name System (DNS) server to resolve Verkada’s fully qualified domain names (FQDN) to IP addresses to communicate with them. Your DHCP server tells the Verkada device where the DNS server is on the network, and the device communicates using UDP port 53. DNS over HTTPS (DoH) is not currently supported. * * * [](https://help.verkada.com/government-solutions/required-network-settings/required-command-connector-network-settings-government-solutions#command-connector-firewall-settings) Command Connector firewall settings ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Verkada Command Connectors require access to many endpoints to ensure they can communicate with Command and that all features are accessible. ### [](https://help.verkada.com/government-solutions/required-network-settings/required-command-connector-network-settings-government-solutions#region-united-states-gov) Region: United States Gov 1 `**api.global-prod.control.verkada.com**` **(HTTPS/443)** 1 `**update.control.verkada.com**` **(HTTPS/443)** 2 `**time.nist.gov**` **(TCP+UDP - HTTPS/443)** 3 `***.kinesisvideo.us-gov-west-1.amazonaws.com**` **(HTTPS/443)** 4 `***.us-gov-west-1.compute.amazonaws.com**` **(HTTPS/443 & UDP/1024-65535)** 5 `**s3.us-gov-west-1.amazonaws.com**` **(HTTPS/443)** 6 `**verkada-firmware.s3.us-west-2.amazonaws.com**` **(HTTPS/443)** 7 `**api.prod-govus-pine.control.verkadagov.com**` **(HTTPS/443)** 8 `**api.control.verkada.com**` **(HTTPS/443)** 9 `**RTSP**` **(\*:8554 on LAN)** 10 `**vsubmit.prod-govus-pine.verkadagov.com**` **(HTTPS/443)** 11 `**relay.prod-govus-pine.control.verkadagov.com**` **(HTTPS/443)** 12 `**vproxy.prod-govus-pine.verkadagov.com**` **(HTTPS/443)** 13 `**vstream.prod-govus-pine.verkadagov.com**` **(HTTPS/443)** 14 `**vflow.prod-govus-pine.verkadagov.com**` **(HTTPS/443)** 15 **Local streaming (\*:4100 on LAN)** * * * **Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=5pRUeH_bhw0) . Last updated 23 hours ago Was this helpful? --- # Required Cellular Gateway Network Settings - Government Solutions | Government Solutions | Verkada Help Verkada devices need to communicate with a [Government Solution Command organization](https://www.verkada.com/solutions/government-grade) via their local network. In most cases, minimal updates to your network settings are needed. Additional configuration may be required for complex or highly secure networks. See [Required Network Settings](https://help.verkada.com/command/required-network-settings) for more information on the required network settings for other Verkada product lines. * * * [](https://help.verkada.com/government-solutions/required-network-settings/required-cellular-gateway-network-settings-government-solutions#compatibility) Compatibility ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Verkada devices are incompatible with local area networks (LANs) that require proxy servers or Secure Socket Layer (SSL)/Transport Layer Security (TLS) inspection. If either is in use, a bypass for all Verkada devices must be implemented for your Verkada devices to communicate with Verkada Command. [](https://help.verkada.com/government-solutions/required-network-settings/required-cellular-gateway-network-settings-government-solutions#ip-address) IP address ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- Verkada devices must be assigned an IPv4 address to communicate on the LAN and to Verkada Command through the internet. By default, all Verkada devices use Dynamic Host Configuration Protocol (DHCP) and User Datagram Protocol (UDP) to obtain their IP addresses and network configurations. If you require your device to have a specific IP address, create a DHCP reservation using the device’s Media Access Control (MAC) address (found on the device’s label). ​ Verkada devices may utilize path MTU discovery to determine the maximum transmission unit of the network path. Therefore, it is necessary to permit ICMP Fragmentation Needed (Type 3, Code 4) and ICMPv6 Packet Too Big (Type 2) packets. Ensure your firewall(s) are configured to permit this in the return path to your Verkada devices. [](https://help.verkada.com/government-solutions/required-network-settings/required-cellular-gateway-network-settings-government-solutions#domain-name-system) Domain Name System -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Verkada devices use the Domain Name System (DNS) server to resolve Verkada’s fully qualified domain names (FQDN) to IP addresses to communicate with them. Your DHCP server tells the Verkada device where the DNS server is on the network, and the device communicates using UDP port 53. DNS over HTTPS (DoH) is not currently supported. [](https://help.verkada.com/government-solutions/required-network-settings/required-cellular-gateway-network-settings-government-solutions#power) Power ------------------------------------------------------------------------------------------------------------------------------------------------------------ Most Verkada devices are powered through Power over Ethernet (PoE). You can use the product [datasheets](https://www.verkada.com/docs/?contentType=datasheet) to figure out the power requirements for your Verkada devices. These are the most common power requirements: * IEE 802.3af, Type 1 PoE * IEEE 802.3at, Type 2 PoE+ * IEEE 802.3bt, Type 3 PoE++ * * * [](https://help.verkada.com/government-solutions/required-network-settings/required-cellular-gateway-network-settings-government-solutions#cellular-gateway-firewall-settings) Cellular Gateway firewall settings ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Verkada Cellular Gateways require access to many endpoints to ensure they can communicate with Command and that all features are accessible. #### [](https://help.verkada.com/government-solutions/required-network-settings/required-cellular-gateway-network-settings-government-solutions#region-united-states-gov) Region: United States Gov * api.prod-govus-pine.control.verkadagov.com (TCP+UDP/443) * 3.32.137.127/32 * 3.31.127.57/32 * 3.30.93.146/32 * api.control.verkada.com (TCP+UDP/443) * 35.155.73.204/32 * 54.186.237.126/32 * 35.166.49.153/32 * 35.84.130.83/32 * vnet.prod-govus-pine.verkadagov.com (TCP+UDP/443) Last updated 23 hours ago Was this helpful? --- # Email Protection | Cloudflare Please enable cookies. Email Protection ================ You are unable to access this email address help.verkada.com ------------------------------------------------------------ The website from which you got to this page is protected by Cloudflare. Email addresses on that page have been hidden in order to keep them from being accessed by malicious bots. **You must enable Javascript in your browser in order to decode the e-mail address**. If you have a website and are interested in protecting it in a similar way, you can [sign up for Cloudflare](https://www.cloudflare.com/sign-up?utm_source=email_protection) . * [How does Cloudflare protect email addresses on website from spammers?](https://developers.cloudflare.com/waf/tools/scrape-shield/email-address-obfuscation/) * [Can I sign up for Cloudflare?](https://developers.cloudflare.com/fundamentals/setup/account/create-account/) Cloudflare Ray ID: **9a9898dfe9df0578** • Your IP: Click to reveal 54.237.218.47 • Performance & security by [Cloudflare](https://www.cloudflare.com/5xx-error-landing) --- # Air Quality Sensor Status LED | Air Quality | Verkada Help Each Verkada [Air Quality Sensor](https://www.verkada.com/air-quality/sensors#overview) is equipped with an outside LED light. This light indicates its operating status. Verkada offers the [SV11](https://www.verkada.com/sensors/sv11/) series and SV20 series (including [SV21](http://sv21/) , [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) ). [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-status-led#sv11-series) SV11 series --------------------------------------------------------------------------------------------------------------- The [SV11](https://www.verkada.com/sensors/sv11/) series follows the same LED convention as all Verkada cameras. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-f40ec6af76669b489ca83b0c4cceab8e74b284e3%252F39d533797af0dee409035ed6d8d0e6f232f303d0.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=c7ae8471&sv=2) [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-status-led#sv20-series) SV20 series --------------------------------------------------------------------------------------------------------------- The newer SV20 series ([SV21](http://sv21/) , [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) ) uses a white LED indicator; however, its status is analogous to that of the blue LED on the SV11. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-bee9908e2734e8a7496e00ea380098f5d0769aec%252F9e5b72d9d92121b9d0e41f4512ecd32f4283d4ae.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=199ecd07&sv=2) Last updated 19 hours ago Was this helpful? --- # Installation Guidelines for Sensors | Air Quality | Verkada Help For best performance, use this article to learn about the standard and recommended guidelines for installing Verkada [Air Quality Sensors](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) . ​ [](https://help.verkada.com/air-quality/hardware-installation/installation-guidelines-for-sensors#standard-guidelines-by-sensor) Standard guidelines by sensor ------------------------------------------------------------------------------------------------------------------------------------------------------------------- ### [](https://help.verkada.com/air-quality/hardware-installation/installation-guidelines-for-sensors#sv20-series) SV20 series Here are some standard guidelines for the [SV20 Series](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) installation: * **CO₂ monitoring** * Wall mounting, between 3-6 ft (0.9–1.8m) from floor * Keep sensor at least 5 ft (1.5m) away from any doors or operable windows * **Vape detection** * Ceiling mounting, no more than 8-9 ft (2.4–2.7m) from the ground. If the height is increased, detection decreases. * If placed in a bathroom, 1 sensor per 2 stalls is recommended. At least 3 ft (0.9m) from vents or walls. * Wall mounting may lead to inaccurate vape detection. * At least 3 ft (0.9m) away from areas that are exposed to airflow and circulation (e.g. HVAC vents, windows, refrigerator blowers, and so on). * Away from direct sunlight exposure. ### [](https://help.verkada.com/air-quality/hardware-installation/installation-guidelines-for-sensors#sv11) SV11 Here are some standard guidelines for the [SV11](https://docs.verkada.com/docs/sensors-quick-start-guide.pdf) installation: * Mount indoors on a ceiling. We recommend to installed 8 ft (2.4m) above the floor. * On a solid, nonmetallic surface (e.g. drywall, drop ceiling, wood, concrete, and so on). * At least 3 ft (0.9m) away from areas that are exposed to airflow and circulation (e.g. HVAC vents, windows, refrigerator blowers, and so on). * Away from direct sunlight exposure. * Wall mounting is possible, however, leads to inaccurate temperatures and air quality detection and should be avoided, if possible. The SV11 is designed to be installed on the ceiling; the range and accuracy values listed in the [data sheet](https://docs.verkada.com/docs/sensors-quick-start-guide.pdf) are based on the device mounted in this position. If the SV11 is mounted on a wall (vertically), it will still function, but the range and accuracy values may not be within the range specified in the [data sheet](https://docs.verkada.com/docs/sensors-quick-start-guide.pdf) . [](https://help.verkada.com/air-quality/hardware-installation/installation-guidelines-for-sensors#recommendations-for-best-performance) Recommendations for best performance --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ### [](https://help.verkada.com/air-quality/hardware-installation/installation-guidelines-for-sensors#installation-location) Installation location To achieve the best accuracy for all the sensors on the device, we recommend to mount the sensor on an 8 ft (2.4m) ceiling. This provides up to 250 sq ft (23 sqm) of total coverage per sensor. **Note**: For vape detection, put 1 sensor for every 2 stalls in a bathroom. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-0dbc18c61a99b0bb14323991586b7dce02c55c2f%252Fcabff804080f73edfbcdac9d3b3ebaa70c540310.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=f02af8f0&sv=2) ### [](https://help.verkada.com/air-quality/hardware-installation/installation-guidelines-for-sensors#installation-surface) Installation surface The sensors are designed to be installed on a solid nonmetallic surface such as drywall, a drop ceiling, concrete, or wood. Metallic or surfaces that adjust the predictable heat generated by the device may lead to temperature inaccuracies. If the SV11 is mounted on a metal surface in a cold \[-5º to 5º C (23° to 41° F)\] or hot \[27º to 50º C (80° F to 122° F)\] environment, we recommend to place a piece of rubber material between the surface and the SV11 mounting plate. This recommendation ensures that the temperature of the mounting surface has less of an impact on the accuracy of the SV11 sensor readings. The SV20 series devices utilize a hardened plastic mount plate that significantly reduces this effect, but we still recommend that they be installed on a solid, nonmetallic surface. ​ ### [](https://help.verkada.com/air-quality/hardware-installation/installation-guidelines-for-sensors#power-consumption) Power consumption Verkada environmental sensors use industry-standard 802.3af \[Power over Ethernet (PoE)\]. During normal operation, the SV11 consumes 4W of power and the SV20 series devices typically consume 3W of power (max of 4W of power). For more information, see [Environmental Sensor Power Requirements](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-power-requirements) . ### [](https://help.verkada.com/air-quality/hardware-installation/installation-guidelines-for-sensors#calibration-time) Calibration time When the device is first plugged-in, temperature, TVOC, and CO₂ (only on the SV20 series) readings may be higher or lower than anticipated. These readings self-correct over an automated calibration period and do not represent a significant amount of variability. All air quality sensors have an initial calibration period of 4 hours, but can take up to 3 days to complete full calibration of the TVOC. For optimal accuracy, we recommend to mount the sensors in a stable environment without intermittent events such as sporadic HVAC events. **Note**: There’s a possibility that there will be variability in the sensor readings if 2 or more air quality sensors are placed next to one another. Each sensor has its own inherit characteristics and calibration can result in different readings. ### [](https://help.verkada.com/air-quality/hardware-installation/installation-guidelines-for-sensors#temperature-humidity-range-and-accuracy) Temperature, humidity range, and accuracy Below are the ranges and accuracy measurements for each of the air quality sensor series temperature and humidity sensors. These values represent the typical and recommended installation location. If the sensor is installed outside of the recommendations, the range and accuracy may fall out of the accuracy range stated in the [data sheet](https://help.verkada.com/en/articles/6732870-what-s-new-in-the-sv20-series) . #### [](https://help.verkada.com/air-quality/hardware-installation/installation-guidelines-for-sensors#sv20-series-1) SV20 series **Temperature Range** **Temperature Accuracy** **Humidity Accuracy** **Comments** < -5º C (23° F) N/A N/A Not within operating range of the device \-5º to 45º C (23° to 113° F) Typical ± 0.3º C (± 0.54º F) Max ± 1º C (± 1.8º F) Operating Range: 0–95% non-condensing Accuracy: ± 3% @ 25º C Accuracy measurements based on the sensor being installed \> 45º C (113° F) N/A N/A Not within operating range of the device #### [](https://help.verkada.com/air-quality/hardware-installation/installation-guidelines-for-sensors#sv11-1) SV11 **Temperature Range** **Temperature Accuracy** **Humidity Accuracy** **Comments** < -5º C (23° F) N/A N/A Not within operating range of the device \-5º to 50º C (23° to 123° F) Typical ± 2.5º C (± 4.5º F) Max ± 3.5º C (± 6.5º F) ± 5% to ± 10% Accuracy measurements based on the sensor being installed \> 50º C (122° F) N/A N/A Not within operating range of the device ### [](https://help.verkada.com/air-quality/hardware-installation/installation-guidelines-for-sensors#wall-mounting) Wall mounting #### [](https://help.verkada.com/air-quality/hardware-installation/installation-guidelines-for-sensors#sv20-series-2) SV20 series The **SV20 series** devices can be mounted on a wall without issue; however, we don’t recommended for use with vape detection. #### [](https://help.verkada.com/air-quality/hardware-installation/installation-guidelines-for-sensors#sv11-2) SV11 The **SV11** can be mounted on a wall, however, we don’t recommended it. The ranges and accuracy of the sensors are specified for the device being installed on a solid ceiling surface. If installed on a wall, the accuracy and ranges of the SV11 sensors may be outside of what is specified in the [data sheet](https://docs.verkada.com/docs/sensors-quick-start-guide.pdf) . **Mount on a non-solid surface (example: hanging in the air)** SV11 sensors are designed to be installed on a solid ceiling surface facing the ground. If the SV11 sensor is installed in "free air", where the front and back of the device are exposed, the accuracy of the temperature and vape detection on the sensor may not fall within the stated range. ### [](https://help.verkada.com/air-quality/hardware-installation/installation-guidelines-for-sensors#exposure-to-direct-sunlight) Exposure to direct sunlight For the highest accuracy, do not place the sensor where it is exposed to direct sunlight. If the sensor is exposed to direct sunlight, the temperature and humidity readings may fall out of the accuracy range stated in the [data sheet](https://docs.verkada.com/docs/sensors-quick-start-guide.pdf) . ### [](https://help.verkada.com/air-quality/hardware-installation/installation-guidelines-for-sensors#exposure-to-air-circulation) Exposure to air circulation If the sensor is exposed to consistent airflow or sporadic airflow (for example, an HVAC vent, a refrigerator blower, a window, and so on), the accuracy of the temperature sensor and the other onboard sensors may fall out of the accuracy range stated in the data sheet. Exposure to airflow changes the thermodynamics of the device which leads to varying inaccuracies in the temperature, humidity, and other sensor readings. Airflow as present in areas, such as HVAC ducts, can generate pressure drops, back pressure, and dynamic fluctuations leading to increased sensor noise and reduced accuracy. For the highest accuracy, mount the sensor away from HVAC vents or areas where the device could be exposed to varying levels of airflow or circulation. Last updated 17 hours ago Was this helpful? --- # Security Screening Settings | Guest | Verkada Help Verkada Guest Security Screening allows organizations across all industries to instantly vet visitors. Per Guest Type, organizations can configure a security screening step that require visitors to present an ID, which is used for searches across external databases. Guest offers a set of controls for the results returned by the feature as well as tools for responding to confirmed offenders. * * * [](https://help.verkada.com/guest/configuration-and-setup/security-screening-settings#control-security-screening-content) Control Security Screening Content ----------------------------------------------------------------------------------------------------------------------------------------------------------------- ### [](https://help.verkada.com/guest/configuration-and-setup/security-screening-settings#hide-incomplete-records) Hide Incomplete Records Incomplete records are records that are missing a photo of the offender and a complete date of birth for the offender. By default, incomplete records are displayed after all high quality records have been dismissed. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1436127735-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FZyuELZr7uIcXX3WnjX0N%252Fuploads%252Fgit-blob-edd8f0a9689b875ea83ac4de0a835f7fdd500ac0%252F68a10f80b4ab83f2ec8d77df7ae7cf80a850eb6f.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=756ef3b7&sv=2) The Hide Incomplete Records toggle allows organizations to focus only on high quality records when reviewing security screening results. With the toggle on, incomplete records do not need to be reviewed. Guest users will still have the option to review incomplete records once high quality records have been dismissed: ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1436127735-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FZyuELZr7uIcXX3WnjX0N%252Fuploads%252Fgit-blob-1675b2a0aa7ad9728b3b93471e8c23e020075832%252F1b8264f68cb3024cdd269d2cf1d25a8af4f85688.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=be96745&sv=2) To turn on the **Hide Incomplete Records** toggle: 1 **In Verkada Command, go to All Products > Workplace >** **Guest.** 2 **On the left navigation, click Guest Settings.** 3 **Under Sites > Security Screening.** 4 **Toggle on Hide Incomplete Records.** A user must be a **Workplace Site Admin** to toggle **Hide Complete Records**\*.\* ### [](https://help.verkada.com/guest/configuration-and-setup/security-screening-settings#record-age-filter) Record Age Filter The Record Age Filter allows organizations to display only records created within a specified number of years, counting back from the current date, as defined by the administrator. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1436127735-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FZyuELZr7uIcXX3WnjX0N%252Fuploads%252Fgit-blob-7a1b1af2d0abf2cdaeaf6789a83dbfacaefee688%252Fc0521be27de7de35696e65e3149efb386fb3917c.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=4423fc26&sv=2) 1 **In Verkada Command, go to All Products > Workplace >** **Guest.** 2 **On the left navigation, click Guest Settings.** 3 **Under Organization > Security & Data.** 4 **Toggle Ignore records older than… and set the desired number of years.** A user must be an **Org Admin** to toggle the Record Age Filter. * * * [](https://help.verkada.com/guest/configuration-and-setup/security-screening-settings#configuring-security-screening-outcomes) Configuring Security Screening Outcomes --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ### [](https://help.verkada.com/guest/configuration-and-setup/security-screening-settings#retention-of-saved-identification-info) Retention of Saved Identification Info If a Guest user confirms a match between a visitor and a record from the security screening, the record as well as the visitor’s identification information will be available on Command for an admin-defined period of time. This time is determined by the **Retention of Saved Identification Info** setting. In the event of a confirmed match, the retained visitor information can include: * visitor’s name * visitor’s date of birth * image of the visitor’s ID * visitor’s address * visitor’s badge photo ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1436127735-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FZyuELZr7uIcXX3WnjX0N%252Fuploads%252Fgit-blob-3280dbea98a220f00ba16b4ff537f22141dc3857%252F595be1488cb82dd1ac3265bee473db3991b75bdc.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=115d683e&sv=2) When Guest Types are configured to save an image of visitor’s IDs, these images will be saved for the period of time set in Retention of Saved Identification Info setting. 1 **In Verkada Command, go to All Products > Workplace >** **Guest.** 2 **On the left navigation, click Guest Settings.** 3 **Under Organization > Security & Data.** 4 **Under Retention of Saved Identification Info, input a number between 1 and 90.** A user must be an **Org Admin** to configure the Retention of Saved Identification Info setting. ### [](https://help.verkada.com/guest/configuration-and-setup/security-screening-settings#staff-notifications) Staff Notifications Staff notifications are sent to relevant contacts for important security screening events, which include: 1 **A match is confirmed between a visitor and a security screening record. The confirmed record is included in these notifications as a PDF and also contain the visitor’s identification information.** 2 **A visitor is added to the Previously Dismissed Matches list. The records that were dismissed for the visitor are included in the notification as a PDF.** Command users can be selected for staff notifications. External phone numbers and emails may also be enrolled to receive staff notifications. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1436127735-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FZyuELZr7uIcXX3WnjX0N%252Fuploads%252Fgit-blob-5fcef4a587b7986bf423d464839fe1cf9f021968%252F9c1fe7a91c2c4227a39e8fbda100790289efa5ea.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=feb25962&sv=2) 1 **In Verkada Command, go to All Products > Workplace >** **Guest.** 2 **On the left navigation, click Guest Settings.** 3 **Under Sites > Staff Notifications.** 4 **Add relevant contacts.** A user must be a **Workplace Site Admin** to configure the staff notifications. * * * **Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=Y9SH2w1glvY) . Last updated 17 hours ago Was this helpful? --- # Microsoft Entra ID SAML Integration - Government Solutions | Government Solutions | Verkada Help Verkada Command can integrate with Microsoft Entra ID using Security Assertion Markup Language (SAML). SAML handles the authentication side of things allowing Microsoft Entra ID to be used to manage access to Command, the same as any other Software as a Service (SaaS) application already integrates into your Microsoft Entra ID tenant. This means that you can incorporate Command into your existing identity framework and authorize users based on your current policies. * * * [](https://help.verkada.com/government-solutions/single-sign-on-sso/microsoft-entra-id-saml-integration-government-solutions#set-up-saml-in-microsoft-entra-id) Set up SAML in Microsoft Entra ID ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Verkada Command is registered as a gallery application and can be found within the Microsoft Entra ID marketplace; in other words, you can leverage it with Microsoft Entra ID Free, Microsoft Entra ID P1, and Microsoft Entra ID P2 licenses. To get started, you need your `client-ID`. Learn how to [generate it and configure your email domains](https://help.verkada.com/command/single-sign-on-sso/saml/enable-saml-for-your-command-account) , then return to this article to complete the remainder of this process. 1 **Add Verkada Command as an enterprise application in your Microsoft Entra ID directory: Go to your Microsoft Entra ID overview page and select Enterprise applications.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1400995684-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F79mFgTcvQ8N4ByjEDZUn%252Fuploads%252Fgit-blob-a79722a44181b1fdc58b4a446717b725395bf3f0%252Fea7d4d52ebddb8b4b886e1e9eb2febc75e0d86b3.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=97057553&sv=2) 2 **At the top of the page, select New Application and search for Verkada Command.** 3 **Select Verkada Command and click Create.** _**Be patient as it can take a few minutes to add the application to your**_ **Microsoft Entra ID** _**tenant**_**.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1400995684-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F79mFgTcvQ8N4ByjEDZUn%252Fuploads%252Fgit-blob-31d38b1f41a163cd63acdd388f7841043225dcba%252Fa059e22dc1d67995f891ded49cfd7d882ce4e00a.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=f68fc42a&sv=2) Once the page refreshes, you should see a similar menu (as shown below). ​ 4 **On Set up single sign-on, click Get started.** ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1400995684-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F79mFgTcvQ8N4ByjEDZUn%252Fuploads%252Fgit-blob-6a28059d10b2ee41a6e442c29b98e00025eff15a%252F7cf12443f73d5124fb52129d4b2835c317bf1d57.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=73d5a593&sv=2) 5 **Choose SAML as the single sign-on method.** ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1400995684-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F79mFgTcvQ8N4ByjEDZUn%252Fuploads%252Fgit-blob-d6d6ca8dd62db59b642475c10341b7b46962fb2c%252F0e6513aae4262222ba5c16809425c6c77d2b8333.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=5857b2d2&sv=2) 6 **If necessary, click Edit to further configure your SAML connection.** 7 **Configure the following fields. You need to add your client ID to the end of each URL before adding them to Microsoft Entra ID. See example below the note.** a. For **Identifier**: [https://saml.prod-govus-pine.verkadagov.com/saml/sso](https://saml.prod-govus-pine.verkadagov.com/saml/sso/) b. For **Reply URL**: [https://saml.prod-govus-pine.verkadagov.com/saml/sso](https://saml.prod-govus-pine.verkadagov.com/saml/sso) c. For **Sign on URL**: [https://saml.prod-govus-pine.verkadagov.com/saml/login](https://saml.prod-govus-pine.verkadagov.com/saml/login) ​[​](https://saml.prod-ap-syd.verkada.com/saml/sso) **Note**: To confirm which region you’re located, please refer to where [your organization was created for Verkada](https://help.verkada.com/command/get-started-with-verkada-command) . ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1400995684-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F79mFgTcvQ8N4ByjEDZUn%252Fuploads%252Fgit-blob-e84505986b291d1cf02b8ac24fe7db4af6b4733e%252Ff62fd260c99f8d34d4950ec1001629614d31095d.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=ba8e6286&sv=2) 8 **Click Save.** 9 **On Attributes & Claims, click Edit to be consistent with these attributes:** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1400995684-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F79mFgTcvQ8N4ByjEDZUn%252Fuploads%252Fgit-blob-8cdb4bb7a93e576e03f624af4351e402854ae662%252F8a7793cc70060ce40c5de3ee9b01b011005ee621.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=e5768dcd&sv=2) 10 **On SAML Signing Certificate, import this Federation Metadata XML into Command.** 11 **Click Download to save for later.** ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1400995684-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F79mFgTcvQ8N4ByjEDZUn%252Fuploads%252Fgit-blob-eee48b3bb43283405a38a393cd643ebe74d102a3%252Fb4ecdbcf1312fe86c154b7e9f07dde1727636750.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=417f8741&sv=2) If you use a different source attributes for email, configure the attributes according to the source attribute you want to use.s The next dialogs that appear contain tools that you can use after the integration has been finalized. ### [](https://help.verkada.com/government-solutions/single-sign-on-sso/microsoft-entra-id-saml-integration-government-solutions#upload-your-federation-metadata-xml-in-command) Upload your Federation Metadata XML in Command After you have completed the steps in Microsoft Entra ID and downloaded the metadata, [upload the XML metadata file](https://help.verkada.com/command/single-sign-on-sso/saml/enable-saml-for-your-command-account) in Command. ### [](https://help.verkada.com/government-solutions/single-sign-on-sso/microsoft-entra-id-saml-integration-government-solutions#test-the-saml-connection-in-microsoft-entra-id) Test the SAML Connection in Microsoft Entra ID 1 **Once the file is uploaded, in your Microsoft Entra ID, click Test to test the integration. A notification will be sent to all users who have a Command account (invitation to org).** ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1400995684-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F79mFgTcvQ8N4ByjEDZUn%252Fuploads%252Fgit-blob-67a512262a5b97e88b3dc244907bae7a5fd6e955%252Ff3f197e1c60a2b69aaa4e5ac9d7dadce9ac29dde.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=a9826f25&sv=2) 2 **Log in with Sign in as current user. If everything is set up correctly, you should be redirected to the Command platform.** ​ 3 **Log in with single-sign on to verify access to Command.** Microsoft Entra ID does not support nested groups for app access at this time. All users must be direct members of groups for assignment. ### [](https://help.verkada.com/government-solutions/single-sign-on-sso/microsoft-entra-id-saml-integration-government-solutions#log-in-via-the-mobile-application) Log in via the mobile application Android and iOS on Command supports login through SAML. In the **email address** field, enter your email and click **Next**. You should be redirected to your IdP (Microsoft Entra ID) to complete the login process. Last updated 23 hours ago Was this helpful? --- # Okta SAML Integration - Government Solutions | Government Solutions | Verkada Help Verkada Command can integrate with Okta using Security Assertion Markup Language (SAML). SAML handles the authentication process, allowing Okta to be used to manage access to Command, the same as any other Software as a Service (SaaS) application already integrated into your Okta tenant. This means Command can be incorporated into your existing identity framework and be access-controlled based on your current policies in place. * * * ### [](https://help.verkada.com/government-solutions/single-sign-on-sso/okta-saml-integration-government-solutions#before-you-begin) Before you begin For a successful integration, choose the best path for your region: * [Enable SAML for Your Command Account](https://help.verkada.com/command/single-sign-on-sso/saml/enable-saml-for-your-command-account) * **For US orgs**, you will use an existing Verkada application following steps directly below. Create a Verkada Okta app[](https://help.verkada.com/government-solutions/single-sign-on-sso/okta-saml-integration-government-solutions#create-a-verkada-okta-app) Log in to Okta.Go to the Applications page and click Browse App Catalog.In the search bar, type Verkada.Click Add.​Click Done. Attribute mappings[](https://help.verkada.com/government-solutions/single-sign-on-sso/okta-saml-integration-government-solutions#attribute-mappings) Navigate to Directory > Profile Editor > choose the Verkada app > verify the attributesClick on Mappings and Verify App to Okta user mappings​User to App mappings:​ * * * [](https://help.verkada.com/government-solutions/single-sign-on-sso/okta-saml-integration-government-solutions#configuration) Configuration ------------------------------------------------------------------------------------------------------------------------------------------------ 1 **In Okta, select the Sign On tab for the Verkada app, and click Edit.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1400995684-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F79mFgTcvQ8N4ByjEDZUn%252Fuploads%252Fgit-blob-1b411990400f985bbbea74e4ca4d9632f5cd6ff1%252F528acaaf4123dd8ead3b738eecea6a5192c1896f.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=e0b70f59&sv=2) 2 **Scroll down to Advanced Sign-On Settings and enter the** [**Client ID**](https://help.verkada.com/command/single-sign-on-sso/saml/enable-saml-for-your-command-account) **from your Command account.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1400995684-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F79mFgTcvQ8N4ByjEDZUn%252Fuploads%252Fgit-blob-74f4293484a71d32b2185c7265e38f1c37e45203%252Fcab4869bcc9e4ccb6bd7cc20ad48af0774f66282.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=dd464d44&sv=2) 3 **Select Save.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1400995684-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F79mFgTcvQ8N4ByjEDZUn%252Fuploads%252Fgit-blob-8b8db3a71413a7f7aeeb7bd67c65c36b8ceb0d76%252F4d52b88b0aaa325eecb346c77acd160de3718e8b.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=446969dd&sv=2) 4 **Scroll further down to SAML Signing Certificates and click Generate new certificate, if a new certificate does not exist.** 5 **To the right of the certificate, select the Actions dropdown and click View IdP metadata** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1400995684-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F79mFgTcvQ8N4ByjEDZUn%252Fuploads%252Fgit-blob-2420a903551b15e34d1569644982e44f240e4fd2%252F59ebff57b10aaee9573e7c81c7655a6715b7aab4.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=28a2261c&sv=2) 6 **Right click on the metadata and select save as and download as XML file type.** 7 **After downloading the XML file, you need to** [**upload it to Command**](https://help.verkada.com/command/single-sign-on-sso/saml/enable-saml-for-your-command-account) **.** 8 **In the Verify Metadata section, click Run Login Test.** * * * [](https://help.verkada.com/government-solutions/single-sign-on-sso/okta-saml-integration-government-solutions#troubleshooting) Troubleshooting ---------------------------------------------------------------------------------------------------------------------------------------------------- * **Updating usernames (emails) does not automatically take effect in Command**. If you need to change a username, un-assign the user from the SAML app, then re-add the user to the app for the change to take effect. * **If a new user cannot log in via SSO**, it could be because the email domain is not being added to the SSO configuration in the Verkada backend. If the user’s email is outside of the email domains provided when SSO was set up, this causes the user to be unable to use SSO. If this is the cause of the problem, you need to edit the SSO configuration and add this domain to remedy the issue. * **If you experience any other problems with setting up SSO**, contact [Verkada Support](https://help.verkada.com/command/need-help/contact-verkada-support) . Last updated 1 day ago Was this helpful? --- # Loss of Network Connection for Air Quality Sensors | Air Quality | Verkada Help Each Verkada [Air Quality Sensor](https://www.verkada.com/air-quality/sensors#overview) is equipped with an outside LED light. This light indicates its operating status. Verkada offers the [SV11](https://www.verkada.com/sensors/sv11/) series and SV20 series (including [SV21](http://sv21/) , [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) ). A flashing white (SV20 series) or flashing blue (SV11) [status LED](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-status-led) on the front of the sensor indicates the sensor is not communicating with Verkada Command. If you see this behavior: * Check that the network is set up correctly for the sensor’s requirements. * If the problem persists, contact [Verkada Support](https://help.verkada.com/command/need-help/contact-verkada-support) . When sensors are offline, alerts/events do not trigger. They continue to record measurements and sync with Command once they reconnect. [](https://help.verkada.com/air-quality/troubleshooting/loss-of-network-connection-for-air-quality-sensors#sv20-series) SV20 series ---------------------------------------------------------------------------------------------------------------------------------------- The SV20 series may reboot where the device recovers with an internet connection or without one. A reboot technically still results in some data loss (no more than 5 minutes of the latest data). If the SV20 series sensors lose an internet connection, these scenarios can occur: Scenario Status Sensor Result Sensor still has power and has not rebooted after internet loss. Sensor should record data as usual, as long as the sensor gets uninterrupted power. Sensor power cycles after loss of internet within 24 hours. Command still records data as usual. Sensor powers off for more than 24 hours. Command does not record data, because the RTC on the device is no longer reliable. If an SV20 series sensors have a static IP configured, sensor devices have a [recovery mechanism](https://help.verkada.com/air-quality/configuration-and-setup/configure-static-ip-addresses-for-air-quality-sensors-sv20-series-only) to account for configuration mistakes or network changes. The device performs a series of checks at regular intervals to ensure connectivity. In case any of these tests fail or the sensor is unable to establish a TLS connection with the **api.control.verkada.com** endpoint, the device falls back to the DHCP operation and begins a [troubleshooting workflow](https://help.verkada.com/air-quality/configuration-and-setup/configure-static-ip-addresses-for-air-quality-sensors-sv20-series-only) . [](https://help.verkada.com/air-quality/troubleshooting/loss-of-network-connection-for-air-quality-sensors#sv11) SV11 -------------------------------------------------------------------------------------------------------------------------- As of December 13, 2021, the SV11 supports offline storage. If the SV11 sensor loses an internet connection, these scenarios can occur: Scenario Status Sensor Result Device loses internet connectivity. Device continues recording data indefinitely Device reboots at any point while offline. Device does not record data when rebooted. An internet connection must be resumed for data recording to resume, because of the lack of an RTC. When the device reboots, the timestamp is unknown until an internet connection resumes. [](https://help.verkada.com/air-quality/troubleshooting/loss-of-network-connection-for-air-quality-sensors#for-all-sensors) For all sensors ------------------------------------------------------------------------------------------------------------------------------------------------ If any Verkada sensor loses an internet connection, these scenarios can occur: Scenario Status Sensor Result Device goes from online to offline. Device records data. Device is offline (not connected to internet, but still powered on, then reboots with no internet. Device does not record data from that point. Device reboots with no internet, then internet resumes. Device recording resumes. The device must be online for (Command) to retrieve data from it. If the device is offline, you cannot view sensor data. You should receive an alert (if you previously set up [sensor events and alerts](https://help.verkada.com/air-quality/events-and-alerts/configure-air-quality-event-alerts) ) when their device goes offline. Last updated 23 hours ago Was this helpful? --- # Bulk Edit Air Quality Sensor Settings | Air Quality | Verkada Help Using the Verkada Command platform, you can edit a group of Verkada [Air Quality Sensors](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-settings) and their respective settings, all at once. [](https://help.verkada.com/air-quality/configuration-and-setup/bulk-edit-air-quality-sensor-settings#bulk-select-sensors) Bulk select sensors --------------------------------------------------------------------------------------------------------------------------------------------------- 1 **In Verkada Command, go to All Products > Devices.** 2 **Select the air quality sensors you want to modify.** 3 **In the search bar, enter device type: Air Quality to filter only for sensors.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-8b016475de7f2bbfb7165fe59f401dc59c47a86e%252F8446ea2a6c032cbcc513ffd9c4bab19666f008b1.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=459d6f1a&sv=2) ​**Note**: You can only edit in bulk when **Air Quality** is the only device type selected. 4 **Check the box next to each sensor you want to update.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-d4402c1d6a0ea8fe80c2457416fb5e01a92f2c94%252F1ab4c9e3ac5e795e2c28d434e777f630ca9becf4.jpg%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=3d894867&sv=2) Alternatively, at the top, click the black box (with a white vertical line) to select **all** devices within the **site** or **org**. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-c76c357f25ae5bde1708e1697bc04405f3984b33%252Ff163a626b5e30d09c9108f848111cc62618e9599.jpg%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=f7054ce8&sv=2) [](https://help.verkada.com/air-quality/configuration-and-setup/bulk-edit-air-quality-sensor-settings#bulk-edit-sensor-settings) Bulk edit sensor settings --------------------------------------------------------------------------------------------------------------------------------------------------------------- 1 **Once you have selected your devices, at the top right, click Edit Settings.** ​**Note**: This may appear as just a gear icon if you’re viewing from a mobile browser or a low-resolution monitor. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-7e31c41391eb36bbf00be14e6d4c67082fb1ca22%252Fe368d4e884eef048c7c5fa1d66a2d0ccc1f37f5d.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=18b3da62&sv=2) 2 **On Edit Settings, you can modify Site, Location, Sensors and Triggers (Alert Thresholds), Notification Settings, and Offline Notifications. See** [**Air Quality Sensor Settings**](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-settings) **for details on how to configure those settings.** * If a given parameter is identical across all selected devices, it appears as the set value. * If there is a different value set across any of the devices, it appears as **Mixed**. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-af156dcb4e86ddc55dc39e4567bc9915b2558e15%252Ffcc75c891c6a727feada1a9db318a608e91e66cd.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=50d2b705&sv=2) 3 **Some model devices contain more or less sensor capabilities than others. You can edit all available sensor reader settings. If you select a mix of sensor devices with different capabilities:** * Changes are still applied to all sensors. * Devices with additional capabilities are also modified. For example, you can modify **Temperature** and **Carbon Monoxide** sensors for an [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) and [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) . However, because this reading only exists on the SV25, the **Temperature** sensor reading is applied to all devices, and the **Carbon Monoxide** sensor reading is only applied to the SV25s. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-4864348df2fe23fd6638973066d8859c4ff18cb4%252F4a3e8589c50f5e7678680fb69f3acf8e11b61a3b.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=ae157157&sv=2) 4 **You can set up triggers for the selected device(s) that will generate alerts:** a. Click **Set Trigger** or **Edit Trigger** for a sensor reading. b. Set your **Thresholds** and **Event Trigger**. c. (Optional) Click [**Create Alert**](https://help.verkada.com/air-quality/events-and-alerts/configure-air-quality-event-alerts) to set up and receive notifications via Email, SMS, or Push Notifications (to the [Command app](https://help.verkada.com/command/get-started-with-verkada-command) ). d. Once you create your alert, click **Save**. **Note**: When editing devices in bulk, you should see a list of alerts that you are listed as an Editor. [Org Admins](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) will see all alerts. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-845b4a5f3c5c68a9999de9179d667c1f0f5b0526%252F291a74b1bc202e4a992df7c15567156a9b5768bc.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=5bea267&sv=2) ​ 5 **Once your changes are finalized, click Next.** 6 **When prompted, confirm the changes that you are about to make, and click Apply.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-43a8fe269e0e03c5a6b8d562b16faf947420c6a9%252F8a6cdd277f006f9ab4d9c1467cfa0c5ebc48d92c.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=f85b5db6&sv=2) ​**Important**: After a bulk change is applied, it cannot be reverted. Any single device configurations are overwritten with the new values and must be set again from their device settings page. 7 **After the change is confirmed, Command applies the modifications to your devices.** ​ ​**Recommendation**: If you modify multiple devices at once, this step can take some time. Do not exit or leave this page while changes are being applied. Leaving or exiting the page during this step can lead to the change only being partially applied. ​ 8 **Once the changes are completed, and you are prompted with a confirmation or error summary, click Done. If you run into any unexpected errors, contact** [**Verkada Support**](https://www.verkada.com/contact/) **.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-0710472b3dd6b6bb574dc11045a8af64700984da%252F39f1a4f39baa9182f169d364af4b9e5ec3ac36a7.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=442171c0&sv=2) Last updated 22 hours ago Was this helpful? --- # Create a Person of Interest for Air Quality sensors | Air Quality | Verkada Help Verkada cameras allow you to create a Person of Interest (POI) using one or more photos of a person’s face. When paired with an Air Quality sensor, cameras can help identify and track nearby individuals during specific air quality alerts. * The camera paired to the sensor must have People Analytics enabled to support POI creation and people tracking from Air Quality sensors. * Sensor readings must be configured with triggers to generate events. See [Air Quality Sensor Settings](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-settings) for more information. * * * [](https://help.verkada.com/air-quality/configuration-and-setup/create-a-person-of-interest-for-air-quality-sensors#enable-air-quality-people-insights) Enable Air Quality People Insights ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- To activate People Insights on your Air Quality sensors, you first need to activate the feature for your organization. 1 **In Verkada Command, go to All Products > Admin.** 2 **In the left navigation, select Feature Manager.** 3 **Under Air Quality > Sensor People Insights, select Enabled from the dropdown menu.** * * * [](https://help.verkada.com/air-quality/configuration-and-setup/create-a-person-of-interest-for-air-quality-sensors#create-a-person-of-interest-profile) Create a Person of Interest profile ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ### [](https://help.verkada.com/air-quality/configuration-and-setup/create-a-person-of-interest-for-air-quality-sensors#people-analytics-page) People analytics page You can create a Person of Interest profile from the People page. Organizations with POI profiles already created will automatically start tracking Air Quality POI. See [Create a Person of Interest](https://help.verkada.com/verkada-cameras/configuration-and-setup/create-a-person-of-interest) for more information. ### [](https://help.verkada.com/air-quality/configuration-and-setup/create-a-person-of-interest-for-air-quality-sensors#air-quality-events-page) Air Quality events page 1 **In Verkada Command, go to All Products > Air Quality.** 2 **Select your sensor, then choose an event on the right to view the individuals detected during that event.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-aa8c67da27e6134cf2485d86bc3f40dc0d72d14d%252Fc12559124407f8fe7477603e39fd2738787b1a40.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=17a617e7&sv=2) 3 **Thumbnails will populate on the right. Click** **in the top right of the image you want to make a POI.** a. Select **Add Person of Interest**. b. Name the POI. c. Click **Create.** 4 **You can now view profiles and their associated air quality events from the People Insights tab in the left navigation.** POI event footage follows the camera’s retention period. For example, if a camera has 30-day retention, POI event clips will no longer be available after that period. * * * [](https://help.verkada.com/air-quality/configuration-and-setup/create-a-person-of-interest-for-air-quality-sensors#remove-a-poi-profile) Remove a POI profile ------------------------------------------------------------------------------------------------------------------------------------------------------------------- 1 **In Verkada Command, go to All Products > Cameras.** 2 **On the left navigation, click People.** 3 **On the left, under People Lists, select the list the POI profile is in.** 4 **Click the photo of the POI you want to manage.** 5 **Click next to their name and select Remove this person.** Last updated 1 day ago Was this helpful? --- # Air Quality Sensor Calibration | Air Quality | Verkada Help Verkada [Air Quality Sensors](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) have an assortment of different readings that allow you to gain more insight into your building or monitor areas where video monitoring is not allowed. The data available depends on the model of the sensor. You can use Verkada sensors to monitor temperature, humidity, carbon dioxide, and other environmental conditions throughout indoor spaces to identify possible impacts on human health or asset performance. The Verkada Air Quality Sensor calibration interface: * Allows you to calibrate your sensors to your specification needs and easily download a certificate to verify compliance. * Provides another level of actionability and verification to the rich data collected by Verkada sensors. Our sensors are factory-calibrated and rated to the specified accuracy in the [SV20 Series Air Quality Sensor](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) overview for a minimum of 10 years. * * * [](https://help.verkada.com/air-quality/configuration-and-setup/air-quality-sensor-calibration#calibrate-a-verkada-sensor) Calibrate a Verkada sensor ---------------------------------------------------------------------------------------------------------------------------------------------------------- The temperature and humidity sensors onboard the [SV20 Series](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) and [SV11](https://docs.verkada.com/docs/sensors-quick-start-guide.pdf) sensors are individually tested and calibrated. To ensure their continued accuracy, recalibration (using an external reference device) is necessary. For the calibration, Verkada uses transfer standards, which are subject to a scheduled calibration procedure. The calibration of the reference, used for the calibration of the transfer standards, is [National Institute of Standards and Technology](https://www.nist.gov/) (NIST)-traceable through an [ISO/IEC 17025](https://www.iso.org/ISO-IEC-17025-testing-and-calibration-laboratories.html) accredited laboratory. ### [](https://help.verkada.com/air-quality/configuration-and-setup/air-quality-sensor-calibration#enable-sensor-calibration-globally) Enable sensor calibration globally 1 **In Verkada Command, go to All Products > Admin.** 2 **In the left navigation, select Privacy & Security .** 3 **Select Feature Manager.** 4 **On Air Quality > Sensor Calibration, select Enable.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-89759f19589546238f17a003c514fc6172c5501f%252Fba361bfdfd24d75b1f41609bfca8db092033b9fc.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=12d8d761&sv=2) ### [](https://help.verkada.com/air-quality/configuration-and-setup/air-quality-sensor-calibration#view-sensor-calibration-data) View sensor calibration data 1 **In Command, go to All Products > Air Quality .** 2 **On the left navigation, click Calibration .** 3 **On Sensor Calibration, select the reading you want to calibrate.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-05c6436fbf103a4ac019f11cfcf8be742bb307c0%252Fb603425b76341b989c259d4c27fa0263b91e2545.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=9405229e&sv=2) You should be able to see all of your devices, their site, calibration status, current reading if an offset has been applied, when and who updated it, and the next due date. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-571426cf7655f2f6966c59902e3cf160c724025e%252F947b6381138ad1c0b1f9032c1fef755db34ced9a.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=9567e175&sv=2) * **Device Name**—Name of the device you want to calibrate. * **Site**—Location of the device you want to calibrate. * **Status**—Status of the device. * **N/A**—No calibration has been applied. * **Calibrated**—A calibration profile has been applied. * **Past Due**—The calibration profile has expired. * **Current**—Current reading of the selected sensor reading. * **Offset**—Offset error that is applied in the calibration profile. * **Last Updated**—Date the sensor was calibrated. * **Updated By**—User who applied the calibration. * **Due Date**—Due date for the next calibration. The calibration procedure should be done on or before this date. 4 **Click the sensor device you want to calibrate.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-89d9a0ad6d167bea6b0c0f9706bd1c625468bab9%252F82dddcee8acc1c0ddfc8bd427b94c6aca3a33485.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=750d824a&sv=2) 5 **Using a reference device, take a reading while holding your reference device next to your sensor.** _**The closer you are to the sensor, the more accurate your calibration is**_**.** a. Enter this reading in the **Reference Reading** field. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-e8e9566b7ae4f0f608742262ffe218a7557356f8%252F298451fc97fefed78a6603e80e5aa1548a4ec176.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=9111a2e8&sv=2) b. If you see an "Offset exceeds range" warning, this means that the device is reading a value past its typical accuracy. We recommend that you check your reference device and ensure you have properly followed the installation guidelines. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-ff532cfe7ab4c52138ee1bc624ddbbe9bb84f4c1%252Fef7b33106ef70e6163bbfdce1dce7186cdd85610.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=cddfa686&sv=2) c. If you see the "Offset limit reached" warning, this means you’ve reached the offset limit for the reading. Either your reference device is wrong or your sensor may not be operating properly. For assistance, contact [Verkada Support](https://www.verkada.com/contact/) . ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-33b0d7a57bfeb38f0b8a567abe02e53e1ede2b70%252F5f2953f3662359d594837569f2505449d65787d5.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=76f23f54&sv=2) 6 **Click Refresh immediately after taking your reference reading to get the current raw reading from your sensor.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-c12b034765417541f13c3e52e91686defee9af94%252F60ecec65a8bfe902983f6e6110f046c20c23f36e.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=b992d8be&sv=2) 7 **Review your calibration profile and click Next.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-47dc8cc2a99f3eb9e70a6a3e957a9c9a9ab6ff89%252Fb8ed55f082fa0ed247fbb3d73e7092e4f786e4b0.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=2b986588&sv=2) 8 **(Optional) Check the Download Calibration Report box to download a PDF of your calibration report.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-46a29f60a47174ff12af50e1f54153e32e665f75%252Ff9fa9e145fe7ed67deb66899fdbf88b892936610.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=79995f24&sv=2) 9 **Click Apply to confirm your calibration.** A calibration event is then permanently stored in the audit log and the offset is immediately applied to your sensor. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-d97fb55f40d3c8e403139f98934a2e9540c17139%252F2687b1bc8ec90d0a945a11bd731b8b747dcdc4f9.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=3cd4079a&sv=2) * * * [](https://help.verkada.com/air-quality/configuration-and-setup/air-quality-sensor-calibration#download-the-most-recent-calibration-certificate) Download the most recent calibration certificate ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ You may need to download a calibration certificate to provide to a third party. You can do this done during the calibration process or you can retrieve it at a later date using the calibration page. Your sensor must have previously been ​[calibrated](https://help.verkada.com/air-quality/configuration-and-setup/air-quality-sensor-calibration#h_c18dfe453b) to download a calibration certificate. When you download a calibration certificate, it creates an audit entry in the [org-wide audit log](https://help.verkada.com/command/organization-wide-settings/manage-and-view-audit-logs) . ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-98ef3e626e317e565e5beff6df871cd5e219bc65%252F04f65d6a1ca06dfa9ea67115987fcbd94c82883b.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=acf3ec4e&sv=2) ### [](https://help.verkada.com/air-quality/configuration-and-setup/air-quality-sensor-calibration#how-it-works) How it works 1 **From the calibration page, select a reading. As an example, look at a sensor’s Temperature calibration history.** 2 **Hover over the device and at the bottom right, find and click Download Calibration Report.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-5cd967c2825aa14dd8188d5fed3f5c5341db7612%252F86ba032d6aba03ca11838b4e572c8cd8d036c635.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=c6fecd6b&sv=2) 3 **Command processes your request and a browser download of the calibration certificate will be initiated once the file is ready.** [](https://help.verkada.com/air-quality/configuration-and-setup/air-quality-sensor-calibration#view-calibration-history) View calibration history ------------------------------------------------------------------------------------------------------------------------------------------------------ Verkada stores all of the different calibration events and certificates, as the calibration history, for each device. This means that every action is permanently logged, when you: * Apply a calibration * [Reset a device](https://help.verkada.com/air-quality/configuration-and-setup/air-quality-sensor-calibration#h_e5d297a428) to factory calibration settings When you download a calibration certificate, it creates an audit entry in the [org-wide audit log](https://help.verkada.com/command/organization-wide-settings/manage-and-view-audit-logs) . 1 **From the calibration page, select a reading. As an example, look at a sensor’s Temperature calibration history.** 2 **Hover over the device and at the bottom right, click the kebab menu (3 vertical dots).** 3 **Select View Calibration History.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-b3571b8fefc38e6ed5a72381f1bdae236e413a72%252F85bcc70449c9e37d22619bae32334ca7a689dd2e.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=6eaf62cc&sv=2) The history log shows the following: * What event took place (Factory Reset | Calibration) * The date when the event occurred * The offset that was applied * The reference reading that was taken during that calibration * The certificate number for that calibration * The user who made the change [](https://help.verkada.com/air-quality/configuration-and-setup/air-quality-sensor-calibration#download-calibration-reports) Download calibration reports -------------------------------------------------------------------------------------------------------------------------------------------------------------- 1 **Continue from how to** [**View calibration history**](https://help.verkada.com/air-quality/configuration-and-setup/air-quality-sensor-calibration#h_1caa74091c) **.** 2 **Hover over the table row.** 3 **At the right, find the download arrow and click Download Calibration Report.** * * * [](https://help.verkada.com/air-quality/configuration-and-setup/air-quality-sensor-calibration#reset-a-sensors-calibration-to-factory-defaults) Reset a sensor’s calibration to factory defaults ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Command allows you to use the factory calibration settings or reset your sensor back to factory default settings if a calibration profile is no longer needed. 1 **Your sensor must be** [**calibrated**](https://help.verkada.com/air-quality/configuration-and-setup/air-quality-sensor-calibration#h_c18dfe453b) **to reset it to factory defaults.** 2 **When you reset a sensor back to factory calibration settings, it creates an entry in the sensor’s calibration history.** 1 **From the calibration page, select a reading. As an example, look at a sensor’s Temperature calibration history.** 2 **Hover over the device and at the bottom right, click the kebab menu (3 vertical dots).** 3 **Select Reset Factory Settings.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-82785feee82b041589ef7c9877d7b0eb64c72bb6%252Fe9936b63ccffb1f65cf4469c5dcaa7671b23c252.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=ad07b2ec&sv=2) 4 **Click Reset to confirm to reset the factory settings for the specified device.** * If successful, you will see a "Factory calibration reset complete" banner. * If unsuccessful, contact [Verkada Support](https://www.verkada.com/contact/) . * * * [](https://help.verkada.com/air-quality/configuration-and-setup/air-quality-sensor-calibration#faq) FAQ ------------------------------------------------------------------------------------------------------------ Do I need to calibrate my sensor?[](https://help.verkada.com/air-quality/configuration-and-setup/air-quality-sensor-calibration#do-i-need-to-calibrate-my-sensor) Most customers do not need to calibrate their sensors. However, you may be required to annually calibrate your devices. With the **Air Quality Sensor Calibration** page, you can now use a reference device to calibrate your sensors. Once calibrated, you can [download a PDF certificate](http://help.verkada.com/en/articles/7852972-air-quality-sensor-calibration#h_5729ad46fa) showing that your sensor was calibrated. Which Verkada sensors can be calibrated?[](https://help.verkada.com/air-quality/configuration-and-setup/air-quality-sensor-calibration#which-verkada-sensors-can-be-calibrated) Follow the [calibrate an air quality sensor](http://help.verkada.com/en/articles/7852972-air-quality-sensor-calibration#h_c18dfe453b) steps to calibrate all Verkada sensors, including the last-generation [SV11](https://docs.verkada.com/docs/sensors-quick-start-guide.pdf) s and the latest [SV20 Series](https://help.verkada.com/en/articles/6732870-what-s-new-in-the-sv20-series) sensors (SV21s, SV23s, SV25s). What kind of calibration does Verkada offer?[](https://help.verkada.com/air-quality/configuration-and-setup/air-quality-sensor-calibration#what-kind-of-calibration-does-verkada-offer) Currently, the **Air Quality Sensor Calibration** page allows you to apply a standard one-point linear calibration to your sensors. Verkada uses a single point to calculate the difference between the reference value and the raw reading to create an offset correction for the error between the two, and then apply that offset to the sensor reading. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-a70a33e8d83f0e0623f6ea6275d3ac657ae2b43d%252F89dc98f46f498f22d766c4afc025fcae90a87125.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=9373b512&sv=2) For example, if your sensor’s raw Temperature reading is 72˚F (22˚C), but your reference device shows 71˚F (21˚C), and your offset is – 1˚F. Once the calibration is applied, if your raw reading is 76˚F (24˚C), your sensor will show 75˚F (23˚C) in Command. Who can calibrate a Verkada sensor?[](https://help.verkada.com/air-quality/configuration-and-setup/air-quality-sensor-calibration#who-can-calibrate-a-verkada-sensor) **Only Org Admins can calibrate Verkada sensors.** The Org Admin must also be a Site Admin for the sites in which the sensors are located. If the Org Admin doesn’t have Site Admin permissions, they can’t view the sensors. To understand role permissions, see [Detailed Role Breakdown for Command Users](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) . Which sensor readings can be calibrated?[](https://help.verkada.com/air-quality/configuration-and-setup/air-quality-sensor-calibration#which-sensor-readings-can-be-calibrated) * Temperature * Humidity * Carbon Dioxide * Carbon Monoxide * Noise Level * PM 2.5, 4.0, and 10.0 Does setting the calibration affect past data?[](https://help.verkada.com/air-quality/configuration-and-setup/air-quality-sensor-calibration#does-setting-the-calibration-affect-past-data) No, calibrating your devices does not affect the past data collected by your sensors. Only the data from the point of calibration onwards has the offset incorporated into it. What kind of reference devices does Verkada recommend using?[](https://help.verkada.com/air-quality/configuration-and-setup/air-quality-sensor-calibration#what-kind-of-reference-devices-does-verkada-recommend-using) Verkada recommends using NIST Traceable Temperature/Humidity sensors, such as the _Traceable Barometric/Temperature/Humidity Wi-Fi Data Logger_ or the _Fluke - 52-260HZCAL 52-2 Dual Input Digital Thermometer with a NIST-Traceable Calibration Certificate with Data_ for calibrating your temperature or humidity sensors. Verkada recommends the _TSI DustTrak™ DRX 8533_ for PM 2.5, PM 4.0, and PM 10 calibration. Last updated 22 hours ago Was this helpful? --- # Integrate Verkada Cameras with Air Quality Sensors | Air Quality | Verkada Help Pair your Verkada Air Quality Sensor with a Verkada Camera to gain visual evidence into environmental conditions or events. Spot events, identify problematic areas or conditions, protect your people and assets—all on a single pane of glass. [](https://help.verkada.com/air-quality/configuration-and-setup/integrate-verkada-cameras-with-air-quality-sensors#add-a-camera-feed-to-your-air-quality-sensor) Add a camera feed to your air quality sensor ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ You may want to add a camera feed so that you can see what’s going on near the sensor at a quick glance. 1 **In Verkada Command, go to All Products > Air Quality.** 2 **Select a sensor where you want to add a camera feed.** 3 **At the top right, click the Camera icon.** 4 **Select which camera you want to add to this sensor.** 5 **Click Confirm > Done to add the camera.** You should see the camera feed appear next to the sensor information. [](https://help.verkada.com/air-quality/configuration-and-setup/integrate-verkada-cameras-with-air-quality-sensors#change-or-remove-a-camera-feed-from-a-sensor) Change or remove a camera feed from a sensor ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ 1 **In Verkada Command, go to All Products > Air Quality.** 2 **Select a sensor where you want to change or remove a camera feed.** 3 **At the top right, click Edit Camera (pencil icon).** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-7351155b1162481a04808d2990390b3bb22741d9%252F7aa2db0f278f90cdb85c41aaddd9f6cc6cfb9f94.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=fa168d94&sv=2) 4 **On Select Camera, change which camera is selected.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-7b2c84ad9634820fbbf9ebbb1ea85909e0df5ee7%252F9f6f5a49be474f97312a144eb10b3c1133be543d.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=f7787bbf&sv=2) 5 **(Optional) On Edit Settings > Camera, remove the feed completely:** a. Click the **Settings** (gear) icon. b. Click **Remove Camera**. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-eefbd75462bc92c811114b01f805f05b982fa43c%252F372da219e8d66119abc43e72056be409a34cc44e.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=c7b7586e&sv=2) 6 **Click Apply to finalize the settings.** [](https://help.verkada.com/air-quality/configuration-and-setup/integrate-verkada-cameras-with-air-quality-sensors#camera-and-sensor-graph-overlay-view) Camera and sensor graph overlay view -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 1 **In Verkada Command, go to All Products > Air Quality .** 2 **Select a sensor to view.** 3 **At the top right, click to change views.** 4 **You should see the sensor graph overlayed on top of the camera feed with sensor events listed on the right. The events are scrollable and may be filtered by date, time, and/or sensor reading.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-ff0d62a6e34abc288a46a4b34c86f56c8f6e6338%252F24ca34cf88fab02b4fea796a874a7b787377997b.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=b3bcd221&sv=2) 5 **Hover over the camera feed and click to access the sensor graph and camera overlay mode in full-screen mode.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-2142f0485b7b129e4057d499592f599fe6832eb2%252F8ef4fcf33029d9b45c240202f68b359f9a496b9b.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=7da7c583&sv=2) The ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-a8470e2d5d3e2d2bdf1c7dd44572f9422814f622%252F16211ea8294bbc9508520d83b7a63923f52dbe80.png%3Falt%3Dmedia&width=300&dpr=4&quality=100&sign=d880001b&sv=2) button will take you to the camera history player, where you can archive footage. Last updated 19 hours ago Was this helpful? --- # Air Quality Event Analytics | Air Quality | Verkada Help Verkada’s [air quality sensors](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) are designed to give you the ability to monitor environments for abnormal conditions automatically and in real time. With sensor analytics, you can track and monitor alert trends, environmental trends, and behaviors across your organization, at the site and device levels. [](https://help.verkada.com/air-quality/events-and-alerts/air-quality-event-analytics#access-event-analytics) Access event analytics ----------------------------------------------------------------------------------------------------------------------------------------- The **Event Analytics** page makes it easier to view and analyze your sensor data. You can now specify which readings to evaluate to see how many alerts are generated on a daily, weekly, or monthly basis. The page has an easy-to-use graph to help identify trends and a table to show the count of total alerts and associated changes. 1 **In Verkada Command, go to All Products > Air Quality.** 2 **On the left navigation, click Analytics .** 3 **On Event Analytics:** a. Click the sensor reading dropdown and choose which reading you want to view. You can select from any of the [Air Quality sensor readings](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) available; however, only alerts on configured and supported devices contribute to the data. b. Click the **timeframe** dropdown (by default, **Weekly** is selected) and choose which timeframe you want to view. * **Hourly**—Shows an hour-by-hour view of the selected day. * **Daily**—Shows a day-by-day view of the past 12 days. * **Weekly**—Shows a week-by-week view for the past 12 weeks. * **Monthly**—Shows a month-by-month view for the past 12 months. g. Click the **sites** dropdown (by default, **All Sites** is selected), and individually select the sites you want to review. If you’re only interested in a portion of the devices in the sites, we recommend that you create a new subsite for those devices. ### [](https://help.verkada.com/air-quality/events-and-alerts/air-quality-event-analytics#understand-the-analytics-table) Understand the analytics table Within the detailed view: * You see a breakdown of how your selected sites have performed over the time interval selected compared to their previous performance. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-7e60e07754aff8a999a33fe5bb9ec81da79f2e58%252F2ee5b828eb51c8effd08cb0ffcc600c8e00402bf.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=9b668bea&sv=2) * At the top left, you see a composite summary of the reading for all selected sites over the time interval selected. You may also select a new sensor reading to analyze. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-aa947f8c319be8e8b46df9c8763164b745e4bbc3%252Fb45b82a0489e75d6b7dc0aa119dae372eded0233.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=b06b023b&sv=2) * You can select any of the columns to be the active tab. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-f7ca3c0b183326f34760df66ab2a0526a8c643a7%252Fea0d1875cc62f5bc8ac16e3e60b1519bde9f3ef6.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=36773495&sv=2) * **Totals Alerts** show the sum of all alerts over the time interval selected. * The number above the column and in the summary section on the top left of the page is the total sum of the **Totals Alerts** for all sites. * **Change** shows the change as a percentage-based reference over the time interval selected. * A **red upward arrow** indicates an uptick in alerts over the measured period. * A **green downward arrow** indicates a decrease in alerts over the measured period. * No change over time is expressed as **0%**. * An increase from zero events in the reference column is considered undefined (division by zero) and is expressed as **–%**. * The most alerts can increase over time is infinite with a **2x increase** corresponding to a **100% change**. * The most alerts can decrease over time is finite converging to 0% where a **2x decrease** corresponds to a **50% change**. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-b56a5da9b23a8de3d5c3ab83b232cfef83dfd975%252F9c12fac276533900904e253ed2b605f999d58e99.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=17bac57c&sv=2) Last updated 19 hours ago Was this helpful? --- # Audio Recording with the SV25 | Air Quality | Verkada Help The Verkada [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) Air Quality Sensor has audio recording capability that provides up to **365** days of audio recording on SV25s where you can easily review, save, and download audio clips directly from Verkada Command. **Model (SKU)** **Audio Retention** **Storage** SV25 **90 Days** 32 GB SV25-128 **365 Days** 128 GB Audio recording pairs natively with the other sensor readings on the SV25 and Verkada cameras and other devices, giving important context into your environment. With audio recording, SV25 you can protect, monitor, and manage your environments across a range of use cases, including: * Adding audio context and verification to noise and motion alerts * As a tool to comply with state regulations that require audio recording in specific school settings [](https://help.verkada.com/air-quality/sensor-data/audio-recording-with-the-sv25#enable-audio-recording) Enable audio recording ------------------------------------------------------------------------------------------------------------------------------------- Org Admins want visibility and control over which devices make use of audio recording. To help address these needs, Verkada has implemented processes to help ensure that audio recording is deployed in a way that respects individual privacy. By default, all audio recording capabilities are **disabled on all SV25 units**. This means that no SV25 records audio out of the box. Only Org Admins can enable the feature. 1 **Admins must review and accept a set of Terms and Conditions from within the Privacy and Security page within Command.** 2 **Once the Terms and Conditions have been accepted, Org Admins need to enable audio on a per-device level. This ensures that audio recording is enabled only on an as-needed basis.** 3 **Org Admins can also choose between "live only audio" (no audio is recorded) or "live and recorded audio" (up to 365 days of audio is recorded on the device and is available in Verkada Command).** 4 **There is a ‘kill switch’ available at the Organization level. This switch allows Org Admins to disable audio recording on all sensors with the flip of a switch. The control also deletes any audio already recorded on any SV25 device.** 5 **The data ownership, responsibility, and authorization for the use of audio recording is at the sole discretion of the customer.** Audio recordings are stored on the device, not in the cloud, and can be downloaded from the device through Command when needed for investigations. [](https://help.verkada.com/air-quality/sensor-data/audio-recording-with-the-sv25#enable-audio-per-device) Enable audio per device --------------------------------------------------------------------------------------------------------------------------------------- These options are only available if the org-level permissions and Terms and Conditions have been set and accepted. 1 **Under the SV25 settings menu, or when multiple SV25s are selected for bulk editing, you should see the Audio tab with the option to enable Live Audio and Recorded Audio.** ​**Note**: To have recorded audio work, you must also have live audio enabled. ​ 2 **Once these settings are confirmed, the device refreshes and sensor readings are unavailable for about 10 seconds. The device is always expected to refresh if either of these settings is changed.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-91b4bba4c3e124a5d433ab481ad10854a635e360%252Fa78d23fde90d4aac8c154de63b336f5838315e3e.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=af1a047c&sv=2) 3 **The device should now have an Audio pill at the bottom of the list of enabled sensors. If only the live audio is enabled, you only see the option to view live audio and not historical.** 4 **If recorded audio is also enabled, you should be able to see the same navigation scrubber you are familiar with from other sensor readings.** 5 **Audio shows a waveform based on the detected noise level picked up from the noise level sensor, which is not capable of audio recording alone. Because of this, it is possible to see a waveform that reflects the noise level of the environment despite audio recording being turned off or a recorded segment being missing or unavailable.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-181d27fccb111e62baa85a862693fba73e22a87b%252F7f2cc94424b95cdb690a0fadda30e66552e85753.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=68ce254d&sv=2) 6 **You are now able to listen to historic audio by scrubbing to that time window and selecting it like any other sensor reading. The audio plays from that moment. The Verkada Command tab must remain active on your browser for audio to continue playing for both historic and live. Switching to another tab stops your audio playback.** [](https://help.verkada.com/air-quality/sensor-data/audio-recording-with-the-sv25#download-a-segment-of-audio) Download a segment of audio ----------------------------------------------------------------------------------------------------------------------------------------------- When you download an audio segment, it is very different from a camera archive, as the requested portion of audio is never stored on the cloud, rather only emailed to you. This means that deleting the email containing the past audio archives will mean that the archive is lost forever. 1 **On the audio service bar, click the Download icon. You should see a time selection download prompt.** ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-3313ae5feee3f0f7cd0c53c4661767dd74707e1d%252F6181ec73eb820914fc5c77606c85e840e2e17c1e.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=ee1b99d&sv=2) 2 **Define the span of time and click Download to have a copy of that clip sent to your email.** ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-376c3c0cdf7270e7c0b6e901fe460ccce9f2ba93%252F6fb2ca94bba19e71fd181b4add9f763a5184c172.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=881cd3ca&sv=2) For security reasons, the **Download** button does not allow the direct file to be downloaded. [](https://help.verkada.com/air-quality/sensor-data/audio-recording-with-the-sv25#erase-audio) Erase audio --------------------------------------------------------------------------------------------------------------- If for any reason you want to erase your recorded audio or disable the feature, you can set the **live** or **historical** option to disable from the SV25s device menu. Last updated 19 hours ago Was this helpful? --- # Air Quality Alerts Migration | Air Quality | Verkada Help On November 15, 2023, Verkada [Air Quality Sensor](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) customers will be migrated to a new alert experience. You can now display and view your Verkada [Air Quality Sensor](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) alerts from the [**Alerts**](https://help.verkada.com/verkada-cameras/events-and-alerts/create-alerts-across-verkada-products) page in Verkada [Command](https://help.verkada.com/command/get-started-with-verkada-command) , making it easier to manage all alerts from a single page across your Verkada products. You can also manage your alert workflows on the **Admin** > [**Manage Alerts**](https://help.verkada.com/verkada-cameras/events-and-alerts/manage-alerts-across-verkada-products) page. This new feature expands alert functionality: * Org Admins can now enable push notifications for all sensor events, including vape, temperature, and more. * With push notifications, users can now use the Command mobile app to receive a notification straight to their mobile device. * Org Admins can now subscribe groups to a notification, and sensor alerts now have a Command user group, allowing for much easier alert-recipient management. [](https://help.verkada.com/air-quality/events-and-alerts/air-quality-alerts-migration#new-migration-process) New migration process ---------------------------------------------------------------------------------------------------------------------------------------- ### [](https://help.verkada.com/air-quality/events-and-alerts/air-quality-alerts-migration#alert-management) Alert management Prior to the new migration, alerts were managed on the sensor’s detail settings page: ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-5f0548102cffe0fb17b18821d9d44caa23382518%252Fc5205d18ab0900e770383e87111c09de6fbb4ef8.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=c91c2d31&sv=2) ### [](https://help.verkada.com/air-quality/events-and-alerts/air-quality-alerts-migration#alert-creation) Alert creation During the migration process, the new alert rules are created on a **per-user** basis. The migration created one (1) alert rule for each user, for each of the following: 1 **One or more sensor alerts. Multiple readings and devices will be grouped together in this alert as a union.** 2 **One or more sensor zone events.** 3 **One or more sensor status events (offline alerts).** In the previous alert system, sensor offline notifications were email only. Now you can receive SMS or Push notifications in addition to email. This means that post-migration, you can have, **at most**, **3 alert rules** if you were subscribed to all 3 of the different use cases. For each of these alerts, your previous sensor notification settings schedule was used for the schedule in the new alert system. This also includes the **Disable when alert ends** setting. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-a3695d3f9917d59e59a7f2642cd3c704021b05f8%252F26a40fb2f86024b6087cf19a42f0ea365a7febb0.png%3Falt%3Dmedia&width=300&dpr=4&quality=100&sign=372b45d3&sv=2) If the SMS method was enabled in the previous alert system, the **Push** notification method was automatically enabled in the new alert system. ### [](https://help.verkada.com/air-quality/events-and-alerts/air-quality-alerts-migration#alert-name-format) Alert name format The alert name is generated using the following format and depends on the alert type: * User name’s sensor alerts * User name’s zone alerts * User name’s status alerts ### [](https://help.verkada.com/air-quality/events-and-alerts/air-quality-alerts-migration#editor-role) Editor role The new alert system introduces the role of **Editor**. Editors can see, modify, and delete their alerts. * In the previous alert system, all [Site Admins](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) were Editors. * In the new alert system, all Site Admins who oversee devices where a user was subscribed are now added as an Editor. Any **new** Site Admins are not automatically added as an Editor. ### [](https://help.verkada.com/air-quality/events-and-alerts/air-quality-alerts-migration#how-this-new-alert-system-works) How this new alert system works At a high level, here are some helpful examples that show how this new alert system works: * If you have 10 users subscribed to vape alerts on 100 sensors, you would have 10 alert rules. * If you have 1 user subscribed to vape alerts on 100 sensors, you would have 1 alert rule. * If you have 2 users subscribed to vape alerts on 1 sensor, you would have 2 alert rules. * If you have 5 users subscribed to vape and temperature alerts on 10 sensors, you would have 5 alert rules. * If you had one user who was subscribed to sensor alerts, sensor zone alerts, and sensor offline alerts set up, they would have 3 alert rules: * John Doe’s sensor alerts * John Doe’s sensor zone alert * John Doe’s sensor status alerts ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-f10a6e3b01c5b91820b3f4664afa2188f779a0f7%252Fa32eaa51058d4b663fc9af2fb0f4c503df6a87cb.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=eaeef2dc&sv=2) ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-a4ca38921b5757fa05477a772baca62aec01d13a%252F9bab6d09e1ccd227c58824c94f9215cb991c0ed3.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=1a0a0737&sv=2) [](https://help.verkada.com/air-quality/events-and-alerts/air-quality-alerts-migration#user-journey-from-previous-to-current-alert-system) User journey from previous to current alert system -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- The goal of this topic is to take you through the pre and post-migration process. 1 **Explore how your alerts appeared in the** [**previous alerts system**](https://help.verkada.com/air-quality/events-and-alerts/air-quality-alerts-migration#h_8475fadc96) **.** 2 **Explain how your alerts appear in the** [**new alert system**](https://help.verkada.com/air-quality/events-and-alerts/air-quality-alerts-migration#h_fc29f16609) **.** ### [](https://help.verkada.com/air-quality/events-and-alerts/air-quality-alerts-migration#previous-alert-system-example) Previous alert system (example) In the previous system, where "Dominic" is the user with these details: * Subscribed to 3 sensors: vape, noise, and temperature alerts. * Scheduled from Monday through Friday, 8:00 AM to 6:30 PM (as shown below). * **Disabled when alert ends** disabled (meaning Dominic would receive a second notification when the alert ended). * In this example, there is another Site Admin ("Will") who can modify these devices. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-929c2e825356bc09b98f26d259b1f98784b9b919%252F79ea19c5364299e217da024c38c21da766ff6aae.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=9d0debb3&sv=2) * "Dominic" is also subscribed to one (1) device’s offline alerts: ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-12a4e35d353363dae91065dfc26c65a6c0fda0d6%252F2f8b83f10538532334e47d0eb5dde04ef58714bf.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=ddbba364&sv=2) * As well as one (1) zone alert: ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-74dba6fe3dac1edf6cc45a0d4b80ea9ee64f37f7%252F6b8832766e755167a3614202b267cd5a4829304e.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=3e05f4da&sv=2) ### [](https://help.verkada.com/air-quality/events-and-alerts/air-quality-alerts-migration#new-alert-system-post-migration) New alert system (post-migration) In the new alert system, you can go to the [**Manage Alerts**](https://help.verkada.com/air-quality/events-and-alerts/air-quality-alerts-migration#h_38985b302d) page to see your migrated alerts. #### [](https://help.verkada.com/air-quality/events-and-alerts/air-quality-alerts-migration#manage-alerts-page) Manage Alerts page 1 **In Verkada Command, go to All Products > Admin.** 2 **Under Org Settings, click Manage Alerts.** 3 **(Optional) At the top, you may need to click Shared Alerts to filter alerts.** All migrated air quality sensor alerts are shared alerts. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-9180ae548978dd29cc1faecfe50ce0ac1e108979%252F0ed08a5a86fed1775121246e9a559686261bbc07.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=ac87260&sv=2) From this example, you see 3 alerts in the list (see below for example details): 1 [**Dominic’s sensor alerts**](https://help.verkada.com/air-quality/events-and-alerts/air-quality-alerts-migration#h_4767aea41c) **rule—Contains any sensor device readings he was subscribed to. In this case, it was 3 sensors and he was subscribed to the vape, noise, and tamper sensor readings.** 2 [**Dominic’s status alerts**](https://help.verkada.com/air-quality/events-and-alerts/air-quality-alerts-migration#h_523b84ebac) **rule—Contains any sensor offline alerts he was subscribed to. In this case, it was one sensor.** 3 [**Dominic’s zone alerts**](https://help.verkada.com/air-quality/events-and-alerts/air-quality-alerts-migration#h_4f1c9fe5ab) **rule—Contains any sensor zones he was subscribed to. In this case, it was 1 sensor zone. Previously, sensor zones would alert to all readings. This means that all sensor readings are selected during the migration process.** #### [](https://help.verkada.com/air-quality/events-and-alerts/air-quality-alerts-migration#dominics-sensor-alerts) Dominic’s sensor alerts **Events setup** Dominic is subscribed to the **3** devices as before, and the union of any readings he was subscribed to (in this case: vape, noise, and temperature). Dominic’s **Disable when alert ends** setting was also successfully migrated. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-68396ed65bfcf1c97dd0aa9861eb1dfdcbca3af9%252Ff55af56302f7095b37e2e516aabb8bfdccea6eb6.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=34ff7750&sv=2) **Recipient setup** For migrated alerts, the **Recipients** section should only contain one (1) single user. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-b0b563b5894783bb60c14ba90c2bae5972ecb4af%252F16bf8aaa2ae7c05c4bccdce3225514b3250465e9.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=a91ae900&sv=2) **Schedule setup** Dominic’s previous schedule of Monday through Friday, 8:00 AM to 6:30 PM was successfully migrated. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-a69d7c1ade3fc6dcea8db1afb6c81a7bc5e568fa%252F46bf38815876dd902500a816b0439304e3b8ebd9.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=77e41286&sv=2) **Settings setup** Will is also an Editor because he was a Site Admin for this device. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-2334154af5a3ef9c69c56e38200af59f368623d5%252F79980c98f17749919eb2cac85e18e0ed5f68e3cd.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=f3fc50b&sv=2) #### [](https://help.verkada.com/air-quality/events-and-alerts/air-quality-alerts-migration#dominics-status-alerts) Dominic’s status alerts **Events setup** Dominic is subscribed to Sensor Status alerts (offline alerts) to the same device as before. Dominic’s **Disable when alert ends** setting was also successfully migrated because, with offline alerts, you always want to know when the device comes back online. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-a434b0db2e94bc5025f7dc08ef717d242dc336d4%252Fda44f149be92cea0fd0b8a394b8e188d466a0500.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=a61a941d&sv=2) The [Recipients](https://help.verkada.com/air-quality/events-and-alerts/air-quality-alerts-migration#h_d7df37001b) and [Schedule](https://help.verkada.com/air-quality/events-and-alerts/air-quality-alerts-migration#h_f782cf14ac) setup will always be the same. **Settings setup** Will is also an Editor because he was a Site Admin for this device. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-9697547ef8f3336e4a9b3bba7ae8f8cea2a5b420%252Fc7870afff63375869219e7634832f868c613f54d.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=443cdfd9&sv=2) #### [](https://help.verkada.com/air-quality/events-and-alerts/air-quality-alerts-migration#dominics-zone-alerts) Dominic’s zone alerts **Events setup** Dominic is subscribed to a single sensor zone alert just as before. All sensor events are selected because, in the previous alert system, zone alerts would notify on any alerts triggered. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-d156ae4dc28efdcf8fabd51f6ba2abf94b509d8e%252F8a80f0aa2aa5b618cb132a95c306194967868ab6.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=66d60e12&sv=2) The [Recipients](https://help.verkada.com/air-quality/events-and-alerts/air-quality-alerts-migration#h_d7df37001b) and [Schedule](https://help.verkada.com/air-quality/events-and-alerts/air-quality-alerts-migration#h_f782cf14ac) setup will always be the same. **Settings setup** Will is also an Editor because he was a Site Admin for this device. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-104027049c118f3cde9d822a73a9ba7232d9778f%252Fb1cb12ae35a107017b65c926b4725dfcdf5a750b.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=f7d0cdfb&sv=2) Last updated 1 day ago Was this helpful? --- # Roles and Permissions for Command | Command | Verkada Help This article describes the set of roles and associated permissions for [Verkada Command](https://help.verkada.com/command/get-started-with-verkada-command) . ### [](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command#roles-and-permissions-by-verkada-product) Roles and permissions by Verkada product All users added to the organization can log in to Command but need additional permissions to view all the products. Select a product from the list below for more information on its roles and permissions. * [Roles and Permissions for Access Control](https://help.verkada.com/access-control/roles-and-permissions-for-access-control) * [Roles and Permissions for Air Quality Sensors](https://help.verkada.com/air-quality/roles-and-permissions-for-air-quality-sensors) * [Roles and Permissions for Alarms](https://help.verkada.com/new-alarms/roles-and-permissions-for-new-alarms) * [Roles and Permissions for Classic Alarms](https://help.verkada.com/classic-alarms/roles-and-permissions-for-classic-alarms) * [Roles and Permissions for Cameras](https://help.verkada.com/verkada-cameras/configuration-and-setup/roles-and-permissions-for-cameras) * [Roles and Permissions for Intercom](https://help.verkada.com/intercom/roles-and-permissions-for-intercom) * [Roles and Permissions for Gateway](https://help.verkada.com/connectivity/roles-and-permissions-for-gateway) * [Roles and Permissions for Guest](https://intercom.help/verkada/en/articles/5715499-roles-and-permissions-for-guest) * [Roles and Permissions for Mailroom](https://help.verkada.com/mailroom/roles-and-permissions-for-mailroom) * * * [](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command#organization-level-roles) Organization-level roles --------------------------------------------------------------------------------------------------------------------------------------------------- Organization member[](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command#organization-member) All users added to an organization are organization members. A user added to the organization who does not have admin permissions has the minimum level of access needed to sign in to the organization. Access allows you to: * View the organization when logged in. * Configure personal notifications (which alerts the user wants to receive). * Set personal 2-Factor Authentication (2FA) settings. Command User Admin[](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command#command-user-admin) Any organization member can be upgraded to a Command User Admin. Access allows you to: * Add and remove users, designate their roles, and assign them to groups. * Add and remove groups and assign users to groups. * Add and remove contacts for individuals outside of your organization. * Create and assign alerts to groups and users in the organization. * Manage and restrict access to Shared Links for users in the organization. * Enable Support Access. Organization Admin[](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command#organization-admin) Any organization member can be upgraded to an Organization Admin. Access allows you to: * View the organization when logged in. * Configure personal notifications (which alerts the user wants to receive). * Set personal and org-wide 2FA settings. * Create floor plans. * Add, delete, and modify access users. * Set user and group permissions for the organization and all sites/subsites. * Configure org-wide settings, including maximum archive duration, enable/disable cloud backup globally, and default camera playback quality. * Rename or delete the org. * Create new sites and subsites. * Add and remove devices. * Adjust camera stream encoding settings. If the [Global Site Admin](https://help.verkada.com/command/users-and-permissions/customize-roles-and-permissions) policy is enabled, all Org Admins will automatically be granted Site Admin access to all sites. * * * [](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command#set-permissions) Set permissions --------------------------------------------------------------------------------------------------------------------------------- Command User Admin[](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command#command-user-admin-1) **Grant permissions** In Verkada Command, go to All Products > Admin .Under Admin > Users & Permissions, click Users.Select a user to grant permissions.Next to Command Roles click .a. Select Command User Admin. b. Click Apply Changes. **Revoke permissions** In Verkada Command, go to All Products > Admin .Under Admin > Users & Permissions, click Users.Select a user to grant permissions.Next to Command Roles click .a. Select None. b. Click Apply Changes. Command User Admins cannot modify the Organization Admin role. They can assign or remove Command User Admins but cannot elevate or lower Organization Admin permissions. Organization Admin[](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command#organization-admin-1) **Grant permissions** In Verkada Command, go to All Products > Admin .Under Admin > Users & Permissions, click Users.Select a user to grant permissions.Next to Command Roles, click .a. Select Org Admin. b. Click Apply Changes. **Revoke permissions** In Verkada Command, go to All Products > Admin .Under Admin > Users & Permissions, click Users.Select a user whose permissions you want to revoke.Next to Command Roles, click .a. Select None. b. Click Apply Changes. * * * [](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command#faq) FAQ --------------------------------------------------------------------------------------------------------- Why has my organization disappeared?[](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command#why-has-my-organization-disappeared) A user must be a member at the organization level to see the organization in the dropdown when they log in. If a user is a member of an organization, they appear on the user list that Organization Admins and Site Admins can access in Command. If your organization disappeared, it can be due to one of these reasons: * Your user account was removed from the organization. * The organization was deleted. **Troubleshoot** * If you are the affected user, contact the Organization Admin and request to re-add you to the organization. * If a user has reported this to you, verify they are a member of the organization. Why are cameras missing from my organization?[](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command#why-are-cameras-missing-from-my-organization) Sites do not inherit users from the organization or other sites. Users who are members of the organization cannot see cameras unless they have explicitly been granted permissions to the site or sub-site where the cameras reside. * If you are the affected user, contact the Organization Admin or Site Admin and request access to the desired sites and subsites. * If a user has reported this to you, grant them access to the desired sites and subsites. Why can’t I access certain features or settings, such as other users?[](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command#why-cant-i-access-certain-features-or-settings-such-as-other-users) If you are unable to access certain features or settings, you don’t have sufficient permissions. Only Admins can access all features and settings. Organization Admins are not automatically escalated to Site Admin for any site. This is a separate feature set. Therefore, Organization Admins do not inherently have permission to view any one particular site, but they can assign themselves the required roles to see their desired sites. **Troubleshoot tips:** * If you are the affected user, contact the Organization Admin or Site Admin and request that they elevate your permissions to Organization Admin or the desired site or subsite. * If a user has reported this to you, elevate their permissions on the organization or desired site or subsite. **Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=7ldbcKo8u0Q) . Last updated 1 day ago Was this helpful? --- # Third-Party VMS Integrations for Air Quality Sensor Events | Air Quality | Verkada Help Air Quality sensors offer your organization a way to monitor essential indoor air quality factors, such as [vape index](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) , [temperature](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) , [humidity](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) , and more. Third-party video management system (VMS) integrations allow Verkada sensors to send alert events to on-premise VMS, such as Milestone X-Protect, Wisenet WAVE, or exacqVision. These integrations allow you to receive and view sensor event data within your VMS system, eliminating the need to build custom APIs or manually match sensor events to camera footage. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-fe0498641943c044c411b519e87337b33500b76a%252F8ec4da5f1f1f0425f7a1241d4d724098c86537cb.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=463990ca&sv=2) Each VMS integration varies based on integration prerequisites set by the manufacturer. You will receive an alert that can be easily linked to a camera and includes the sensor name, sensor reading, reading value, threshold surpassed, and timestamp. At this time, the **video integration feature only sends alert event data**. It does not send time-series data or graph data. #### [](https://help.verkada.com/air-quality/configuration-and-setup/third-party-vms-integrations-for-air-quality-sensor-events#supported-third-party-vms-providers) Supported third-party VMS providers * Milestone X-Protect * Wisenet WAVE * exacqVision * * * [](https://help.verkada.com/air-quality/configuration-and-setup/third-party-vms-integrations-for-air-quality-sensor-events#enable-third-party-vms-integrations) Enable third-party VMS integrations -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- You need [Org Admin permissions and Site Admin permissions](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) for each site that the sensors are located in to enable this feature. To activate the Third-Party VMS Integration functionality on your sensors, you first need to enable the feature for your organization. 1 **In Verkada Command, go to All Products > Admin .** 2 **Select Privacy & Security> Feature Manager.** 3 **Under Air Quality > Third-Party VMS Integration, select Enable from the dropdown.** ### [](https://help.verkada.com/air-quality/configuration-and-setup/third-party-vms-integrations-for-air-quality-sensor-events#set-up-a-third-party-vms-integration) Set up a third-party VMS integration A sensor may only be connected to a single VMS server. Once integrated, the device will appear as **Unavailable** if a different video integration is initiated. Sensor **must be on the same local network and VLAN** as the third-party VMS server. 1 **In Command, go to All Products > Air Quality.** 2 **On the left navigation, click VMS Integration .** 3 **Select a Video Management System.** a. Click **Submit a suggestion** to send a suggestion to our product team. b. In the top right, click **\+ Add Integration** select another supported VMS ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-a5527b163c47c8f4188df12382c78bc68eb3d3d5%252F78cdc1a1b23c77dec60d0410f23da53185a383a6.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=6f8e77b8&sv=2) 4 **Each VMS integration will be slightly different\*\*,\*\* but you will need to enter the following:** a. Server **IP Address**: The IP address of your VMS server. b. Server **Port** Number: The port on your VMS server which will be able to receive events. c. (If applicable) **Username**: A configured username that is capable of receiving alerts into the system. d. (If applicable) **Password**: Password for the configured user above. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-3e07d27e46e0b6a4e4f51acb22ea301fc37b2e4a%252Fda75ba5b863422246a2242892df463009d37aea5.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=fcd7cf5&sv=2) 5 **Select the sensors you would like to connect and click Integrate.** 6 **The devices will begin to receive the configuration and attempt to establish a connection to the VMS server. This may take a few minutes to complete.** * * * ### [](https://help.verkada.com/air-quality/configuration-and-setup/third-party-vms-integrations-for-air-quality-sensor-events#status-indicators-on-command) Status indicators on Command * Green: Successfully connected or submitted an event. * Orange: The device may be offline or has **not yet** submitted a status to the backend. * Red: Failed to connect or failed to submit an event to the VMS server. The **Refresh** button checks if any of the devices have submitted any events or attempted connections to the server. It does not force the device to connect to the server. * * * [](https://help.verkada.com/air-quality/configuration-and-setup/third-party-vms-integrations-for-air-quality-sensor-events#mange-third-party-vms-integration) Mange Third-Party VMS Integration ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ### [](https://help.verkada.com/air-quality/configuration-and-setup/third-party-vms-integrations-for-air-quality-sensor-events#edit-integration) Edit integration 1 **In Command, go to All Products > Air Quality.** 2 **On the left navigation, click VMS Integration .** 3 **You will see a list of existing integrations** 4 **Next to the integration you want to edit click > Edit Integration.** a. Modify the configuration as needed. b. Click **Edit Devices.** c. Click **Save Changes.** ### [](https://help.verkada.com/air-quality/configuration-and-setup/third-party-vms-integrations-for-air-quality-sensor-events#delete-integration) Delete integration 1 **In Command, go to All Products > Air Quality.** 2 **On the left navigation, click VMS Integration .** 3 **Next to the integration you want to delete click > Delete Intergration.** a. Enter the confirmation code. b. Click **Delete.** * * * [](https://help.verkada.com/air-quality/configuration-and-setup/third-party-vms-integrations-for-air-quality-sensor-events#what-needs-to-be-done-on-the-vms-server-side) What needs to be done on the VMS Server Side? --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- The process differs between each VMS. Refer to their documentation for precise instructions. In general, the following steps must be completed: * Create generic or user defined events for each device & reading. * Create alarms for the events. * Create rules to set up custom actions such as trigger camera recording or notifications. * Create mappings between these different elements: * Event → Alarms → Rules → 3rd Party Camera Association You may need to repeat these steps for each device. Last updated 22 hours ago Was this helpful? --- # Air Quality Sensor Zones | Air Quality | Verkada Help Verkada [sensor zones](https://www.verkada.com/blog/adding-more-control-to-environmental-monitoring-with-audio-alert-and-device/) allow you to treat a collection of sensors as a single group or a virtual sensor. Sensor zones are designed to ensure that a single trigger source (for example, a student vaping) does not create duplicate alerts across multiple devices within the same area. Alerts from zones are similar to alerts from individual sensors, except they also include the zone name in the alert, followed by the name of the first sensor to trigger the alert. To use a zone effectively, you should have at least 2 devices selected. If you’re looking to set up alerts on a per-device level, we recommend using the [device-level alerts](https://help.verkada.com/air-quality/events-and-alerts/configure-air-quality-event-alerts) instead of zone functionality. An ongoing alert prevents the dispatch of additional alerts from any other devices in the zone for that specific sensor reading until the zone event has been resolved for at least 10 minutes. [](https://help.verkada.com/air-quality/events-and-alerts/air-quality-sensor-zones#before-you-begin) Before you begin -------------------------------------------------------------------------------------------------------------------------- We recommend reviewing these guidelines before you create a sensor zone: * All sensors in the zone must be in the same site or the same subsite. * You can have as many zones per site as you want, with any number of sensors. * Zones are treated differently than subsites. * Sensors do not have to be at the same physical location; however, a sensor can only be a part of one zone. We recommend that sensors in a zone be in the same room or space. [](https://help.verkada.com/air-quality/events-and-alerts/air-quality-sensor-zones#sensor-zones) Sensor zones ------------------------------------------------------------------------------------------------------------------ ### [](https://help.verkada.com/air-quality/events-and-alerts/air-quality-sensor-zones#create-a-zone) Create a zone Once you create a zone you will see the sensors appear in a box with the zone label at the top left. Sensors not in a zone appear as normal. 1 **In Verkada Command, go to All Products > Air Quality.** 2 **On the right, click Sensor Zone (above any site or subsite) to start your configuration.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-abfc892757350bd2a4ba468ab95c8a58db636693%252Fd31b7906e46327e3588097923d0897157f6dd865.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=b536afdd&sv=2) 3 **On Create Sensors Zone:** a. Give the zone a unique **Name**. b. Add devices from your site into that zone. You can only group devices from the same site into a zone. c. Click **Apply** to create the zone. ### [](https://help.verkada.com/air-quality/events-and-alerts/air-quality-sensor-zones#edit-a-zone) Edit a zone You can still configure sensor event triggers at the device level. If you change a sensor trigger on the device level it will override what was configured for the zone. When you go to edit the zone, you will see **Mixed** for that trigger value. 1 **In Verkada Command, go to All Products > Air Quality.** 2 **Find a zone under the Summary section.** 3 **At the top right of the zone click Edit to edit the following options:** a. Zone name. b. Selected sensors. c. Notifications. d. Delete the zone. ### [](https://help.verkada.com/air-quality/events-and-alerts/air-quality-sensor-zones#mute-sensor-zone) Mute sensor zone 1 **In Verkada Command, go to All Products > Air Quality.** 2 **Find a zone under the Summary section.** 3 **At the top right of the zone click Edit.** 4 **Scroll down to Notifications and click next to the alert you want to mute.** 5 **Click Mute Alert:** a. Choose the duration for the alert to mute: **1 day, 1 week, Always, or Custom.** b. If you choose **Custom**, set the duration, and click **Mute**. ### [](https://help.verkada.com/air-quality/events-and-alerts/air-quality-sensor-zones#delete-sensor-zone) Delete sensor zone 1 **In Verkada Command, go to All Products > Air Quality.** 2 **Find a zone under the Summary section.** 3 **At the top right of the zone click Edit.** 4 **Scroll down to Notifications and click next to the alert you want to delete.** 5 **Click Delete Alert then Yes to confirm.** [](https://help.verkada.com/air-quality/events-and-alerts/air-quality-sensor-zones#sensor-zone-alerts) Sensor zone alerts ------------------------------------------------------------------------------------------------------------------------------ ### [](https://help.verkada.com/air-quality/events-and-alerts/air-quality-sensor-zones#create-zone-alerts) Create zone alerts 1 **In Verkada Command, go to All Products > Air Quality.** 2 **Find a zone under the Summary section.** 3 **At the top right of the zone click Edit.** 4 **Scroll down to Notifications and click Create Alert.** 5 **Continue with configuration on the Create Alert modal. See** [**Sensor Alerts and Events > Create Alert**](https://help.verkada.com/air-quality/events-and-alerts/configure-air-quality-event-alerts) **.** ### [](https://help.verkada.com/air-quality/events-and-alerts/air-quality-sensor-zones#view-zone-alerts) View zone alerts 1 **In Verkada Command, go to All Products > Air Quality.** 2 **Find a zone under the Summary section.** 3 **At the top right, click Zone Alerts.** 4 **You are automatically redirected to the Alerts page with alerts filtered to your selected zone.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-62c5f4850042eeee5b7deb5333b36f7a090f4f5f%252F81e161107dbb1bd247d82c8437646103f14d0b05.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=b1add26e&sv=2) ### [](https://help.verkada.com/air-quality/events-and-alerts/air-quality-sensor-zones#edit-sensor-zone-alerts) Edit sensor zone alerts 1 **In Verkada Command, go to All Products > Air Quality.** 2 **Find a zone under the Summary section.** 3 **At the top right of the zone click Edit.** 4 **Scroll down to Notifications and click next to the alert you want to edit.** 5 **Click Edit Alert:** * Continue with configuration on the **Create Alert** modal. See [Sensor Alerts and Events > Create Alert](https://help.verkada.com/air-quality/events-and-alerts/configure-air-quality-event-alerts) . Last updated 18 hours ago Was this helpful? --- # Detect and Understand Carbon Monoxide | Air Quality | Verkada Help ⚠️ If your live reading is currently over 200 ppm, **contact emergency services immediately**. **The SV25 Is not a life safety device**, and does not satisfy the requirements to be used as an emergency carbon monoxide detector. **Do not rely solely on Verkada alerts.** These alerts do not provide a sufficient timely warning and the threat to health and safety carbon monoxide (CO) may be compromised. [](https://help.verkada.com/air-quality/sensor-data/detect-and-understand-carbon-monoxide#common-facts-about-carbon-monoxide) Common facts about carbon monoxide --------------------------------------------------------------------------------------------------------------------------------------------------------------------- ### [](https://help.verkada.com/air-quality/sensor-data/detect-and-understand-carbon-monoxide#what-is-it) What is it? An odorless, colorless, and toxic gas. Example sources: Automobile exhaust, gas stoves, leaking chimneys, water heaters, and furnaces. Measurement range: 0—1,000 ppm ### [](https://help.verkada.com/air-quality/sensor-data/detect-and-understand-carbon-monoxide#effects) Effects CO inhibits your blood from carrying oxygen even after getting to fresh air. ### [](https://help.verkada.com/air-quality/sensor-data/detect-and-understand-carbon-monoxide#exposure) Exposure CO is primarily a health risk when brief peak exposure is routine or levels in a space continue to rise or do not dissipate. * Because it’s impossible to see, taste, or smell toxic fumes, CO can be deadly and the presence in a building can be unknown. * Detection of singular large spikes do not always indicate a persistent problem or danger. * The effects of CO exposure can vary greatly from person to person depending on age, overall health, and the concentration and length of exposure. [](https://help.verkada.com/air-quality/sensor-data/detect-and-understand-carbon-monoxide#understand-an-event) Understand an event --------------------------------------------------------------------------------------------------------------------------------------- ### [](https://help.verkada.com/air-quality/sensor-data/detect-and-understand-carbon-monoxide#example-1) Example 1 **Scenario**: A diesel truck idling near an open window may look like this: ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-8bbc4c8740121aeebe12c0b95001cca90dcca1c1%252F14ce29b68888db8ddd5aa008c362a2cb85a69dfd.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=b803f3a&sv=2) This would equate to about 35 ppm over 5 minutes. If no other events occur, the occupants of that room would have been exposed to: * 2.917 ppm/hour * 0.365 ppm/8 hours In this case, the occupants might have been exposed to a peak event, but the total exposure concentration is still very low and of no need for concern. A typical meter will enter an alarm state when exposed to 15–50 ppm over an hour or a sum of 50 ppm over 8 hours. ### [](https://help.verkada.com/air-quality/sensor-data/detect-and-understand-carbon-monoxide#example-2) Example 2 With the same example, assume that this diesel truck will make 20 stops a day. At this same spot, that would be: * 7.2925 ppm/hour * 58.34 ppm/8 hours This level indicates actionable concerns, such as making an idle engine policy or closing the window. However, this would not necessarily be an emergency as there is no threat to well-being. If you begin to see events like this regularly and you cannot identify the source, you may want investigate more. ⚠️ If your fire alarm system enters an alarm state due to the presence of CO, always treat it like an emergency, even if the SV25 does not detect it. ### [](https://help.verkada.com/air-quality/sensor-data/detect-and-understand-carbon-monoxide#example-3) Example 3 This graph is also over the same interval of time; however, the circumstances were life-threatening conditions. Lucky for the occupants, the SV25 was mounted directly next to a certified, life safety carbon monoxide meter. **The SV25 is not a certified life-safety carbon monoxide meter.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-f65faa4e0a21ed155ad6f9dc99ab3c347a0ffca7%252Fdb149645a080bc561d63f7fe2b818121e0d72fe9.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=c33e0427&sv=2) Just like the first circumstance, the values began with a spike, however ,the level persisted to rise. The building’s fire alarm went off and the occupants were evacuated. This represents a life-threatening event. If the occupants had not evacuated, they would have been exposed to **400–500 ppm/hour**. In this case, the SV25 was able to provide insights to the fire department to identify a failed water heater. ⚠️ If the SV25 sensor’s live reading shows unsafe values of carbon monoxide that are increasing or are not dissipating, evacuate the area immediately and contact emergency services. Last updated 19 hours ago Was this helpful? --- # Air Quality Sensor Power Requirements | Air Quality | Verkada Help Verkada [Environmental Sensors](https://docs.verkada.com/docs/sensors-quick-start-guide.pdf) use industry-standard 802.3af (Power over Ethernet \[PoE\]). The average bandwidth consumption is less than 5 kbps. Verkada [Air Quality Sensors](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) may consume additional power when performing operations, such as firmware upgrades or initial calibration. The table reflects the maximum power draw for a particular sensor model within the normal temperature. We recommended to provide an additional power budget on your switch for the sum of all of your sensors. **Model** **Normal Operation (802.3af)** [SV11](https://www.verkada.com/sensors/sv11/) 4W [SV21](http://sv21/) 3W [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) 3W [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) 3W Last updated 17 hours ago Was this helpful? --- # Configure Static IP Addresses for Air Quality Sensors (SV20 Series Only) | Air Quality | Verkada Help Verkada Air Quality Sensors provide the option to configure/assign a static IP to ensure that your air quality sensor devices maintain consistent network communication without relying on dynamic IP allocation protocols, such as the Dynamic Host Configuration Protocol (DHCP). #### [](https://help.verkada.com/air-quality/configuration-and-setup/configure-static-ip-addresses-for-air-quality-sensors-sv20-series-only#only-the-sv20-series-models-support-static-ip) **Only the SV20 series models support Static IP:** * SV21 * SV23 * SV25 * SV25-128 _The SV11 does_ _**NOT**_ _support static IP._ Verkada devices support private IP addresses, as defined in [RFC 1918](https://datatracker.ietf.org/doc/rfc1918/) . This means that only private IP ranges specified in the RFC, such as 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16, are compatible with the static IP configuration feature. [](https://help.verkada.com/air-quality/configuration-and-setup/configure-static-ip-addresses-for-air-quality-sensors-sv20-series-only#before-you-begin) Before you begin ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ To configure a static IP address on a sensor device, it must initially connect to Command and update to the latest firmware using DHCP. Once the update process is complete, the device can receive the new static IP configuration. [](https://help.verkada.com/air-quality/configuration-and-setup/configure-static-ip-addresses-for-air-quality-sensors-sv20-series-only#configure-a-static-ip-address) Configure a static IP address -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Only [Site Admins](https://help.verkada.com/verkada-cameras/configuration-and-setup/roles-and-permissions-for-cameras) have the ability to enable this feature or modify static IP configurations. 1 **In Verkada Command, go to All Products > Air Quality .** 2 **Select a sensor to configure.** 3 **In the top right, click Settings.** 4 **Under Device > Device IP, click the dropdown and select Manual.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-9855a35ebcb13265bed798987923e6a1a8e33afb%252F7b66256e6cce7e03371268c7d9d17676fb644fb5.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=737c63e3&sv=2) 5 **Under Manual, enter the static IP addressing information.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-86a26a361c84c39caa1784cb47f3c461b35817c6%252Fb9a30e35c6a48f8b876564da5cda86426492c6be.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=9f0dd9f8&sv=2) 6 **Click Apply to save the configuration. This change is immediately applied to the sensor interface.** ### [](https://help.verkada.com/air-quality/configuration-and-setup/configure-static-ip-addresses-for-air-quality-sensors-sv20-series-only#recovery-mechanisms) Recovery mechanisms Sensors have a recovery mechanism in case of configuration mistakes or network changes. The device performs the following checks at regular intervals to ensure connectivity. If any of these tests fail, the device falls back to the DHCP operation. Recovery Mechanism How to Perform this Task **On the subnet, verify there is no duplicate IP conflict** Send Address Resolution Protocol (ARP) requests for the configured sensor IP. If the sensor receives an ARP request, the reply it considers it as a duplicate IP conflict. **Verify there is a default gateway** Send ARP requests for the configured gateway IP. If no reply is received by the sensor, the gateway is considered unreachable. The device on the network with the configured IP of the gateway. **DNS resolution is operational for Verkada domains** Perform Domain Name Server (DNS) lookups for Verkada domains. In case the device doesn’t receive a response from any of the domains, this test fails. **SSL/TLS sessions can be established with the required endpoints** Send HyperText Transfer Protocol Secure (HTTPS) requests to the Verkada endpoints required for sensor operation. In case the device is unable to perform a Transport Layer Security (TLS) handshake with any of the endpoints, or in case there is any error while performing this handshake, this makes the test fail. ### [](https://help.verkada.com/air-quality/configuration-and-setup/configure-static-ip-addresses-for-air-quality-sensors-sv20-series-only#endpoints-for-dns-tests) Endpoints for DNS tests The following list of endpoints is used for DNS tests, as these are critical for sensor device operation. For a full list of endpoints, see [Air Quality Sensor Network Settings](https://help.verkada.com/air-quality/air-quality-sensor-network-settings) . Copy api.control.verkada.com - TCP/443 relay.control.verkada.com - TCP/443 index.control.verkada.com - TCP/443 firmware.control.verkada.com - TCP/443 update.control.verkada.com - TCP/443 ### [](https://help.verkada.com/air-quality/configuration-and-setup/configure-static-ip-addresses-for-air-quality-sensors-sv20-series-only#endpoint-for-tls-tests) Endpoint for TLS tests For TLS tests, only the **api.control.verkada.com** endpoint is used. If the sensor is unable to establish a TLS connection with this endpoint, it falls back to DHCP operation. ### [](https://help.verkada.com/air-quality/configuration-and-setup/configure-static-ip-addresses-for-air-quality-sensors-sv20-series-only#troubleshoot-workflow) Troubleshoot workflow 1 **If the sensor encounters any issues during these checks, it attempts to fall back to its default DHCP operation and perform the connectivity tests listed above.** 2 **If the DHCP connection fails, the sensor retries using the static IP configuration.** 3 **If the sensor again fails to connect using its static IP configuration, it alternates between static IP and DHCP operations in exponential backoff increments, ranging from 20 seconds up to 1 hour.** ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-c387e70e82b63b92ee5d0ea44c77d38b2d413912%252F92a3759374339ad658e0c5426df55aba53e80f8c.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=19ab232b&sv=2) * If the sensor successfully connects to Verkada Command using DHCP, it continues to operate on DHCP until it is rebooted—via Command or by power cycling the sensor. * Bulk configuration for static IP addressing is not supported for sensor devices. Last updated 1 day ago Was this helpful? --- # Configure Air Quality Event Alerts | Air Quality | Verkada Help You can enable alerts for a variety of air quality events, depending on your configuration needs. For more information about the air quality events types see [below](https://help.verkada.com/air-quality/events-and-alerts/configure-air-quality-event-alerts#h_71912ba2a2) . You must be a Site Admin (for all selected devices) to use the **Readings & Thresholds** feature. Learn more about [Roles and Permissions for Air Quality Sensors](https://help.verkada.com/air-quality/roles-and-permissions-for-air-quality-sensors) . [](https://help.verkada.com/air-quality/events-and-alerts/configure-air-quality-event-alerts#configure-air-quality-event-alerts) Configure air quality event alerts ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ ### [](https://help.verkada.com/air-quality/events-and-alerts/configure-air-quality-event-alerts#create-alert-greater-than-events) Create Alert > Events 1 **Log in to Verkada Command.** 2 **On the Command homepage, left navigation, click Alerts.** 3 **On the Alerts page, next to My Alerts, click .** 4 **On Select Event, select the Air Quality product type.** 5 **Search for or select an event to configure.** 6 **(Optional) Some event types are general and have more specific options once you select them. If prompted, complete any additional configuration steps then click Next.** 7 **Select your devices/sites, based on the alert type you can configure events to be device-specific, site-specific, or all devices.** * When you select **Sites** or **All Devices**, new devices added after alert creation will automatically generate alerts. Click **Done** to continue. 8 **(Optional) Some event types have additional setup steps. If that is the case, click the additional steps and follow the prompts in the configuration window.** 9 **Click Done and continue with the alert** [**recipients**](https://help.verkada.com/air-quality/events-and-alerts/configure-air-quality-event-alerts#h_0580f3aa78) **.** ### [](https://help.verkada.com/air-quality/events-and-alerts/configure-air-quality-event-alerts#create-alert-greater-than-recipients) Create Alert > Recipients 1 **On Recipients, you can search for or select other Command users individually or you can assign the alert to a group.** 2 **Select the dropdown menu next to a user or group to choose their notification method(s). Recipients can be notified either via a push notification, SMS, or email.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-a30e5c666efe865b169b36f277c2ab798ad76c5d%252F3a9609d9912905edd0f35abfff403a95e0b820c8.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=1b1054ea&sv=2) 3 **(Optional) By default, you will be added to the alert created. To remove yourself, select the dropdown menu and click Delete.** 4 **Click Done and continue with the alert** [**notification schedule**](https://help.verkada.com/air-quality/events-and-alerts/configure-air-quality-event-alerts#h_0851c7fd6d) **.** Any recipient added to this alert will see it appear under the **Shared Alerts** section of their **Alerts** page. ### [](https://help.verkada.com/air-quality/events-and-alerts/configure-air-quality-event-alerts#create-alert-greater-than-notification-schedule) Create Alert > Notification Schedule 1 **On Notification Schedule, you must specify what days and times you want alerts to be sent. By default, events are generated 24/7.** ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-b9042c786a9dd12580abefdd20f412fe59cbac5e%252F7b61969c185d482c85ec3b7f15a687d75aee8d13.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=dbcc5532&sv=2) 2 **Click Done and continue with the alert** [**device actions**](https://help.verkada.com/air-quality/events-and-alerts/configure-air-quality-event-alerts#h_acf058e28e) **or** [**finish the alert**](https://help.verkada.com/air-quality/events-and-alerts/configure-air-quality-event-alerts#h_244e665ed1) **.** ### [](https://help.verkada.com/air-quality/events-and-alerts/configure-air-quality-event-alerts#create-alert-greater-than-device-action) Create Alert > Device Action In addition to notifying individuals, you can configure your horn speaker to play when an alert is triggered. These alerts can be text-to-speech or an uploaded MP3 file. 1 **On Device Action, select the horn speaker(s) you want to play your message.** 2 **Select your device’s notification preference (Text to Speech or Audio File).** a. For **Text to Speech,** enter the desired message up to 200 characters. b. For **Audio File,** drag and drop the file or click **choose a file** to upload your audio clip. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-6eebd070cac52d81c895573628cb7b21ba245804%252Fbd7aa4597a411933461874e312ac1e72683f4dab.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=130ab7ed&sv=2) 3 **Click Done and continue with** [**finish the alert**](https://help.verkada.com/air-quality/events-and-alerts/configure-air-quality-event-alerts#h_244e665ed1) **.** ### [](https://help.verkada.com/air-quality/events-and-alerts/configure-air-quality-event-alerts#finish-the-alert) Finish the alert 1 **Click Next on the bottom right of the configuration window once you have configured all the desired alert settings.** 2 **Enter a descriptive name for the alert.** 3 **Click Done and you will start to receive alerts.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-75fcc30636d14fdd34cc9e376db710c1542f4ef2%252F943420792c6bfe40aee47eab735038e52669e4ac.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=f26b2d78&sv=2) ### [](https://help.verkada.com/air-quality/events-and-alerts/configure-air-quality-event-alerts#understand-the-various-air-quality-event-types) Understand the various air quality event types Alert Type Description **Schools** Receive vape alerts for a school. **Schools and Hospitality** Receive vape, noise, and tamper alerts. **Server Rooms, Data Centers, or Refrigeration** Receive temperature and humidity alerts. **Employee Health and Safety** Receive noise, CO2, carbon monoxide, TVOC, Formaldehyde, and PM 2.5 alerts. **Online/Offline** Air quality device changed state to online or offline. **Custom Air Quality Readings** Configure alerts for the different [Air Quality Sensor Readings.](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) Last updated 18 hours ago Was this helpful? --- # Add a Device to Your Command Organization | Verkada Cameras | Verkada Help You need to add your devices to Command before you can access and manage them. You need [Org Admin or Site Admin permissions](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) for a site to add a device. [](https://help.verkada.com/verkada-cameras/configuration-and-setup/add-a-device-to-your-command-organization#add-devices) Add devices ------------------------------------------------------------------------------------------------------------------------------------------- 1 **In Command, go to All Products > Devices.** 2 **At the top right, click Add Devices.** 3 **Enter the serial numbers or order numbers of the devices.** 4 **Click Add Devices. The newly added devices will display on Devices > All Unassigned Devices.** Alternatively, you can add devices using **Scan QR** or **Upload CSV**. If you upload a comma-separated value (CSV) file, you can download a template for ease of use. * * * [](https://help.verkada.com/verkada-cameras/configuration-and-setup/add-a-device-to-your-command-organization#set-up-a-device) Set up a device --------------------------------------------------------------------------------------------------------------------------------------------------- You need to assign a device to a site and complete the setup to move it from the **Unassigned Devices** list. Devices can be set up individually or in bulk. You can only set up one product type at a time. If devices from multiple product lines are selected, you will not see the **Set Up** option. 1 **In Verkada Command, select All Products > Devices.** 2 **Under All Unassigned Devices:** a. Select the device(s) you want to set up. b. Click **Set Up**. 3 **Under General:** a. Enter a unique name. b. Select a site. c. Enter a location. 4 **(For cameras only) Under Settings:** a. (Optional) From the **Default** dropdown, select **Copy from another camera** and select a camera to copy its configuration. b. Confirm the configuration or make any necessary changes. 5 **Click Apply to configure the devices.** You can only copy configurations from cameras located in the same site as the new camera. * * * **Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=qcrS5i8_XR4) . Last updated 1 day ago Was this helpful? --- # Manage Your Sensor Dashboard | Air Quality | Verkada Help Verkada’s [Air Quality Sensors](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) dashboards enable you to easily, view, analyze, and display sensor data across all of your sensors within your environments on a smart display or status screen. You can easily access these dashboards from an external device through the air quality dashboard live links. You can also share and pair dashboards to any browser compatible device. With the use of different tiles, you can add multiple view types to pages within your dashboard and automatically cycle through them within Verkada Command or with a monitor. The hierarchy for sensor dashboards is **dashboards** > **pages** > **tiles**. You can have multiple dashboards in your organization, each of which can contain multiple pages and each page can contain multiple tiles. * * * [](https://help.verkada.com/air-quality/sensor-data/manage-your-sensor-dashboard#set-up-your-sensor-dashboard) Set up your sensor dashboard ------------------------------------------------------------------------------------------------------------------------------------------------ 1 **In Verkada Command, go to All Products > Air Quality.** 2 **On the left panel, click Dashboards and at the top right, click Add Dashboard.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-e0600a4a61e955178292b9ca2cb81a60a96b33d1%252Fc7d430cacf504a385eaf98b697668f87c64c50e3.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=ffef7183&sv=2) 3 **On Create your dashboard, give your dashboard a unique name to easily manage this dashboard later.** 4 **You can then start customizing your dashboard with various settings described below.** ### [](https://help.verkada.com/air-quality/sensor-data/manage-your-sensor-dashboard#add-sensor-tiles) Add sensor tiles 1 **On your newly named dashboard, click Add Sensor Tiles.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-659f3201aabaa1de46cce175e87745053eee2555%252Fe273d6f02271517fed2cca62e02d4b109c63c9c1.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=c57fbb65&sv=2) 2 **On the Tiles slide-out page, select and add tiles. You can add up to 6 tiles per page, including these options, where you can view:** * **Time-Series Line Graph**—Live and 24 hours of historical data for a single sensor reading * **Sensor Readings**—Multiple, live numeric values from a single sensor device * **Metric**—Single aggregated metric across sensor devices * **Gauge**—Color value relative to customizable thresholds * **List**—Table of aggregated metrics across sensor devices 3 **Give your tile a unique name.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-035160050746d6bbd675d55e34e7e71ebd576785%252F51d4a108ff450ef64e509a5161e73e6b1c7e77ce.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=56010164&sv=2) ### [](https://help.verkada.com/air-quality/sensor-data/manage-your-sensor-dashboard#choose-the-layout-for-your-tiles) Choose the layout for your tiles 1 **(Optional) Add more tiles to your dashboard, or click Layout to choose the best layout for your tiles, and click Done.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-2b5e78583d467894f337380a2b8f9a85a5eb58b1%252F90492a5e0ce0afb51f81389ef4085c410359aea3.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=b581d862&sv=2) **Example of a selected layout** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-e6063b30db16ed7c13294d0757081527e95cba71%252F9b9c074bd6acc6eb94049a1a964222588e682890.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=11da8212&sv=2) 2 **Rearrange the tiles (drag and drop), as needed.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-357a5568c649b9ac17d4a037054969dc042ae183%252Fddb024c305c59d75a22d4098a681672d56449a42.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=6f5d430&sv=2) 3 **(Optional) Delete a tile: Hover over the tile and click Delete Tile.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-4bdaa2aa7a5882c3f07f2a7007148ae3609acadb%252F383f7edf6b8ddaf6b07802aa16dbae2fa3f114f1.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=c6058647&sv=2) ### [](https://help.verkada.com/air-quality/sensor-data/manage-your-sensor-dashboard#set-up-your-page) Set up your page 1 **Give the page a unique name.** 2 **At the bottom right, click Show this page for 15 seconds to adjust how long you want the page to display when viewing in full-screen mode. Choose from 10s, 15s, 30s, 1m, and 5m intervals.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-c7bf5eea795b98a68c4c3e0c5624609260b54880%252Fec33ffe52a428aa123186dc7bd26027be1e1ac26.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=7879de4a&sv=2) 3 **On the left panel, click the plus (+) icon to add more pages to your dashboard. You can have up to 10 pages. Repeat the steps from above to set up additional pages.** ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-8426b8c6fe1f19c5455f789f9c67b39e3d74fd6e%252F77adfe87c2f0b15d9d02750ef9ac345b14bfda27.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=48ef720a&sv=2) ### [](https://help.verkada.com/air-quality/sensor-data/manage-your-sensor-dashboard#rearrange-or-remove-pages) Rearrange or remove pages 1 **Next to the page name, click Delete to remove pages.** 2 **Once you’ve finished setting up your pages, click Done.** ### [](https://help.verkada.com/air-quality/sensor-data/manage-your-sensor-dashboard#customize-data-settings) Customize data settings 1 **Select the sensor(s) to monitor (you can filter by site name or by the sensors name).** ​**Note**: Some tiles allow you to select multiple sensors and some only allow you to select one. ​ 2 **Once selected, at the top left, click Customize Data.** 3 **Choose which** [**sensor readings**](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) **to display and adjust the thresholds, as needed (select-drag the numbers around).** a. For **Temperature**, click **°F** and choose **Fahrenheit** or **Celsius**. b. Customize your settings, as needed, and click **Done**. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-5a4b5fa9e7cd1a1df7da9eb4cf938cf57d28f71a%252F51cd99ad58228501bcc1323283b5527b7e9349c3.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=8c4563df&sv=2) [](https://help.verkada.com/air-quality/sensor-data/manage-your-sensor-dashboard#view-a-sensor-dashboard) View a sensor dashboard -------------------------------------------------------------------------------------------------------------------------------------- **Note**: You must have already set up a dashboard to view one. 1 **In Verkada Command, go to All Products > Air Quality.** 2 **On the left panel, click Dashboards and at the top right, click Add Dashboard.** 3 **Select a dashboard to view.** 4 **On your selected dashboard, at the top right, click View.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-7945570c6fefce542c7966d84079f127aea49407%252F31765ee8be2949075d742d05e5380957e87105c9.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=470bf709&sv=2) 5 **You should see the window in full screen mode and then to the sensor dashboard view mode, where you have the option to view:** * Dashboard and page names (at the top left). * Time and timezone (at the top right). **Note**: The data displayed updates every one (1) minute. This is a default setting and cannot be changed. Pages rotate based on the preset time you configured in the setup flow. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-d1a317b707e6770584ce3084e6c7a949b6dbf371%252F6ed9c04738931bce0ce7d7fc3f02299f271b778a.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=95e69c0&sv=2) 6 **At the top right, click X to exit or press the esc key on your keyboard.** [](https://help.verkada.com/air-quality/sensor-data/manage-your-sensor-dashboard#share-a-dashboard) Share a dashboard -------------------------------------------------------------------------------------------------------------------------- Dashboard sharing utilizes the same robust and secure system implemented in camera live links. 1 **In Verkada Command, go to All Products > Air Quality.** 2 **On the left panel, click Dashboards and (optionally) at the top right, click Add Dashboard.** 3 **Once you have created a new dashboard or selected one from the dropdown, at the top right, click Share.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-75271b8192b23f3651af55344e0003f847363db8%252F05095847c2c7a6d07e3095bcd1a7d087b1d51a49.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=d166167c&sv=2) 4 **You should see the option to create a new dashboard link for a set duration of time. The longest permitted expiration (at this time) is 52 weeks. When you’re ready, click Create to have your link’s management bubble populate below. Other options that you can do:** * Rename a link and see the time till expiration. * Click **Copy Link** to copy the link to your clipboard. * Click **Send Link** to share the code via email, SMS, or by contact. * Click **Pair TV** to pair the link to a smart display. ### [](https://help.verkada.com/air-quality/sensor-data/manage-your-sensor-dashboard#manage-shared-links) Manage shared links You can manage shared links, [just like cameras](https://help.verkada.com/verkada-cameras/sharing-video/share-a-cameras-live-stream) , as follows: 1 **in Verkada Command, go to All Products > Admin.** 2 **Under Org Settings, scroll to Manage Shared Links.** Alternatively, for quick access within the dashboard, go to **Manage Shared Links** > **Share** to redirect you to this page. [](https://help.verkada.com/air-quality/sensor-data/manage-your-sensor-dashboard#pair-a-dashboard) Pair a dashboard ------------------------------------------------------------------------------------------------------------------------ Dashboard pairing allows for the rapid deployment of Air Quality dashboards on smart TVs and displays that otherwise would be difficult to send a link to or type on with a keyboard. Pairing works by sharing a **Live Link** based on a successful synchronization, as described above. **Note:** Pairing a dashboard is currently only supported in US-based organizations. **Recommendation**. Anyone with access to the link (within the address bar of the dashboard) can open the dashboard on a different device. Ensure that the URL is hidden, by default, within your smart device, or hidden on full screen should this be a security concern to you. 1 **You can pair a dashboard using one of these options:** * At the top right of the dashboard, click **Pair**. * Within an already created live link, click **Pair**. 2 **If not already specified (as noted above in** [**Share a dashboard**](https://help.verkada.com/air-quality/sensor-data/manage-your-sensor-dashboard#h_a4a6a289a7) **), you should see the option to create a new dashboard link for a set duration of time. The longest permitted expiration at this time is 52 weeks.** 3 **On your smart display navigate to vkda.co/pair.** 4 **You should see a 5-character code generated on the screen. You must enter the code into the pairing prompt in Command before it expires.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-529a500da5aa5ed3730d9b103d7621aabc61281c%252Fbc7969ba153c8409337deecd59365f83a04f161d.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=dbb6ec9e&sv=2) 5 **When you’ve entered the code, click Pair. Your display should then redirect you to your Air Quality dashboard link.** ### [](https://help.verkada.com/air-quality/sensor-data/manage-your-sensor-dashboard#manage-your-dashboard-link) Manage your dashboard link 1 **In Verkada Command, go to All Products > Air Quality.** 2 **On the left panel, click Dashboards and at the top right, click Add Dashboard.** 3 **Once you have created a new dashboard or selected one from the dropdown, at the top right, click Share to see the corresponding live link that was created.** Alternatively, you can manage the link using this method: 1 **In Verkada Command, go to All Products > Admin.** 2 **Under Org Settings, scroll down to Manage Shared Links to see the corresponding live link that was created.** [](https://help.verkada.com/air-quality/sensor-data/manage-your-sensor-dashboard#delete-a-sensor-dashboard) Delete a sensor dashboard ------------------------------------------------------------------------------------------------------------------------------------------ 1 **In Verkada Command, go to All Products > Air Quality.** 2 **On the left panel, click Dashboards .** 3 **Under Actions, click Delete.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-5ba1339a7c076227672f2b306a4e9445f2341ed3%252F94537cb628e838e75d862de43850d06bf7f9657c.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=99e2e517&sv=2) 4 **On Delete Dashboard, click Delete again to confirm. This cannot be undone.** [](https://help.verkada.com/air-quality/sensor-data/manage-your-sensor-dashboard#faqs) FAQs ------------------------------------------------------------------------------------------------ Who can create, edit and remove a dashboard?[](https://help.verkada.com/air-quality/sensor-data/manage-your-sensor-dashboard#who-can-create-edit-and-remove-a-dashboard) [Org Admins](https://help.verkada.com/air-quality/roles-and-permissions-for-air-quality-sensors) can create, edit, and remove dashboards. They must also be a [Site Admin](https://help.verkada.com/air-quality/roles-and-permissions-for-air-quality-sensors) for the sites where the sensors are located. If you don’t have Site Admin permissions, you can’t view the tiles created in the dashboard. Learn more about the [Roles and Permissions for Air Quality Sensors](https://help.verkada.com/air-quality/roles-and-permissions-for-air-quality-sensors) . Who can view a dashboard?[](https://help.verkada.com/air-quality/sensor-data/manage-your-sensor-dashboard#who-can-view-a-dashboard) A [Site Viewer](https://help.verkada.com/air-quality/roles-and-permissions-for-air-quality-sensors) can view dashboards; however, they can only see the sensors in their site(s). If they don’t have permission to view a sensor in the dashboard, the value is be empty. You can also share and pair dashboards with live links just like cameras. See [Manage shared links](https://help.verkada.com/air-quality/sensor-data/manage-your-sensor-dashboard) (above). **Note**: Verkada supports multiple dashboards per organization. Dashboards are created per organization, not per user. How often does the dashboard data update or refresh?[](https://help.verkada.com/air-quality/sensor-data/manage-your-sensor-dashboard#how-often-does-the-dashboard-data-update-or-refresh) The data that is displayed on the dashboard updates every one (1) minute. This is a default setting and cannot be changed. Can I share my dashboard publicly?[](https://help.verkada.com/air-quality/sensor-data/manage-your-sensor-dashboard#can-i-share-my-dashboard-publicly) Yes! You can now share dashboard with live links just like cameras. See [Manage shared links](https://help.verkada.com/air-quality/sensor-data/manage-your-sensor-dashboard) (above). How do I display the dashboard on a larger screen?[](https://help.verkada.com/air-quality/sensor-data/manage-your-sensor-dashboard#how-do-i-display-the-dashboard-on-a-larger-screen) To display the dashboard on a larger screen (TV or monitor), there must be a computer connected to the display, and that computer must be logged in to Verkada Command. From there, you can navigate to the dashboard and click **Live**, which will display the live view on the connected display. Do the sensor tiles integrate with a Verkada Viewing Station or camera grid?[](https://help.verkada.com/air-quality/sensor-data/manage-your-sensor-dashboard#do-the-sensor-tiles-integrate-with-a-verkada-viewing-station-or-camera-grid) No, at this time, the sensor tiles and dashboard are standalone. Can I add cameras to my sensor dashboards?[](https://help.verkada.com/air-quality/sensor-data/manage-your-sensor-dashboard#can-i-add-cameras-to-my-sensor-dashboards) Currently, you can only add sensor information to sensor dashboards. Last updated 1 day ago Was this helpful? --- # Best Practices for Vape Detection | Air Quality | Verkada Help With a collection of up to 15 embedded sensors, [Verkada air quality sensors](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) simultaneously measure air quality, temperature, humidity, motion, noise, and more. School leaders can configure the device to display which sensor data they want to monitor, and set custom alerts for when certain thresholds are exceeded. Users can then receive alert notifications in real–time, allowing for fast and proactive responses. [](https://help.verkada.com/air-quality/sensor-data/best-practices-for-vape-detection#how-it-works) How it works --------------------------------------------------------------------------------------------------------------------- As vaping occurs, users can see spikes in Verkada’s Vape Index, which measures against a range of different onboard sensors to identify the likelihood of vaping or smoking occurring on a scale of 1 to 100. Administrators can set custom thresholds and time delayed thresholds to receive real-time alerts via SMS and email (or webhooks via our API). When detected, an alert can also be sent to pre-selected faculty members and on-campus security, allowing teams to respond quickly. ### [](https://help.verkada.com/air-quality/sensor-data/best-practices-for-vape-detection#vape-detection-algorithm) Vape detection algorithm The new, improved vape detection algorithm displays values in a more binary fashion, with a higher confidence level when making a decision about whether an event is a true positive, if thresholds for certain indices are successfully met. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-6aaaea80f08f96eacd81c2c5d0308f6ff5d4063a%252F3e55f5d746e81c79fda5c5402592cf54f0b97b8e.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=a955b14f&sv=2) ### [](https://help.verkada.com/air-quality/sensor-data/best-practices-for-vape-detection#custom-threshold-values) Custom threshold values Changes in the event detection and analysis phases now account for how the triggers are set for custom thresholds values, which includes the time the sensor needs to make an accurate prediction to flag an event as a positive vape event. * A _higher sensitivity_ generates a higher volume of events as the analysis time needed to create an event is lower. * A _lower sensitivity_ causes the sensor to gather environmental data for a longer duration to make a more accurate prediction (low being the default). ### [](https://help.verkada.com/air-quality/sensor-data/best-practices-for-vape-detection#custom-triggers) Custom triggers When you set a custom trigger now, it now allows you to choose the values at which the sensor now creates an alert. By default, the trigger is set to 50. For most deployments, this should be a good starting point. If you notice that you get alerts for false positives at around 50, then consider adjusting the trigger; for example, if you’re getting false positives at around 60, and true positives at around 70. In this case, we recommend to adjust the trigger to be at around 70. ### [](https://help.verkada.com/air-quality/sensor-data/best-practices-for-vape-detection#sensor-data) Sensor data All sensor data is accessible from the Verkada Command platform and is set against a timeline to give administrators a complete view of when these events took place. Additionally, administrators can pair a Verkada camera with any sensor, providing a layer of visual evidence to see exactly what happened. For locations, such as bathrooms, cameras can be placed outside these private areas, giving administrators a non-invasive way to monitor these incidents. [](https://help.verkada.com/air-quality/sensor-data/best-practices-for-vape-detection#installation-requirements) Installation requirements ----------------------------------------------------------------------------------------------------------------------------------------------- If installed for vape detection, you should install the air quality sensor on ceilings. Wall mounting is possible, but degrades performance for accurate vape detection and events. **Recommendation**. We recommend installing at 8 ft (2.4m) and a maximum height of 9 ft (2.7m) for best air quality measurements. If air quality is not an intended use case, the device can be mounted at other heights or orientations. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-7e7f891e6a4dd49c33eaf6bfbecc0ae3bb438b36%252F6f7db4ae51ccbcaf11cae95bb13bef267b994984.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=85495c3e&sv=2) ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-36d3e97b0d8d8261ad8c7b6be94de08115b0dce4%252F79b74f0ac2b871f75eef3227bc6ce4f24df8cfdd.jpg%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=e06a2b14&sv=2) ### [](https://help.verkada.com/air-quality/sensor-data/best-practices-for-vape-detection#range-of-air-quality-sensors-for-vape-detection) Range of air quality sensors for vape detection When mounted on an 8 ft (2.4m) ceiling, the SV11, SV23, and SV25 can detect vaping events within a 250 sq ft (23 m2) area around the sensor, or a 8 ft (2.4m) radius. Higher ceilings or increased distance from the sensor decreases detection accuracy, as the vape/smoke particles are less likely to reach the sensor in sufficient concentrations. The range for vape detection and other sensors is also dependent on airflow, ventilation, filtration systems, and other variables. In most cases, alert thresholds for all sensors can be adjsuted to meet the unique needs of your environment. [](https://help.verkada.com/air-quality/sensor-data/best-practices-for-vape-detection#considerations) Considerations ------------------------------------------------------------------------------------------------------------------------- * Verkada air quality sensors are not a life safety device, and should not be used as a smoke detector. Learn more about [Detect and Understand Carbon Monoxide](https://help.verkada.com/air-quality/sensor-data/detect-and-understand-carbon-monoxide) . * The SV21 lacks the sensors required to do vape detection and does not support this feature. * The SV11, SV23, and SV25 Vape Index measures air quality events indicative of vaping and smoking, but cannot provide 100% proof of a vaping incident. * School security and administrative teams should use the Vape Index and Verkada camera integration to help with investigations and monitor vaping activity and patterns, but use searches for physical evidence as the basis for further disciplinary/legal actions. * Certain smoke or cooking fumes can be identified as a vape event. In practice, this is rare in typical school environments. * The SV11, SV23, and SV25 will be less able to detect vaping/smoking incidents if a person uses significant efforts to hide the activity, such as exhaling into a closed container, out of a window, and so on. However, the more typical behavior of breathing into a shirt or jacket still results in a detected vape event in our testing. Last updated 18 hours ago Was this helpful? --- # Air Quality Sensor Readings | Air Quality | Verkada Help Verkada [Air Quality Sensors](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) contain a wide variety of sensors that are used to track information about your environment. Verkada creates recommended sensor value ranges based on data from the Environmental Protection Agency ([EPA](https://www.epa.gov/) ), the World Health Organization ([WHO](https://www.who.int/) ), the Occupational Safety and Health Administration ([OSHA](https://www.osha.gov/) ), the American Society of Heating, Refrigeration, and Air-Conditioning Engineers ([ASHRAE](https://www.ashrae.org/) ), and more. [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings#sensor-color-readings) Sensor color readings --------------------------------------------------------------------------------------------------------------------------------- To make things easy to view at a glance, Verkada’s sensor readings are associated with different colors (except Air Quality Index, which follows the [US AQI color scheme](https://www.airnow.gov/aqi/aqi-basics/) ). * **Green**—Values are within an established range of recommended or safe levels. * **Yellow**—Values are slightly outside the range of recommended or safe values. * **Orange**—Values are significantly outside the range of recommended or safe values. * **Red**—Values are dramatically outside the range of recommended or safe values, often requiring immediate attention. * **Purple**—Values detected are potentially fatal. **The area should be evacuated if not resolved immediately**. (This does not apply to Air Quality Index, which follows the [US AQI color scheme](https://www.airnow.gov/aqi/aqi-basics/) .) Verkada SV20 series sensors can be mounted in several different configurations. The specific configuration depends on your installation constraints and which sensor readings you find most meaningful. See the [datasheet](https://docs.verkada.com/docs/sensors-sv21-sv23-sv25-quick-start-guide.pdf) for more information. * * * [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings#event-types) Event types ------------------------------------------------------------------------------------------------------------- For each event type noted below, any measurement outside of the green zone may require attention, if unexpected or outside of the normal range for the sensor location. In the case of [TVOC Index](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings#h_c6ec96d87d) : A VOC index outside of the green zone may require attention, such as increasing ventilation with clean air, if the change is unexpected for this sensor location. ### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings#air-quality-index) Air Quality Index Description Measurement Range Compatible Sensors The U.S. Air Quality Index (AQI) measures total air pollution and provides benchmarks for healthy values. When AQI exceeds 100, air quality is unhealthy: at first for certain sensitive groups of people, then for everyone as AQI values get higher. 0–500 (unbounded) [SV11](https://docs.verkada.com/docs/sensors-overview.pdf) , [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) ### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings#ambient-light) Ambient Light Description Measurement Range Compatible Sensors Ambient light is a measure of how much natural (sunlight, moonlight) and artificial (lamps, interior lighting) light is in a given area. The amount of light an individual is exposed to could cause physical discomfort. Knowing ambient light levels in a space can help point out energy inefficiencies and improve overall energy consumption. The [lux](https://en.wikipedia.org/wiki/Lux) value is a measure of illuminance; the total amount of light that falls on a surface. It is a standardized unit of measurement of light level intensity. However, the lux value varies based on the device’s mount position (wall, ceiling, etc.) and the environment the device is installed in. For example, lux readings on a sensor installed on an office wall will drastically differ from a sensor installed on the office ceiling. Lux can be understood with these reference descriptors; however, light is perceived by people differently. 0 lux—Dark room 25 lux—Candlelight 50 lux—Moonlight 100 lux—Reading light on a plane 300 lux—Dimly lit room 600 lux—Well lit room 1K lux—Brightly lit room 2K lux—Art gallery lighting 5K lux— Need sunglasses to see 0–6,000 lux [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) ### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings#barometric-pressure) Barometric pressure Description Measurement Range Compatible Sensors Barometric pressure is the measurement of air pressure in the atmosphere. Specifically, the measurement of the weight exerted by air molecules at a given point on Earth. Barometric pressure changes constantly and is always different, depending on where the reading takes place, specifically with regard to altitude. For example: At sea level, barometric pressure ranges between 100,000 Pa (29Hg) and 101,325 Pa (31 Hg). In a place like Denver, which is one mile above sea level, barometric pressure ranges between 51,350 Pa (15.16 Hg) and 83,000 Pa (24.5 Hg). On the other hand, the lower the altitude, the higher the barometric pressure. For example, the Dead Sea, the lowest point on Earth, can reach levels of 101,658 Pa (31.45 Hg) 300–1,250 hPa [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) ### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings#carbon-dioxide-c02) Carbon Dioxide (C02) **Recommended**. We recommend to investigate better air quality management for most workplaces when the exposure limits are 5,000 ppm within an 8-hour period. Description Measurement Range Compatible Sensors Carbon dioxide (CO2) is a colorless and odorless gas that’s produced both naturally, like people breathing and through human activities, such as burning gasoline, wood, or oil. Indoor CO2 levels are dependent on factors, such as the number of people present, the amount of time an area has been occupied, the amount of fresh air entering the space, the size of the room, and nearby combustion by-products. **At or under 1,200 ppm**, the CO2 levels are within a healthy range and are typical of spaces with good ventilation and air exchanges. **At over 1,200 ppm**, occupants may start to experience mild drowsiness if exposed for an extended period of time. **At over 2,000 ppm**, occupants may feel sleepiness or nausea. **Readings over 5,000 ppm** indicate that the space is at a hazardous level and should be evacuated/ventilated immediately. 0–6,000 ppm [SV11](https://docs.verkada.com/docs/sensors-overview.pdf) , [SV21](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) ### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings#carbon-monoxide-co) Carbon Monoxide (CO) ⚠️ If the live reading is currently over 200 ppm as you are reading this, contact emergency services immediately. The [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) is not a life safety device and does not satisfy the requirements to be used as an emergency CO detector. Alerts sent from Verkada will not provide a sufficiently timely warning given the threat to health and safety CO may pose and should not be solely relied on. Description Measurement Range Compatible Sensors Carbon monoxide (CO) is an odorless, colorless, and toxic gas. Because it is impossible to see, taste, or smell the toxic fumes, CO can be deadly and the presence in a building can be unknown. The effects of CO exposure can vary greatly from person to person, depending on age, overall health, and the concentration and length of exposure. Examples sources of CO can include automobile exhaust, gas stoves, leaking chimneys, water heaters, and furnaces. CO inhibits your blood from carrying oxygen even after getting to fresh air. The presence of any level of CO may warrant some investigation. **Values over 35 ppm** (with no sign of decline) may indicate an issue that requires evacuation. **Values over 200 ppm** (with no sign of decline) may indicate an emergency or life-threatening situation. Learn more about how to [Detect and Understand Carbon Monoxide](https://help.verkada.com/air-quality/sensor-data/detect-and-understand-carbon-monoxide) . 0–1,000 ppm [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) ### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings#dew-point) Dew Point Description Measurement Range Compatible Sensors The dew point is the temperature to which air must be cooled, at constant pressure, for the air to reach 100% relative humidity, meaning the air becomes saturated with water vapor. If the air cools further, condensation occurs. The dew point provides a more accurate measure of how humid the air feels compared to relative humidity, as a higher dew point indicates more moisture in the air. _Derived from Temperature & Humidity Readings._ 23 °F to 122 °F (-5 °C to 50 °C) [SV11](https://docs.verkada.com/docs/sensors-overview.pdf) , [SV21](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) ### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings#formaldehyde-ch2o) Formaldehyde (CH2O) Description Measurement Range Compatible Sensors Formaldehyde is a colorless, flammable gas at room temperature, and has an extremely strong odor. Long-term exposure and high concentrated exposure (over 1,000 ppb) to formaldehyde may cause adverse health effects. Increased formaldehyde levels can be a result of the resins used to manufacture composite wood products, building materials, insulation, household products such as flues, paints, lacquers, smoking tobacco, fertilizers, and pesticides. If in the presence of high concentrations, get to fresh air. 0–5,000 ppb Unlike most other sensors that are measured in ppm, CH2O is measured in parts per billion (ppb). [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) ### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings#humidex) Humidex Description Measurement Range Compatible Sensors Humidex measures how hot we feel in hot, humid weather. It is a parameter intended for the general public to express how the combined effects of warm temperatures and humidity are perceived. It provides a number that describes how hot people feel. Color-coded relative Humidex ranges are aligned to healthy indoor air guidelines set by the government and industry standards. _Derived from Temperature & Humidity Readings_ Range: 0–50 Recommended: 0–15 [SV11](https://docs.verkada.com/docs/sensors-overview.pdf) , [SV21](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) ### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings#humidity) Humidity Description Measurement Range Compatible Sensors The relative humidity is the amount of moisture in the air compared to what the air can hold at that temperature. Color-coded relative humidity ranges are aligned to healthy indoor air guidelines set by the government and industry standards. Range: 0–100% Recommended: 20–80% [SV11](https://docs.verkada.com/docs/sensors-overview.pdf) , [SV21](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) ### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings#heat-index) Heat Index Description Measurement Range Compatible Sensors The heat index is what the temperature feels like to the human body when relative humidity is combined with the temperature. This is important for understanding human comfort. When the body overheats, it sweats to cool down. Evaporation of sweat helps lower body temperature since it’s a cooling process. However, sweat evaporates more slowly when high humidity makes it feel warmer because the body struggles to cool itself. In contrast, sweat evaporates more quickly when humidity is low, so the body feels cooler in dry conditions. The heat index increases as air temperature and humidity rise and decreases as they drop. _Derived from Temperature & Humidity Readings._ 23 °F to 160 °F (-5 °C to 71 °C) [SV11](https://docs.verkada.com/docs/sensors-overview.pdf) , [SV21](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) ### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings#mold-risk-index) Mold Risk Index Description Measurement Range Compatible Sensors The Mold Risk Index assesses the likelihood of mold growth in confined, unventilated spaces based on temperature and humidity levels. Higher temperatures combined with elevated humidity create ideal conditions for mold spores to thrive, making these factors key indicators of potential mold growth. This index helps to identify when conditions may reach critical levels, allowing for timely interventions to prevent mold development. 0 (Green) – Little to no risk for mold growth. 1 (Yellow) – Warning! Moderate mold risk. Mold will start to grow after 8 or more weeks, especially on vulnerable materials in the current environment. 2 (Orange) – Danger! High mold risk. Mold will start to grow in 4 to 8 weeks on all kinds of materials. 3 (Red) – Red Alert! Extreme and imminent mold risk. Mold will start to grow in less than 4 weeks. _Derived from Temperature & Humidity Readings._ 0–3 Index [SV11](https://docs.verkada.com/docs/sensors-overview.pdf) , [SV21](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) ### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings#motion) Motion Description Measurement Range Compatible Sensors A measure of changes in infrared light absorption caused by the motion of warm bodies, as measured by a passive infrared sensor. Powered by the same technology as motion sensors for intrusion detection, a "Yes" motion event indicates human/animal motion or other large changes in heat or infrared activity. Binary - motion detected as "Yes" or "No" [SV11](https://docs.verkada.com/docs/sensors-overview.pdf) , [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) ### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings#noise-level) Noise Level Description Measurement Range Compatible Sensors A measure of the total noise level at the sensor. Color-coded noise level ranges are aligned to safe noise level guidelines set by OSHA and other government and industry standards. OSHA regulations state that noise levels cannot exceed 90 dB over an 8-hour period or 95 dB over a 4-hour period. 20–120 dB SPL (A-Weighted) [SV11](https://docs.verkada.com/docs/sensors-overview.pdf) , [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) ### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings#pm-2.5-pm-4-pm-10) PM 2.5, PM 4, PM 10 Description Measurement Range Compatible Sensors Particulate Matter (PM) refers to tiny inhalable particles or droplets in the air that are less than 2.5, 4, or 10 microns in width, respectively. These particles can have negative health effects and are caused by dust, vehicle exhaust, burning fuels, cooking, smoking, and vaping. Color-coded PM ranges are aligned to healthy indoor air guidelines set by the government and industry standards. 0–1,000 μg/m3 [SV11](https://docs.verkada.com/docs/sensors-overview.pdf) , [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) ### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings#reset-r-viral-index) RESET® Viral Index Description Measurement Range Compatible Sensors The RESET® Viral Index is designed to assess the likelihood of airborne virus transmission in indoor spaces, using research on virus transmission and applying it to continuous monitoring. It consolidates research and data on factors like virus survivability, impacts on immune system health, and exposure levels to calculate infection potential, providing valuable insights into the outcomes of operational decisions. 0 – 20 (Purple) – Poor. Maximum likelihood of indoor airborne virus transmission. 20 - 40 (Red) – Unsatisfactory. Very high likelihood of indoor airborne virus transmission. 40 – 55 (Orange) – Needs Improvement. High likelihood of indoor airborne virus transmission. 55 – 70 (Yellow) – Fair. Moderate likelihood of indoor airborne virus transmission. 70 – 100 (Green) – Good. Low likelihood of indoor airborne virus transmission. Over >85% is excellent, with little to no indoor airborne virus transmission risk. For more information on the RESET® Viral Index, [**please refer to their resource page**](https://reset.build/resources/indexes/viral) . _Derived from Temperature, Humidity, PM2.5, and CO2 Readings._ 0–100 % Index [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) ### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings#temperature) Temperature Description Measurement Range Compatible Sensors Color-coded temperature ranges are aligned to healthy indoor air temperatures set by the government and industry standards. 23 °F to 122 °F (-5 °C to 50 °C) [SV11](https://docs.verkada.com/docs/sensors-overview.pdf) , [SV21](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) ### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings#tvoc-index) TVOC Index Description Measurement Range Compatible Sensors VOCs are chemicals that evaporate into the air and are emitted by cleaners, paints, varnishes, fragrances, and hundreds of other products. Examples: benzene, ethylene glycol, and formaldehyde. The VOC Index describes the current VOC status in a room relative to the sensor’s recent history. In this way, the VOC Index behaves like a human nose as it can detect relative intensity, duration, and frequency of VOC events. The value "100" refers to the typical indoor gas composition over the past 24 hours. While values between 100 and 500 indicate a deterioration, values between 0 and 100 inform about improvement of the air quality. VOCs are measured as a group because of their cumulative effects, with a high VOC index associated with negative health impacts. Color-coded VOC index ranges are aligned to healthy indoor air guidelines set by government and industry standards. 0–500 Index [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) ### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings#tvoc-ppb) TVOC (ppb) Description Measurement Range Compatible Sensors A Total Measure of Volatile Organic Compounds (TVOC) are chemicals that evaporate into the air and are emitted by cleaners, paints, varnishes, fragrances, and hundreds of other products. Examples: benzene, ethylene glycol, and formaldehyde VOCs are measured as a group because of their cumulative effects, with high TVOC values associated with negative health impacts. Color-coded TVOC ranges are aligned to healthy indoor air guidelines set by the government and industry standards. 0–60,000 ppb [SV11](https://docs.verkada.com/docs/sensors-overview.pdf) ### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings#vape-index) Vape Index Description Measurement Range Compatible Sensors A score derived from multiple sensors is strongly correlated with vaping and/or smoking activity. Vape Index measurements outside of the green zone indicate suspected vaping/smoking activity, but could also reflect smoke or fumes from other sources. In particular, smoke from cooking, burning fuel, wildfires, etc. may register highly on the Vape Index. 0–100 Index [SV11](https://docs.verkada.com/docs/sensors-overview.pdf) , [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) Last updated 17 hours ago Was this helpful? --- # Air Quality Sensor Settings | Air Quality | Verkada Help Verkada’s [Air Quality Sensors](https://www.verkada.com/air-quality/sensors#overview) are all-in-one devices for monitoring environmental changes in your physical space. You can configure the device to display which sensor data you want to monitor, and set custom alerts for when certain thresholds are exceeded. You can also get [alert notifications](https://help.verkada.com/air-quality/events-and-alerts/configure-air-quality-event-alerts) in real-time, allowing for fast and proactive responses. [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-settings#edit-your-air-quality-sensor-settings) Edit your air quality sensor settings ----------------------------------------------------------------------------------------------------------------------------------------------------------------- 1 **In Verkada Command, go to All Products > Air Quality.** 2 **Select the sensor you want to modify.** 3 **At the top right, click Settings.** 4 **On Edit Settings > General, configure the settings, as needed for each category:** [**General**](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-settings#h_0a5d18a6b6) **,** [**Camera**](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-settings#h_c7300020c4) **,** [**Sensors and Triggers**](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-settings#h_1905a9e65c) **,** [**BACnet**](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-settings#h_6c10de28ca) **, and** [**Device**](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-settings#h_4f03494ca1) **.** 5 **Click Apply when you’re satisfied with your selections.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-ffdd35771a7eeb1bc43fd5a5f0755cf117390233%252Fbfbc9bc926bc1d1dc4969459bfb558d86774d57b.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=ee883dd6&sv=2) ### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-settings#general) General Field How to Configure **Name** Create a unique name for the sensor. **Site** Just like Verkada cameras, you can add sensors to a site or subsite to define permissions. To **add an air quality sensor to a site**: 1. Next to **Site**, click **Change**_._ 2. Select your preferred site. 3. Click **Apply**. **Zone** Using [sensor zones](https://help.verkada.com/air-quality/events-and-alerts/air-quality-sensor-zones) , you can group air quality sensors together in zones to treat a collective of devices as one. To **add an air quality sensor to a zone**: 1. Next to **Zone**, click **Change.** 2. Select a zone. 3. Click **Apply**. **Location** To **set the location** of the air quality sensor: 1. Next to **Location**, click **Change**. 2. When you see the map and search bar, enter an address or move the map to set the set location. 3. Click **Apply**. **Thumbnail** You can add a thumbnail to: Help identify your sensor on the **Air Quality** home page. Update the image on the **Air Quality** home page and the device’s page. To **add a thumbnail** to your air quality sensor: Click **Select Thumbnail** where you can upload an image from your desktop. To **remove the thumbnail**, click **Remove Thumbnail**. **Serial Number** Unique identifier for your sensor, used to claim the device to your Command organization. **Sensor Timezone** To **change the timezone** where the sensor data is located, as specified under **Location**. ### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-settings#camera) Camera On **Edit Settings**, select **Camera** to add a context camera to your sensor. This provides visibility into the environment it is monitoring. ### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-settings#sensors-and-triggers) Sensors and triggers Not all air quality sensor versions include all sensor readings. You can only see readings available for your device’s model. #### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-settings#enable-sensor-readings) Enable sensor readings 1 **On Edit Settings, click Sensors and Triggers to configure.** 2 **Check the box next to the sensor reading you want to enable. When a reading is active, it has a black checkmark next to it. Learn more about** [**sensor readings**](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) **.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-b6f6c153fa1444a20bacec4dc1ae44696f042ecc%252F1004a124ec2b35454478fbbb210ed4b56be41003.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=6952d08c&sv=2) #### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-settings#disable-sensor-readings) Disable sensor readings To disable a reading, uncheck the box. The checkmark inside the checkbox disappears. Learn more about [sensor readings](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) . #### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-settings#view-temperature-readings-in-celsius) View temperature readings in Celsius On **Edit Settings** > **Sensors and Triggers**, go to **Temperature**, click the **Unit** dropdown to switch to Celsius. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-eaa5881bf4d051f1ec95957af5fe80092179321b%252Fd25f8811b7ba9aa441364ce5daf1a6c06850fd8a.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=b1c35c8d&sv=2) This setting is **changed for all users** who can view this sensor. #### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-settings#adjust-motion-sensitivity) Adjust motion sensitivity If your sensor is installed near an air conditioning unit (too sensitive) or far from the ground (not sensitive enough), it can impact the performance of the motion sensitivity. If you notice irregular motion events, we recommend to adjust the motion sensitivity to better accommodate the device. On **Edit Settings** > **Sensors and Triggers**, go to **Motion**, click the **Sensitivity** dropdown to select **Low**, **Medium** (default), or **High**. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-bb0a21e4eed4ef143954aecb2aa60add11bb855d%252F51318e6f761320c739e90fd85103b5e343f11b73.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=ff356e3&sv=2) ### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-settings#bacnet) BACnet 1 **On Edit Settings > BACnet.** 2 **Click the dropdown and select Enable or Disable, as needed. When you enable, BACnet/IP support is enabled for this device. Learn more about** [**BACnet for Verkada sensors**](https://help.verkada.com/air-quality/configuration-and-setup/bacnet-for-verkada-air-quality-sensors) **.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-73603e1534062cbd7b722371bb11e9556f045590%252F878e71e5f0cbc843e33e0eee8ea15385de396658.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=1c186d98&sv=2) ### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-settings#device) Device ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-10d5e8d32845d2e05b5b40cc9f6d83286ceb601c%252Fd68f1f913b462b1d7a571300c24f3181769a9d53.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=518f4d0b&sv=2) #### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-settings#device-ip) Device IP Verkada SV20 series ([SV21](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) ) Air Quality Sensors provide the option to [configure/assign a static IP](https://help.verkada.com/air-quality/configuration-and-setup/configure-static-ip-addresses-for-air-quality-sensors-sv20-series-only) to ensure that your air quality sensor devices maintain consistent network communication without relying on dynamic IP allocation protocols, such as the Dynamic Host Configuration Protocol (DHCP). To configure a static IP address on a sensor device, the device must initially connect to Command and update to the latest firmware using DHCP. Once the device’s update process is complete, it has the ability to receive the new static IP configuration. Learn more about [Static IP configuration for Air Quality Sensor Devices](https://help.verkada.com/air-quality/configuration-and-setup/configure-static-ip-addresses-for-air-quality-sensors-sv20-series-only) . #### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-settings#identify-your-sensor) Identify your sensor 1 **On Edit Settings > Device.** 2 **Click Identify to locate the sensor in a room:** * Have the [SV11](https://www.verkada.com/sensors/sv11/) flash blue and orange * Have the [SV21](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) flash orange rapidly for a short amount of time #### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-settings#reboot-a-sensor-device) Reboot a sensor device 1 **On Edit Settings > Device.** 2 **Click Reboot.** You can only reboot the device when the device is able to maintain a connection with the Verkada Command backend. Devices that blink blue or white (and some cases with orange status lights) are unable to remotely reboot this way. #### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-settings#delete-a-sensor-device) Delete a sensor device 1 **On Edit Settings > Device.** 2 **Click Delete.** 3 **Enter the verification code to confirm your request.** Deleting the device from your organization unclaims the device, and anyone who has the serial number can claim it in their organization. This also wipes all sensor data and resets the device back to factory defaults. #### [](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-settings#offline-notifications) Offline notifications You can set notifications for when the sensor goes offline: 1 **On Edit Settings > Device.** 2 **Under Offline Notifications, click Create Alert. Learn more about how to** [**create alerts**](https://help.verkada.com/verkada-cameras/events-and-alerts/create-alerts-across-verkada-products) **.** Last updated 1 day ago Was this helpful? --- # Manage Your Licenses | Command | Verkada Help To have access to [Verkada Command](https://help.verkada.com/command/get-started-with-verkada-command) , you must have valid Verkada licenses for all your Verkada products. [](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses#how-verkada-licensing-is-applied) How Verkada licensing is applied ------------------------------------------------------------------------------------------------------------------------------------------------------- Verkada licensing is applied for each Command organization, and the licenses co-term to a single expiration date. This means that all of the licenses in an organization are combined, and the expiration date for the organization is the weighted average of all the individual licenses. Learn more about how to [calculate a license expiration date](https://help.verkada.com/command/licensing-and-warranty/calculate-license-expiration-date) . * * * [](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses#view-licenses-and-active-products) View licenses and active products --------------------------------------------------------------------------------------------------------------------------------------------------------- Licenses and active products are available on the Command [License Manager page](https://command.verkada.com/admin/org-settings/license-manager) . 1 **In Verkada Command, go to All Products > Admin .** 2 **In the left navigation, select Licenses & Renewals.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F705858581-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FNRq5qDDjsYNxwNzF1bcB%252Fuploads%252Fgit-blob-9c51fdf140fbaab6d9001f86a6d78064ddbe54e6%252Ff8f4fb05373787f14c0406248009cf0d8ce7657a.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=83e4ff21&sv=2) For each product type that requires a license, you see a count of the active products and claimed licenses. If you have _less_ claimed licenses than active products _for any of your product types_, your license state is **Invalid**, which means you’ll need to [claim your license key](https://help.verkada.com/command/licensing-and-warranty/find-and-add-license-keys-to-command) to continue using Command. Learn more about how to [manage your licenses](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses) . If you uninstall or replace a product, for example due to a warranty replacement, you must remember to delete the product from Command. If you do not delete the product, it will continue to count against your active products. Please note that deleting a product also removes all data associated with the product (e.g., footage, camera settings), so do not delete the product before you’re absolutely certain that you will not re-add that specific device to Command. ### [](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses#view-the-license-state-and-expiration-date) View the license state and expiration date At the top left of the **Manage Licenses** page, you can see the expiration date for your licenses and the current License state of your organization. All Verkada licenses [co-term to a single expiration date](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses) , so you will only see a single expiration date even if you have bought and claimed multiple license keys. ### [](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses#view-transaction-log-of-all-license-actions) View transaction log of all license actions The transaction shows a log of all license actions taken in your organization, such as [claiming a new license key](https://help.verkada.com/command/licensing-and-warranty/find-and-add-license-keys-to-command) , or unclaiming a key if it was claimed by mistake. If you have any questions regarding the transactions in your log, contact [Verkada Support](https://help.verkada.com/command/need-help/contact-verkada-support) . ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F705858581-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FNRq5qDDjsYNxwNzF1bcB%252Fuploads%252Fgit-blob-871b39a82960ede722626bb37c2ab5c59027528c%252Fc6322db8e18428880621d4b9c72baa09f4ee8126.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=dcc418c9&sv=2) * * * [](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses#move-devices-between-command-organizations) Move devices between Command organizations --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Licenses do not automatically move with the device. If you need to move devices from one Command organization to another, you need to move the license keys separately. Contact [\[email protected\]](https://help.verkada.com/cdn-cgi/l/email-protection#abc7c2c8cec5d8c2c5ccebddced9c0cacfca85c8c4c6) for support in moving device licenses between Command organizations. * * * [](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses#license-requirements-by-product-family) License requirements by product family ------------------------------------------------------------------------------------------------------------------------------------------------------------------- Refer to this table for an overview of the license requirements of each product family: **Product Family** **License requirement** Access Control One door license per door on: AC62 AC42 AC41 AC12 AX11 IO Controller: One access IO controller license per controller Mobile NFC: One mobile NFC credentials license per 20 users Alarms One alarm license per location (physical address). Alarm licensing covers a limited number of devices and video verification events. In addition, **one license per device** for the following: BZ11 Horn speaker Cellular backup module Learn more about each [alarm license each tier offered](https://help.verkada.com/classic-alarms/compliance-licensing-trials/classic-alarms-licensing) . Cameras One camera license per Verkada camera One camera license per non-Verkada camera (channel) connected to a Command Connector Optional: One Cloud Backup License per 30-day increments on a single device’s cloud retention. Learn more about [Extended Cloud Backup Licensing](https://help.verkada.com/verkada-cameras/historical-playback/extended-cloud-backup-licensing) . Multisensor cameras One MLT2 camera license per two-camera multisensor One MLT4 camera license per four-camera multisensor Environmental sensors One sensor license per environmental sensor Gateway One cellular gateway license per cellular gateway One Wi-Fi gateway license per Wi-Fi gateway Optional: One data plan license per connected camera or intercom. A multisensor camera needs four data licenses. Intercom One Intercom license per intercom device One Desk Station license per iPad running the Verkada Desk Station app Viewing station One viewing station license per viewing station Workplace One Workplace license grants you access to use one Guest iPad and one Mailroom site. * * * [](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses#purchase-command-licenses) Purchase Command licenses ----------------------------------------------------------------------------------------------------------------------------------------- Command licenses are available in 1, 3, 5, and 10-year terms. There are two types of licenses: capacity increase (CAP) and renewal (RNW). * **Capacity Increase (CAP) licenses**: Verkada CAP licenses are automatically activated when the associated Verkada hardware order is shipped. New device licenses include a 30-day extension beyond the purchased term to accommodate shipping and installation. The extension period is fixed and does not depend on when the device is installed or activated. * **Renewal (RNW) licenses:** Verkada RNW licenses extend an organization’s existing term but remain inactive until the earlier of: * The date they are claimed within a Command organization or * One year after the purchase date. If unclaimed after one year, the license automatically activates, and its term begins to run. Any license claimed beyond this one-year period results in a shortened remaining term. This policy ensures compliance with the intended service period. Licenses are usually sold with your Verkada devices, but you can also purchase them separately from your Verkada reseller or sales representative. See the latest [licensing prices](https://www.verkada.com/pricing/) . * * * [](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses#renew-your-licenses) Renew your licenses ----------------------------------------------------------------------------------------------------------------------------- When your licenses are soon to expire, you need to renew your license to avoid losing access to Verkada Command. You can renew your license by contacting your Verkada Sales Representative or your Verkada Reseller. ### [](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses#renewal-notifications-and-license-expiration) Renewal notifications and license expiration 30 days before expiry, you will expect to: * Receive an email notifying you that your licenses are about to expire. * See a banner in Command. You will lose access to Command if you haven’t renewed your license within 30 days after your expiration date. * * * [](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses#licensing-overcap-policy) Licensing overcap policy --------------------------------------------------------------------------------------------------------------------------------------- An organization is considered to be in overcap when it has more devices commissioned than the number of licenses claimed. ### [](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses#overcap-policy) Overcap policy Verkada enforces software compliance by requiring each hardware product to have a valid, claimed software license(see requirements above). The Overcap policy introduces an **Invalid** status for organizations that exceed their claimed licenses, ensuring compliance across all Verkada products. After a 90-day grace period, organizations without proper licensing lose access to critical functions, including device management and notifications. ### [](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses#how-it-works) How it works Verkada will notify all Command users 90 days **before** an organization loses access, prompting them to claim additional licenses. Organization Admins will receive in-product banners and emails over 90 days to ensure they restore compliance. All devices will remain functional when access to Command is restricted. However, users will still have access to the **License Manager**, **Devices**, and **Technical Support** pages when an organization is no longer compliant. ### [](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses#restore-compliance) Restore compliance Organization Admins can perform **one** of the following actions to restore compliance: * Claim any unused licensing keys. * Remove any unused devices from the organization. * Contact your Sales Representative or email [\[email protected\]](https://help.verkada.com/cdn-cgi/l/email-protection#e08c8983858e93898e87a09685928b818481ce838f8d) if you believe there has been an error with the licensing implementation on your account. * * * [](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses#faq) FAQ --------------------------------------------------------------------------------------------- What happens if I have insufficient or expired licenses?[](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses#what-happens-if-i-have-insufficient-or-expired-licenses) Verkada will send you an email notification and add a banner notification to your Command Organization. You need valid licenses to use Command. If you don’t [claim your licenses](https://help.verkada.com/command/licensing-and-warranty/find-and-add-license-keys-to-command) when adding new devices or products or renew them when they expire, you will lose access to most of your Command functionality after a 30-day grace period. * For expired organizations, you have a 30-day grace period before you lose access. * For organizations with insufficient licenses, you have a 90-day grace period before you lose access. * Contact your Verkada Partner or Sales Representative to purchase additional licenses. At the end of this grace period, you will no longer have access to any of your devices or configure any settings. Alarms and Event notifications will also be disabled. You will, however, be able to delete devices and products so you get back into compliance in case you have insufficient licenses. How will I know if my licenses are soon to expire?[](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses#how-will-i-know-if-my-licenses-are-soon-to-expire) 30 days before your license is set to expire, Verkada will send you an email notification and add a banner notification to your Command Organization. How do I regain full access to Command?[](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses#how-do-i-regain-full-access-to-command) If your access to Command was limited due to insufficient licenses, you can: * Delete the products that are above your license cap to get back into compliance * Contact your Verkada Partner or Sales Representative to purchase additional licenses. If your access to Command was limited due to expired licenses, you can contact your Verkada Partner or Sales Representative to renew your licenses. Will my devices still record data?[](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses#will-my-devices-still-record-data) As long as your Verkada devices are still connected, they will continue to record data. This data will be available when you regain access to Command (as long as you’re still within the retention period for the given device). Badges and Verkada Pass will still work as before, but you’ll be unable to change your settings via Command. What happens if I don’t return my expired trial devices?[](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses#what-happens-if-i-dont-return-my-expired-trial-devices) Trialing a Verkada device is the best way to experience how our products and platform works. You can initiate a free trial for most of our devices through your Verkada Sales Rep, or your Verkada Partner. The free trial lasts for 30 days. After the 30 days are up, you’ll see a banner in Command reminding you to return or purchase your trial devices. If you don’t return the devices within 30 days of the expiry date they will stop working as expected. If you need additional time to test our trial devices and platform, you can ask your Verkada Sales Rep for an extension. * * * **Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=uzn7B9k2qpU) . Last updated 1 day ago Was this helpful? --- # Manage Sites and Subsites | Verkada Cameras | Verkada Help Verkada sites are a logical way of grouping and managing devices within [Verkada Command](https://help.verkada.com/command/get-started-with-verkada-command) and provide several feature options that make managing and viewing the devices in a site easier. Site permissions are broken down into roles, so you can also specify the type of access each user or group has to devices within the site. To make the viewing experience more secure, users can only see devices in the sites where they have been granted access. This allows you to scope which devices are accessible to each user or group. See [Roles and Permissions for Command](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) for more information. Subsites are used to grant permissions to specific sections of a site. This eliminates having to create a new site each time you need to scope permissions to one or more devices. You can nest a subsite in other subsites, providing a permissions hierarchy for better access control. An example use case: Only allowing access to outdoor cameras. * * * You need at least **Site Admin** permissions to create and manage sites. [](https://help.verkada.com/verkada-cameras/configuration-and-setup/manage-sites-and-subsites#create-a-site) Create a site ------------------------------------------------------------------------------------------------------------------------------- 1 **In Verkada Command, go to All Products > Cameras.** 2 **At the top right, click Manage Sites. Alternatively, on the left navigation, click the Sites icon.** 3 **At the top right, click Create Site.** 4 **Name your site and click Add.** ### [](https://help.verkada.com/verkada-cameras/configuration-and-setup/manage-sites-and-subsites#rename-a-site) Rename a site 1 **In Verkada Command, go to All Products > Admin.** 2 **On the left navigation, click the Sites icon.** 3 **Click the ellipses icon and select Rename to change the name of the site. Alternatively, to the right, you can click the site’s name to edit it inline.** ### [](https://help.verkada.com/verkada-cameras/configuration-and-setup/manage-sites-and-subsites#delete-a-site) Delete a site 1 **In Verkada Command, go to All Products > Admin.** 2 **On the left navigation, click the Sitesicon.** 3 **Select the site that you want to delete.** 4 **Confirm that all devices in that site have been deleted or moved to another site.** 5 **At the top right, click the ellipses dropdown and select Delete.** * * * [](https://help.verkada.com/verkada-cameras/configuration-and-setup/manage-sites-and-subsites#configure-settings-and-permissions) Configure settings and permissions ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- When you access and select a site, you have more options to configure for that site. You need at least **Site Admin** permissions to create and manage sites. 1 **In Verkada Command, go to All Products > Cameras.** 2 **In the left panel, select a specific site or click Manage Sites.** 3 **Click the kebab icon and select a specific site.** 4 **For selected site, configure these settings, as needed:** * **Reorder Cameras**—Change the order in which you see the cameras. This feature is helpful where you can prioritize the feeds you want to see in a specific order. * [**View as Grid**](https://help.verkada.com/verkada-cameras/live-streaming/cuadriculas) —Display all the cameras in the site as a grid. * **View Site Stats**—View trends of data usage for cameras at the site and individual level. * **Set Bandwidth Limit**—Restrict the amount of network resources allocated to camera-related activities, such as streaming. * **Share Site**—[Share camera sites and floor plans](https://help.verkada.com/verkada-cameras/sharing-video/share-multiple-cameras) (in bulk) to give people temporary access to a site or subsite. * **Star Site**—[Create a starred view](https://help.verkada.com/verkada-cameras/configuration-and-setup/manage-sites-and-subsites#h_2513e8a755) to filter your most viewed sites. ### [](https://help.verkada.com/verkada-cameras/configuration-and-setup/manage-sites-and-subsites#add-cameras-to-an-empty-site) Add cameras to an empty site 1 **In Verkada Command, go to All Products > Cameras.** 2 **Scroll down until you see the empty site.** 3 **Click the camera icon.** 4 **Select Add New Cameras to be taken to the Add Devices page with this site preselected.** ### [](https://help.verkada.com/verkada-cameras/configuration-and-setup/manage-sites-and-subsites#move-cameras-to-a-new-site) Move cameras to a new site 1 **In Verkada Command, go to All Products > Cameras.** 2 **At the top left, check the box next to the camera’s feed. You should see a bar at the top of the page.** 3 **Use the Select Site dropdown box to select the destination site to move the cameras to** 4 **Select Move Cameras to this site and add the cameras you want to move.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1795869993-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FylYKicREo6JpuOJH4teK%252Fuploads%252Fgit-blob-86c4311e345859b1164f8a26a302c013ff62594a%252F7dd67e6c3d22cee28c564eae3c9f9756912b278d.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=5284e251&sv=2) ### [](https://help.verkada.com/verkada-cameras/configuration-and-setup/manage-sites-and-subsites#manage-your-sites-permissions) Manage your site’s permissions The Site Manager page allows admins to view the number of users who have access to the site and their permissions and roles based on the products on the site. 1 **In Verkada Command, go to All Products > Admin.** 2 **On the left navigation, click Sites.** 3 **Select the site where you want to manage permissions.** 4 **On the right pane, select Manage Permissions. You should see a list of all user groups and users in the organization.** 5 **At the top right, use the search field to find a specific group or user and click that group’s or user’s row.** 6 **Edit the various roles that apply to the user.** You cannot edit roles that have been inherited from a parent site or a group. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1795869993-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FylYKicREo6JpuOJH4teK%252Fuploads%252Fgit-blob-fc34ec9bea2ce9e6d975044b93da411429ddb76f%252Fb9bc3c18d6e905020015618e9e8374e7eb5c3a78.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=da5170c&sv=2) Alternatively, you can manage your permissions as follows: 1 **In Verkada Command, go to All Products > Cameras.** 2 **In the left panel, select a specific site or click Manage Sites.** 3 **On the Sites page, at the far right, click Manage Permissions.** 4 **Continue with steps above to manage your site’s permissions, as needed.** * * * [](https://help.verkada.com/verkada-cameras/configuration-and-setup/manage-sites-and-subsites#view-all-sites) View all sites --------------------------------------------------------------------------------------------------------------------------------- You need at least **Live-Only Viewer** permissions to view sites. 1 **In Verkada Command, go to All Products > Admin.** 2 **On the left navigation, click Sites.** Alternatively, for any Verkada device, at the top right, you can click **Manage Sites**. All of your organization’s sites are listed on the left, with subsites nested under their respective parent sites. Learn more about the various view options you can configure for your site below. ### [](https://help.verkada.com/verkada-cameras/configuration-and-setup/manage-sites-and-subsites#view-your-specific-sites-and-subsites) View your specific sites and subsites 1 **In Verkada Command, go to All Products > Cameras.** 2 **By default, a site is selected. At the top of your collected footage (as shown), press Shift+hover over the title of the site allows you to quickly expand and collapse all parent sites at the same level. Or, optionally, click All Sites to see all of your sites.** 3 **Next to the site name, click the kebab icon and select a specific site.** 4 **Click Sites. and this expands the Sites panel (on the left), where you can see all sites (expand or collapse) and click through (or filter) the sites.** ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1795869993-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FylYKicREo6JpuOJH4teK%252Fuploads%252Fgit-blob-e5188171a585db12d857dbe46d3d3b1f9e694700%252F9adc2e7e226384c252b95d145465cdeab9965ef2.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=a768cca&sv=2) 5 **On the sites panel, click Manage Sites to open the Sites page.** ### [](https://help.verkada.com/verkada-cameras/configuration-and-setup/manage-sites-and-subsites#view-additional-details) View additional details You can view additional details about the selected site on the right pane: * Total number of devices contained in the site, broken down by device type. * Additional details if the site is an Alarm, Guest, or Mailroom site. ### [](https://help.verkada.com/verkada-cameras/configuration-and-setup/manage-sites-and-subsites#create-a-starred-site-view) Create a starred site view On your **Sites** page, at the top left, click the **star**![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1795869993-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FylYKicREo6JpuOJH4teK%252Fuploads%252Fgit-blob-1fd84aeedca19f1c764275ac18079e6c7e55b203%252Fe18b7708eae2bc78163438b2c9f6c9f67e8982a3.png%3Falt%3Dmedia&width=300&dpr=4&quality=100&sign=42cf4573&sv=2)icon next to the site you want to keep your most visited sites easily accessible. On the right pane, you click the **star**![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1795869993-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FylYKicREo6JpuOJH4teK%252Fuploads%252Fgit-blob-1fd84aeedca19f1c764275ac18079e6c7e55b203%252Fe18b7708eae2bc78163438b2c9f6c9f67e8982a3.png%3Falt%3Dmedia&width=300&dpr=4&quality=100&sign=42cf4573&sv=2)icon (or click again to remove the star) for a site. 1 **In Verkada Command, go to All Products > Cameras.** 2 **At the top, next to the site name, click the kebab dropdown and select Star Site. Alternatively, you can also create a star site from the** [**Site Manager**](https://help.verkada.com/en/articles/8590140-site-manager) **page.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1795869993-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FylYKicREo6JpuOJH4teK%252Fuploads%252Fgit-blob-5675d09dc8f59c3db4168f58e1bcda1ebbdf4a84%252Fdb98907bd78836781b21214da83f5a5664dd5645.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=51617573&sv=2) 3 **When you select a star site, that site displays on the left site navigation as Starred. Only the starred site/subsite displays on the menu. Sites higher or lower on the hierarchy aren’t automatically starred.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1795869993-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FylYKicREo6JpuOJH4teK%252Fuploads%252Fgit-blob-8519ac206f443c31bcb85388aa16c8cfa1776c13%252Fc5c3ca2c93f72278dcd703f4798c66bc0a3a1f02.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=b183ba35&sv=2) ### [](https://help.verkada.com/verkada-cameras/configuration-and-setup/manage-sites-and-subsites#remove-a-star-from-a-site) Remove a star from a site 1 **In Verkada Command, go to All Products > Cameras.** 2 **At the top, next to the site name, click the kebab dropdown and select Unstar Site. Alternatively, you can also unstar a site from the** [**Site Manager**](https://help.verkada.com/en/articles/8590140-site-manager) **page.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1795869993-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FylYKicREo6JpuOJH4teK%252Fuploads%252Fgit-blob-1d6bf4ab4e05d2316587dcbbec9d73ce83776894%252F4a84b5607b7e2f93d90f3fb4bdea5042dfe93716.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=d0c5ae52&sv=2) * * * [](https://help.verkada.com/verkada-cameras/configuration-and-setup/manage-sites-and-subsites#manage-subsites) Manage subsites ----------------------------------------------------------------------------------------------------------------------------------- You need at least **Site Admin** permissions to create and manage subsites. Subsites are used to grant permissions to specific sections of a site. This eliminates having to create a new site each time you need to scope permissions to one or more cameras. You can nest a subsite in other subsites providing a hierarchy of permissions for better access control. An example use case: Only allowing access to outdoor cameras. ### [](https://help.verkada.com/verkada-cameras/configuration-and-setup/manage-sites-and-subsites#create-a-subsite) Create a subsite 1 **In Verkada Command, go to All Products > Admin.** 2 **On the left navigation, click Sites.** 3 **Select the site that you want to create a subsite for.** 4 **At the top right, click Add Subsite.** 5 **Name your subsite and click Add.** ### [](https://help.verkada.com/verkada-cameras/configuration-and-setup/manage-sites-and-subsites#create-a-subsite-within-a-named-site) Create a subsite within a named site 1 **In Verkada Command, go to All Products > Cameras.** 2 **At the top right, click Manage Sites.** 3 **Hover over the site you where you want to create a subsite.** 4 **At the far right of that site, click Subsite.** 5 **On the Add New Subsite Within <**_**"your selected site">**_**, enter a new subsite name, and click Add.** ### [](https://help.verkada.com/verkada-cameras/configuration-and-setup/manage-sites-and-subsites#delete-a-subsite) Delete a subsite You cannot delete a site or subsite until all cameras and subsites have been removed\*.\* 1 **In Verkada Command, go to All Products > Cameras.** 2 **At the top right, click Manage Sites.** 3 **Hover over the site you want to delete.** 4 **On the right side, click Delete.** 5 **Click Delete to confirm.** * * * **Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=wqcg5pRMqbI) . Last updated 1 day ago Was this helpful? --- # BACnet for Verkada Air Quality Sensors | Air Quality | Verkada Help Verkada [Air Quality Sensors](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) offer your organization a way to monitor essential indoor air quality factors, such as [CO2](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) , [CO](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) , [PM 2.5](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) , [PM 4.0](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) , [PM 10.0](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) , [AQI](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) , [TVOC](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) , and [formaldehyde](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) . The [Building Automation and Control Networks (BACnet)](https://www.ashrae.org/technical-resources/technical-faqs/question-51-what-is-bacnet) integration allows Verkada sensors to inform a building’s Heating, Ventilation, and Air Conditioning (HVAC) system about an air quality metric or any sensor reading, allowing the building HVAC to respond to these indoor air quality conditions. Verkada sensors can integrate with the Building Management System (BMS) protocol, BACnet. By integrating Verkada’s sensors with this protocol, your organization’s HVAC systems can now automatically respond to suboptimal air conditions. Learn how to [configure BACnet for your Verkada Air Quality Sensors](https://help.verkada.com/air-quality/configuration-and-setup/configure-bacnet-on-air-quality-sensors) . [](https://help.verkada.com/air-quality/configuration-and-setup/bacnet-for-verkada-air-quality-sensors#about-bacnet) About BACnet -------------------------------------------------------------------------------------------------------------------------------------- BACnet is a communication protocol specifically designed for building automation and control systems. It is an industry-standard protocol used to facilitate the exchange of data between various devices and systems within a building, such as HVAC, lighting, security, and other building automation systems. BACnet provides a standardized way for different devices and systems from different manufacturers to communicate with each other, regardless of the underlying hardware or software implementation. The goal of BACnet is to enable efficient and standardized communication between different building automation devices, promoting interoperability, scalability, and flexibility in the design and operation of building control systems. [](https://help.verkada.com/air-quality/configuration-and-setup/bacnet-for-verkada-air-quality-sensors#benefits-of-bacnet) Benefits of BACnet -------------------------------------------------------------------------------------------------------------------------------------------------- Here are some instances where the intuitiveness of BACnet can be beneficial to your organization: * Adjusts the temperature in a room or building to save costs * Adjusts the output of dampers to increase fresh air circulation in a room * Turns on supply fans * Automatically closes windows when poor air quality is detected * Automatically turns on air filtration systems and increases outdoor airflow when the CO2 levels are high * Only runs air through filtration systems when pollution thresholds are met, to avoid unnecessary filtration when the air is clean * Automatically increases the ventilation rate in a lab when there are high levels of VOCs * Uses the [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) and [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) as occupancy sensors to save on HVAC energy costs, if programmed to allow the HVAC system to reduce its operation when the room is unoccupied * Uses the [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) light sensor to turn off the lights in a room when it is unoccupied, but light is detected * Triggers a strobe or alarm if vaping is detected [](https://help.verkada.com/air-quality/configuration-and-setup/bacnet-for-verkada-air-quality-sensors#use-cases-for-bacnet) Use cases for BACnet ------------------------------------------------------------------------------------------------------------------------------------------------------ If your BMS, also sometimes called a Building Automation System (BAS), supports BACnet, you can use Verkada sensors as inputs to control HVAC equipment or any other equipment inside your BMS. BACnet allows centralized control and monitoring, and by accepting various input readings from Verkada sensors, such as temperature, humidity, [PM 2.5](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) , [TVOC](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) , and [CO2](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) among others, can be used to control the outputs to remediate the effects. For example, a sensor installed in a meeting room could trigger a high CO2 alert, which would then feed this information in turn to the BAS/BMS, which in turn controls a specific action such as powering on a ventilation fan or damper in the meeting room. [](https://help.verkada.com/air-quality/configuration-and-setup/bacnet-for-verkada-air-quality-sensors#example-implementation) Example implementation ---------------------------------------------------------------------------------------------------------------------------------------------------------- **Scenario**: You want your Verkada Air Quality sensor to monitor CO2 in a conference room and increase fresh air flow when CO2 hits 700 ppm. 1 **Install the Verkada Air Quality Sensor and put it on your BACnet network.** 2 **Enable BACnet on the device and give it a unique device ID. See** [**how to enable BACnet on a device**](https://help.verkada.com/air-quality/configuration-and-setup/bacnet-for-verkada-air-quality-sensors#h_2d2ca08f93) **.** 3 **Go to your BACnet over IP compatible BMS, and use the "discover" feature to find your Verkada sensor. In this example, use Vykon WorkPlace N4.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-fd9d50cadad9e68ea06b41585b5bab03824c09b3%252F6b94c8262ff8c822caa8cfef838c007623a67d60.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=27ab36c&sv=2) This returns the BACnet devices found on the network. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-3813a336bbd7f67860d06d46d6432000bf68203b%252F8301a638e4c71999af53ac0f2f3ec89702570185.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=25408f1b&sv=2) 4 **Rename the device and add it to your BMS.** 5 **Run a BACnet Who-Has discover to find all the available points.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-1c2ea640a84a70088dc5f3b7d534337669157a5e%252Fa9115d3d1199859d819e7d8e4e5fb7d4f4fe39f1.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=cce6823b&sv=2) 6 **Add the points to your BMS and use them to make HVAC decisions.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-51af7f3175cd3fcd1a81cc3f7159b86fc102015d%252F54011e3800ce03b65114bdaeb9c14883591f96ee.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=8b0e31ac&sv=2) a. In this case, **In2** is linked to the SV25 CO2 reading, which goes to **In A** which is a **GreaterThanEqual** function. b. If the **SV25 CO2** reading is above **700 ppm**, send **True**; otherwise, send **False**. c. Link the **Out** (the output) of that function to the input of a BooleanWritable variable; in this case, **In16**. **In16** determines the **Out** boolean. d. Link the **Out** boolean to your damper control. * If **Out** is True, the damper is **open**. * If **Out** is **False**, the damper is **closed**. [](https://help.verkada.com/air-quality/configuration-and-setup/bacnet-for-verkada-air-quality-sensors#faq) FAQ -------------------------------------------------------------------------------------------------------------------- Do all BMSs/BASs use BACnet?[](https://help.verkada.com/air-quality/configuration-and-setup/bacnet-for-verkada-air-quality-sensors#do-all-bmss-bass-use-bacnet) No, not all Building Management Systems (BMSs)/Building Automation Systems (BASs) support BACnet. Most major HVAC providers have products and controllers that support this feature. However, you should talk with your HVAC specialist to understand if your system is supported. **Required**. Your building must have a BAS that is compatible with BACnet IP to use this integration. We recommend that you contact your HVAC specialist to understand if your system is supported. If you are unsure whether your BAS supports BACnet, contact [Verkada Support](https://www.verkada.com/contact/) for additional assistance. Which sensor readings are supported by BACnet?[](https://help.verkada.com/air-quality/configuration-and-setup/bacnet-for-verkada-air-quality-sensors#which-sensor-readings-are-supported-by-bacnet) You can use all Verkada [sensor readings](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) as inputs for your BMSs, such as [temperature](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) , [humidity](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) , [CO2](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) values, [Vape Index](https://help.verkada.com/air-quality) , and so on, to control dampers, ventilation fans, or other HVAC equipment. Do Verkada sensors control the HVAC directly?[](https://help.verkada.com/air-quality/configuration-and-setup/bacnet-for-verkada-air-quality-sensors#do-verkada-sensors-control-the-hvac-directly) No, the Verkada sensors do not control the building’s HVAC system directly. Instead, the sensors relay their readings to your BMS, which in turn uses these as inputs in a function that controls the building’s HVAC, such as adjusting the temperature in a room or increasing the airflow in a closed space. Do Verkada Air Quality monitors support BACnet MS/TP?[](https://help.verkada.com/air-quality/configuration-and-setup/bacnet-for-verkada-air-quality-sensors#do-verkada-air-quality-monitors-support-bacnet-ms-tp) No, BACnet Master Slave (MS)/Token Passing (TP), the hard-wired version of BACnet that requires an [RS-485](https://en.wikipedia.org/wiki/RS-485) connection, similar to our access control readers, is currently not supported by Verkada Air Quality Sensors. Contact your SE should you require additional information or support. What does BACnet do when enabled?[](https://help.verkada.com/air-quality/configuration-and-setup/bacnet-for-verkada-air-quality-sensors#what-does-bacnet-do-when-enabled) Once BACnet is enabled on a device, the BMS controller is now able to "discover" the device on the BACnet network. This is why the BACnet device needs a device ID, which is used to identify the device on the network, as well as a port, also used for communication.The server will initiate a handshake with the device via the "Who-Is/I-Am" flow. It will then figure out what properties the device has with the "Who-Has/I-Have" flow. The Verkada [SV21](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , and [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) all support the BACnet/IP protocol and support IPv4. The UDP port defaults to 47808 (0xBAC0). Last updated 19 hours ago Was this helpful? --- # Classic Alarms Sites | Classic Alarms | Verkada Help This article is a guide for classic Alarms. Refer to this [article](https://help.verkada.com/new-alarms/configuration-and-setup/alarm-sites) if you have new Alarms. See [New Alarms vs Classic Alarms](https://help.verkada.com/new-alarms/new-alarms-vs-classic-alarms) if you are unsure which version of Alarms you have. * * * Alarms sites allow you to manage your Alarms devices. Events from other devices in the organization (cameras, air quality sensors, doors) can become alarm triggers with customizable response actions. A site automatically becomes an Alarms site when you add an alarm panel or alarm console. * * * [](https://help.verkada.com/classic-alarms/configuration-and-setup/classic-alarms-sites#create-a-new-site) Create a new site --------------------------------------------------------------------------------------------------------------------------------- 1 **In Verkada Command, go to All Products > Alarms.** 2 **At the top right, click Add Alarm Site.** 3 **On Location:** a. Click the **Site** dropdown and select **Add New Site**. b. On **Add New Site**, enter a unique site name, and click **Add**. c. Click the **Location** dropdown and select **Add New Address**, and click **Next**. d. **Confirm** the location. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-b7dfee18f51f18d96a37a139840217fadf5f4175%252Faaa7d75b0e0e99256d45520052e24b0e611e2828.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=f25ba884&sv=2) * * * [](https://help.verkada.com/classic-alarms/configuration-and-setup/classic-alarms-sites#designate-an-existing-site-as-an-alarms-site) Designate an existing site as an Alarms site --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 1 **In Verkada Command, go to All Products > Alarms.** 2 **At the top right, click Add Alarm Site.** 3 **On Location:** a. Select the desired site. b. Set the location to the address that you would like first responders to be dispatched to the event of an emergency. 4 **Follow the prompts to configure your new alarm site.** * * * [](https://help.verkada.com/classic-alarms/configuration-and-setup/classic-alarms-sites#move-devices-between-alarms-sites) Move devices between Alarms sites ----------------------------------------------------------------------------------------------------------------------------------------------------------------- 1 **In Verkada Command, go to All Products > Alarms.** 2 **Select your alarm site.** 3 **At the top, select Devices.** 4 **Hover over any one of the alarm devices and at the top right of the device, click the ellipsis icon and select Move to move the device to the new alarm site.** ​ **Watch this video to see how this works** * * * [](https://help.verkada.com/classic-alarms/configuration-and-setup/classic-alarms-sites#remove-devices-from-your-alarms-site) Remove devices from your Alarms site ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- 1 **In Verkada Command, go to All Products > Alarms.** 2 **Select your alarm site.** 3 **At the top, select Devices.** 4 **Select a device by clicking it and then select the 3 vertical dots in the right-hand corner.** 5 **Hover over any one of the alarm devices and at the top right of the device, click the ellipsis icon and select Delete to remove the devices from the alarm site.** When you delete an alarm console or alarm panel, the action also removes these devices from your organization. Last updated 23 hours ago Was this helpful? --- # How to Arm/Disarm Your Alarm Site | Classic Alarms | Verkada Help There are multiple methods you can use to arm/disarm your alarm site: * Verkada [Command website](https://help.verkada.com/classic-alarms/configuration-and-setup/how-to-armdisarm-your-alarm-site#h_eaec729e84) * [Alarm console via the keypad](https://help.verkada.com/classic-alarms/configuration-and-setup/how-to-armdisarm-your-alarm-site#h_4e6eb5e049) * [Alarms app or Command app](https://help.verkada.com/classic-alarms/configuration-and-setup/how-to-armdisarm-your-alarm-site#h_a5a0ab48bc) #### [](https://help.verkada.com/classic-alarms/configuration-and-setup/how-to-armdisarm-your-alarm-site#command-website) Command website 1 **In Verkada Command, go to All Products > Alarms. The current state of your alarm site is described by the status under the name of the site.** 2 **Under the name of the alarm site, you have 2 option to disarm:** * Toggle on **Disarmed** to disarm your system. * Clicking the **Armed** slider. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-02c293ba7459566261c9e7aabc25f16225981d93%252F0e94e59f6894ee7c28f12291d30accafe4911f29.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=5570a235&sv=2) ### [](https://help.verkada.com/classic-alarms/configuration-and-setup/how-to-armdisarm-your-alarm-site#alarm-console-via-the-keypad) Alarm console via the keypad Users without access to Command can arm/disarm the system from [configured keycode(s)](https://help.verkada.com/classic-alarms/configuration-and-setup/configure-classic-alarms-site-settings) in your alarm site or the user [keycodes](https://help.verkada.com/classic-alarms/configuration-and-setup/generate-a-user-or-general-keycode-with-classic-alarms) . In the alarm console, enter one of your configured site-level or user-generated 6-digit keycode(s) to arm/disarm the system. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-0372668182addf3419cd52b426b155e3edc10352%252Fc3519f48467a6b01020bf991acb770567750beb8.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=babe8378&sv=2) ### [](https://help.verkada.com/classic-alarms/configuration-and-setup/how-to-armdisarm-your-alarm-site#alarms-app-or-command-app) Alarms app or Command app Command users of **any** access level who are granted [user permissions](https://help.verkada.com/classic-alarms/roles-and-permissions-for-classic-alarms) can also arm/disarm alarm sites from the Verkada **Alarms mobile app** or the **Verkada Command mobile app**. 1 **Log in to the app using your Command credentials.** 2 **Next to the alarm site name, click the Shieldicon to arm/disarm. For the Command app, click the Alarmsicon.** ​**Example**: Alarms App (Disarmed) ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-6fe77af639f63783261be7768822b2d9ec948aba%252Fe7ef68c33a4ca029dc03707c60a01d93d6b6262b.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=9048bae9&sv=2) **Example**: Alarms App (Armed) ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-730c380f266a83a30bd9cb48ee8067701cc051bf%252Fa9ea9bd487b980abd50b9809487eae0a49982b56.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=d73679e9&sv=2) ​**Example**: Command App ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-ea355ed2fd2e30c47ec51d8e0d6cf861692c8ee0%252F4c4cb96dff117c661309f36a95cfe46592a4d23a.jpg%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=6503c3c9&sv=2) [](https://help.verkada.com/classic-alarms/configuration-and-setup/how-to-armdisarm-your-alarm-site#badge-to-arm-disarm-from-the-access-controller) Badge to arm/disarm from the access controller ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- You can configure a reader on a door to arm or disarm an alarm site. The door you choose to select can be in any site. **Recommendation**. We recommend to use 2 separate doors to arm and disarm the site. If preferred, however, you can use the **Toggle via Doors** option to configure the door to change the state from armed to disarmed, or vice versa when triggered. Once the door is selected, a valid unlock event (for example, a keycard, Bluetooth, and remote unlock) arms/disarms the site. To select the door to disarm or arm a site, you must go to your alarms site settings: 1 **In Verkada Command, go to All Products > Alarms > Select Site > Settings.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-e6edc2cef2696b174fb30ab31a77df8878f3ac9a%252F7e94c682574a1896a976f7b02f206a03eb27f41a.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=3fdbbeef&sv=2) 2 **Once in the alarms site settings, click Arm/Disarm > Select Doors.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-869ab36b7efe0b3886f25d9963561020557c7021%252F004c6ccb870ce0f708737a9438b13e003ec1f334.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=f6918ad0&sv=2) Last updated 23 hours ago Was this helpful? --- # Delete Air Quality Sensors from Command | Air Quality | Verkada Help When you delete an air quality sensor from Verkada Command, you erase all of its data and reset it to factory default settings. This is a good way to reset the sensor and start over, move it to a different organization, or remove it, if no longer needed. You must be an Org Admin with Site Admin permissions on the site that contains the sensor(s) to delete and remove sensors from your org. Learn more about [Roles and Permissions for Command](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command) . 1 **In Verkada Command, go to All Products > Air Quality.** 2 **Select the sensor you want to delete.** 3 **On the sensor’s page, at the top right, click Settings.** 4 **On Edit Settings, go to Device.** 5 **At the right of Delete Device, click Delete.** ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-1afe51ec32183937e628ad4e941229e7c136fff8%252F8daa249b109d41ef7676b0c2c4a9a7ec7c51910e.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=f0692644&sv=2) 6 **Complete the validation prompt for the selected device and click Apply.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-bc11ab3d32da7266bbfa3d9b6913e586ead3a2cd%252F20d75e34ed899146654445e5d686934bf0c6c077.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=80b52f3b&sv=2) [](https://help.verkada.com/air-quality/configuration-and-setup/delete-air-quality-sensors-from-command#delete-a-sensor-from-the-mobile-app) Delete a sensor from the mobile app ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 1 **In your Command app, go to Air Quality > Home.** 2 **Select and tap the sensor you want to delete.** ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-163526017ac047ecaf5953b26964cca18265330f%252F2f49b00c20e7e3fa8ec67da49efa34da97dcf43d.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=4ce6d099&sv=2) 3 **At the top right, tap the option menu > Settings.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-c80732afd056380a39881febd784b0b149963ace%252F14da606c7effbfd137238c2c726e44445aa68b79.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=4d46fa67&sv=2) 4 **Tap Delete Sensor.** 5 **Follow the prompts to confirm.** ### [](https://help.verkada.com/air-quality/configuration-and-setup/delete-air-quality-sensors-from-command#bulk-delete-sensors-from-command) Bulk delete sensors from Command 1 **In Command, go to All Products > Devices.** 2 **Filter for device type: Air Quality.** 3 **Check the box next to the sensors you want to delete.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-d4402c1d6a0ea8fe80c2457416fb5e01a92f2c94%252F1ab4c9e3ac5e795e2c28d434e777f630ca9becf4.jpg%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=3d894867&sv=2) Alternatively, at the top, click the black box (with white vertical line) to select **all** devices within the **site** or **org**. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-c76c357f25ae5bde1708e1697bc04405f3984b33%252Ff163a626b5e30d09c9108f848111cc62618e9599.jpg%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=f7054ce8&sv=2) 4 **At the top right, click Delete. Note: This may appear asif you’re viewing from a mobile browser or a low-resolution monitor.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-eadd2cb38f87e9e73d4be8959745d3e908788e97%252Fb4b1f72cb40f3277b3ed0ee27a40e87a2fa22fd1.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=b0cc5854&sv=2) Last updated 22 hours ago Was this helpful? --- # Manage Alerts Across Verkada Products | Verkada Cameras | Verkada Help Alerts notify you of important events from your organization. This allows you to shift from reactive to proactive monitoring. The [Alerts](https://command.verkada.com/alerts/device-events) page lets users view their subscribed alerts to easily find important events and relevant footage. You can set up alerts for events across the [cameras](https://help.verkada.com/verkada-cameras/events-and-alerts/create-camera-event-alerts) , intercom, [access control](https://help.verkada.com/access-control/alerts-and-events/configure-access-control-event-alerts) , [alarms](https://help.verkada.com/classic-alarms/events-and-alerts/configure-alarms-event-alerts) , [gateway](https://help.verkada.com/connectivity/events-and-alerts/configure-gateway-status-alerts) , and [air quality](https://help.verkada.com/air-quality/events-and-alerts/configure-air-quality-event-alerts) product lines. * * * [](https://help.verkada.com/verkada-cameras/events-and-alerts/manage-alerts-across-verkada-products#edit-alerts) Edit alerts --------------------------------------------------------------------------------------------------------------------------------- 1 **On the Command homepage, left navigation, click Alerts .** 2 **Under My Alerts:** a. Hover over the alert you want to edit. b. To the right of the alert, click . c. Select **Edit Alert**. d. Select the event setup step you want to edit and make any needed changes. e. Click **Done** and repeat with other event setup steps as needed. 3 **Click Save once all changes have been made.** Alerts configured with the old alert system containing multiple event times are not supported under the new alert system. If you see the message **Editing this alert is no longer supported,** recreate the alert to update its configuration or contact [Verkada Support.](https://help.verkada.com/command/need-help/contact-verkada-support) ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1795869993-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FylYKicREo6JpuOJH4teK%252Fuploads%252Fgit-blob-cf69d2c6a7e39ad56a3845573170766833961935%252Ffb132ea804f6784d1499e6554b230f5e2ddf2999.png%3Falt%3Dmedia&width=300&dpr=4&quality=100&sign=a38bd934&sv=2) * * * [](https://help.verkada.com/verkada-cameras/events-and-alerts/manage-alerts-across-verkada-products#mute-alerts) Mute alerts --------------------------------------------------------------------------------------------------------------------------------- #### [](https://help.verkada.com/verkada-cameras/events-and-alerts/manage-alerts-across-verkada-products#mute-an-alert) Mute an alert 1 **On the Command homepage, left navigation, click Alerts .** 2 **Under My Alerts:** a. Hover over the alert you want to mute. b. To the right of the alert, click . c. Select **Mute Alert** and choose the duration. If you choose **Custom**, set the duration and click **Apply**. #### [](https://help.verkada.com/verkada-cameras/events-and-alerts/manage-alerts-across-verkada-products#mute-all-alerts) Mute all alerts 1 **In Command, go to All Products > Admin.** 2 **On Org Settings, select Manage Alerts.** 3 **In the top right, click the mute icon to mute all alerts.** a. Choose the duration for the alert to mute. b. (Optional) If you choose **Custom**, set the duration and click **Apply**. c. Click **Yes** to confirm and mute all alerts. Muting an alert will only mute it for your account and not other alert recipients. * * * [](https://help.verkada.com/verkada-cameras/events-and-alerts/manage-alerts-across-verkada-products#delete-alerts) Delete alerts ------------------------------------------------------------------------------------------------------------------------------------- 1 **On the Command homepage, left navigation, Alerts.** 2 **Under My Alerts:** a. Hover over the alert you want to delete. b. To the right of the alert, click . c. Select **Delete Alert**. 3 **Click Delete when prompted to confirm the deletion.** You can only delete alerts that you created. Contact the admin who created a shared alert to delete it. * * * [](https://help.verkada.com/verkada-cameras/events-and-alerts/manage-alerts-across-verkada-products#manage-editors) Manage editors --------------------------------------------------------------------------------------------------------------------------------------- You can add editors to an alert you create so other admins can also view and manage the alert. Editors can view, modify, or delete the alert from the [**Manage Alerts**](https://command.verkada.com/admin/manage-alerts) page. 1 **On the Command homepage, left navigation, Alerts.** 2 **Under My Alerts:** a. Hover over the alert you want to manage editors. b. To the right of the alert, click . c. Select **Manage Editors**. d. Add or remove users or groups as needed. 3 **Click Save to confirm the changes.** Editors are **not** added as alert [recipients](https://help.verkada.com/verkada-cameras/events-and-alerts/create-alerts-across-verkada-products) by default. This means editors can not see the events on their Alerts page and will not receive notifications for alerts unless they are also added as alert recipients. * * * [](https://help.verkada.com/verkada-cameras/events-and-alerts/manage-alerts-across-verkada-products#find-events) Find events --------------------------------------------------------------------------------------------------------------------------------- The Alerts page contains more information about notifications, including date and time, notification type, site, and location. 1 **On the Command homepage, left navigation, click Alerts.** 2 **(Optional) Use the filters in the search bar to narrow down the events.** 3 **Select an event to view the associated video clip.** Historical footage and thumbnails are **only** accessible for the duration of the camera’s retention. * * * **Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=b697WsAOqW4) . Last updated 1 day ago Was this helpful? --- # Alarm Setup and Install Best Practices | Classic Alarms | Verkada Help Building materials, obstructions, distance, and general radio frequency (RF) interference are highly variable across different environments and from the time of day. As such, we highly recommend that you read and follow guidelines outlined in this article to ensure that your wireless system operates to the best of its ability. [](https://help.verkada.com/classic-alarms/hardware-installation/alarm-setup-and-install-best-practices#add-your-wireless-alarm-hub-to-verkada-command) Add your wireless alarm hub to Verkada Command ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 1 **Remove the cover from your alarm hub and plug the device into a Power over Ethernet (PoE) switch.** 2 **In Verkada Command, go to All Products > Add Devices and select a site. This will be your alarms site.** 3 **Find and enter the 12-character serial number, beginning with "DQ6", located at the bottom of the device or on the box that was provided.** 4 **Click Activate.** 5 **Once you activate your hub, follow the setup flow to configure your alarms site. If you added it to an existing alarms site, you can skip this step.** 6 **Navigate to the Alarms > Devices tab and verify that your wireless hub is reporting online and the LED on the hub is solid blue.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-5ba0bb0ffac4630c86073bf89ef8f9f8400ed828%252F1d4b6ef0d1b70d9b563f4f768ab8a8c44b249060.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=96250579&sv=2) [](https://help.verkada.com/classic-alarms/hardware-installation/alarm-setup-and-install-best-practices#add-your-wireless-sensors-to-command) Add your wireless sensors to Command --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Place your wireless sensors next to the wireless hub. **Note**: Prior to installing the sensors in their final locations, our team will verify that all of your sensors are properly communicating with your hub and reporting events to Command. ### [](https://help.verkada.com/classic-alarms/hardware-installation/alarm-setup-and-install-best-practices#add-your-wireless-sensors-by-sn) Add your wireless sensors by SN 1 **In Verkada Command, go to All Products > Devices.** 2 **At the top right, click Add Devices and select a site. This is the alarms site associated to your wireless sensor.** 3 **Find and enter the 12-character serial number, located at the bottom of the device or on the box that was provided.** 4 **Click Activate to automatically associate the sensor to the alarms site and the hub(s) in your organization.** **Note**: Wireless sensors and hubs do **not** have to exist in the same Alarms site. Sensors automatically communicate with the closest physical hub that exists in your entire organization. ### [](https://help.verkada.com/classic-alarms/hardware-installation/alarm-setup-and-install-best-practices#power-on-your-wireless-sensors) Power on your wireless sensors When the sensors are first powered on, they automatically try to join the closest hub to report their status. 1 **Pull the battery tabs from your sensor(s) to power on the device.** 2 **Initiate trigger event(s), as detailed in** [**Set Up Your Wireless Devices**](https://help.verkada.com/classic-alarms/hardware-installation/set-up-your-wireless-alarm-devices) **, for your specific sensor (door open/close, motion detected, button press, and so on).** ### [](https://help.verkada.com/classic-alarms/hardware-installation/alarm-setup-and-install-best-practices#validate-wireless-sensor-coverage) Validate wireless sensor coverage 1 **Place the hub as close to the desired location as possible, such as the center of the floor/building for maximum coverage.** 2 **The most recent sensor events are time-stamped in the Alarms site > Devices tab. You can monitor this page to ensure that sensor events and the sensor’s current signal strength are properly reported to Command.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-f7077f0ae25694ecfbcdb6e5d80f444492079ddb%252Fea9126c36651ab9d0b6a2a31207a4c4be6b64fbb.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=3d822de8&sv=2) 3 **Relocate your wireless sensors to their desired install locations and send several trigger events (door open/close, motion detected, panic button press, glass break tester, and shorting the metal contacts on the water sensor). The lowest recommended Received Signal Strength Indicator (RSSI) is -85. We recommend not allowing lower values (for example, 90, -95, and so on); this weak signal strength means that the sensors will likely drop offline and experience difficulties upgrading. The -85 RSSI provides a safer barrier to the variability in environmental changes.** 4 **If the events are reported to Command, install the sensor in its final location and send 1 more event for good measure; otherwise:** a. If no events are being received, move closer to the hub to determine if the issue is related to signal coverage. b. If you find that events are received when you move closer to the hub, perform a site walk to determine if there are any obstructions that could be dampening the signal. c. Reposition the hub for better coverage and restart the testing. d. If all else fails, you may want to consider purchasing an additional hub and license to fully cover your floor/building. [](https://help.verkada.com/classic-alarms/hardware-installation/alarm-setup-and-install-best-practices#configure-command) Configure Command ------------------------------------------------------------------------------------------------------------------------------------------------- Before you begin this configuration, verify your [alarm site settings](https://help.verkada.com/classic-alarms/configuration-and-setup/configure-classic-alarms-site-settings) and validate system operations by raising a few test alarms. ### [](https://help.verkada.com/classic-alarms/hardware-installation/alarm-setup-and-install-best-practices#put-your-alarm-site-in-test-mode) Put your Alarm site in test mode When the system is put in test mode, the system and monitoring agents still go through the alarms flow, but do **not** dispatch emergency services, unless you explicitly request it. 1 **Toggle on Enable Emergency Dispatch.** 2 **Toggle on Monitoring Test Mode.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-f0e2abc5c3f79544edaba33cf5ba7be2f5fbd95e%252Ff323e9f7a36c0e81f7b1ceffda1d356b7d62c256.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=82f82a23&sv=2) ### [](https://help.verkada.com/classic-alarms/hardware-installation/alarm-setup-and-install-best-practices#configure-the-user-call-list-and-notifications) Configure the user call list and notifications **Required**. At least 1 user with a phone number must be subscribed to receive a call from our monitoring agents. In the screenshot example, the first person listed receives a call and then the following person would be the second to be called if the first person is unavailable, and so on. Each user will receive SMS and email notifications when an alarm is raised. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-ab2767aeb2785872c71282f4ea585367e82a23a2%252F0552b338fe236bb79ba4ba5d26831050d2b3501b.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=f6687e1d&sv=2) ### [](https://help.verkada.com/classic-alarms/hardware-installation/alarm-setup-and-install-best-practices#add-wireless-or-wired-sensors-as-triggers) Add wireless or wired sensors as triggers **Note**: All added sensors are used as triggers. 1 **On the Alarm Triggers page (for Wireless Sensor Events or Wired Sensor Events), click Add Sensor.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-0ea89a7353b204b03491b1a9768397bf1b68af40%252F8e150637629d38bcad602ece79b2da0c586427ab.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=43e71646&sv=2) ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-e86b4dced2b2c572cf5f6be7d8342de9a1f00452%252F227689ec4aaa55476f700f403987def4cf85263d.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=ba95af69&sv=2) 2 **Click Editto configure additional settings, such as door contact sensors and panic buttons.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-578fa6da41764afd4c1cae020bd8736bac7a86d4%252Fda63968fdc193c9843a6b5859d98813a02cfb536.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=360dbbd6&sv=2) ### [](https://help.verkada.com/classic-alarms/hardware-installation/alarm-setup-and-install-best-practices#arm-the-site-and-raise-a-test-alarm) Arm the site and raise a test alarm 1 **Arm the alarms site from Command and monitor the Activity tab.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-548d11acec120b01eeb6c0164c0a44824ae68504%252Fb1457dd12497f7974671e7c0f645ae9734a15135.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=78f26a29&sv=2) 2 **Trigger your sensors and after the entry delay has elapsed, an alarm should be raised.** * Users on the notification list can resolve the alarm by spelling out their last name and phone number associated with their account to the monitoring agent. * Command users can also manually resolve the alarm banner or by disarming their system. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-f2edb24285afdf5840bd723ebce2ff4a17cb9862%252F1f1e00588d41095cc16a19e7f6a5fbaf3916e27f.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=afaa5b4e&sv=2) 3 **Expand the alarm-raised event to see all of the sensors that were tripped:** a. Under the alarm period, click **See Details**. In this view, you can see details about the flow of events for the raised alarm event. b. Click **See more** to expand the list of device events and include context camera footage for raise-alarm events, if configured. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-c1e4f373861c4e01aa4dafaeff5daeac1be12167%252Ffc75fb7c75709499065d83829a9107f68b4f79ae.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=ed35de44&sv=2) ### [](https://help.verkada.com/classic-alarms/hardware-installation/alarm-setup-and-install-best-practices#ensure-the-event-population) Ensure the event population Under the alarm site > **Devices** tab, ensure that all of the wireless sensors have populated at least 1 event. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-c691ee65609cacbb5c32e476751bbd2bf7035f6f%252Fb7a6c0aef5d71e3f522283469fc4d9f768e2285f.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=f4600f36&sv=2) Last updated 23 hours ago Was this helpful? --- # Configure BACnet on Air Quality Sensors | Air Quality | Verkada Help Verkada [Air Quality Sensors](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) offer your organizations a way to monitor essential indoor air quality factors, such as [CO2](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) , [CO](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) , [PM 2.5](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) , [PM 4.0](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) , [PM 10.0](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) , [AQI](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) , [TVOC](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) , and [formaldehyde](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) . The [Building Automation and Control Networks (BACnet)](https://www.ashrae.org/technical-resources/technical-faqs/question-51-what-is-bacnet) integration allows Verkada sensors to inform a building’s Heating, Ventilation, and Air Conditioning (HVAC) system about an air quality metric or any sensor reading, allowing the building HVAC to respond to these indoor air quality conditions. Verkada sensors can integrate with the Building Management System (BMS) protocol, BACnet. By integrating Verkada’s sensors with this protocol, your organization’s HVAC systems can now automatically respond to suboptimal air conditions. Learn more about [BACnet for Verkada Air Quality Sensors](https://help.verkada.com/air-quality/configuration-and-setup/bacnet-for-verkada-air-quality-sensors) . To use this integration, your building must have a Building Automation System (BAS) that is compatible with BACnet IP. We recommend that you contact your HVAC specialist to understand if your system is supported. If you are unsure or need help, contact [Verkada Support](https://www.verkada.com/contact/) . * * * [](https://help.verkada.com/air-quality/configuration-and-setup/configure-bacnet-on-air-quality-sensors#enable-bacnet-for-your-org-using-the-feature-manager) Enable BACnet for your org using the Feature Manager ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- To activate the BACnet functionality on your sensors, you first need to enable the BACnet feature for your organization. 1 **In Verkada Command, go to All Products > Admin.** 2 **Select the Privacy & Security tab.** 3 **Click Feature Manager.** 4 **Under Air Quality, find Sensor BACnet and change it from Disable to Enable.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-67ab3faa7c56358e462438be17f0b39af2845030%252F772863bf6645683a2d094823cce8a35d86ee0a53.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=a157f7bf&sv=2) * * * [](https://help.verkada.com/air-quality/configuration-and-setup/configure-bacnet-on-air-quality-sensors#enable-bacnet-on-a-verkada-sensor) Enable BACnet on a Verkada sensor --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Once the BACnet feature is enabled for your organization, you’re ready to enable it on your devices. Learn more about [BACnet for Verkada Air Quality Sensors](https://help.verkada.com/air-quality/configuration-and-setup/bacnet-for-verkada-air-quality-sensors) . 1 **In Verkada Command, go to All Products > Air Quality.** 2 **Click the sensor you want to enroll for BACnet.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-f4794300d9bd36590320402204d9f69a38aab3d9%252Fd14e46752ee887282eaccfe73c018033a70b69a2.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=8937e998&sv=2) 3 **At the top right, click the Settings icon (gear).** 4 **On the left, click BACnet. (If you don’t see the BACnet option, ensure the device is an** [**SV21**](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) **,** [**SV23**](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) **, or** [**SV25**](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) **, and** [**ensure BACnet is enabled for your organization**](https://help.verkada.com/air-quality/configuration-and-setup/bacnet-for-verkada-air-quality-sensors) **.)** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-a4b7846285cd5df0beb7381b1e37c14fa464a441%252F235117b107fa4ef83518ad92780fac4f861faf1f.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=e66db610&sv=2) a. Click the dropdown and select **Enable**. b. Assign a unique **BACnet** **Device ID** so you can identify your sensor on your BAS/BMS. The Device ID identifies the device on the BACnet network; therefore, each Verkada sensor should have a unique Device ID in the range of 0–4194302. c. Assign a **BACnet port**. The default BACnet port is **47808**, which is a commonly used UDP port for BACnet/IP, but it can also be any number in the range of 47808–47823. We recommend that the UDP port stay unchanged because the default value is mainly used. 5 **Click Apply to save your changes.** BACnet should now be enabled on the device. Anything on the BACnet server can now poll the device for properties. * * * [](https://help.verkada.com/air-quality/configuration-and-setup/configure-bacnet-on-air-quality-sensors#disable-bacnet-on-a-verkada-sensor) Disable BACnet on a Verkada sensor ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 1 **In Verkada Command, go to All Products > Air Quality.** 2 **Click the sensor you want to disable BACnet for.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-f4794300d9bd36590320402204d9f69a38aab3d9%252Fd14e46752ee887282eaccfe73c018033a70b69a2.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=8937e998&sv=2) 3 **At the top right, click the Settings icon (gear).** 4 **On the left, click BACnet. (If you don’t see the BACnet option, ensure the device is an** [**SV21**](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) **,** [**SV23**](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) **, or** [**SV25**](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) **, and** [**ensure BACnet is enabled for your organization**](https://help.verkada.com/air-quality/configuration-and-setup/bacnet-for-verkada-air-quality-sensors) **.)** a. Click the dropdown and select **Disable**. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-f12a87c05414b69aa6cb846ec344dd9014496338%252Fdaa725ff60ce4ccc85fb7b763c9431410ddc281b.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=757ca6a2&sv=2) b. Click **Apply** to save your changes. * * * [](https://help.verkada.com/air-quality/configuration-and-setup/configure-bacnet-on-air-quality-sensors#bacnet-pics) BACnet [PICS](https://www.bacnetinternational.net/catalog/manu/siemens/CM110665en_06_001.pdf) ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ ### [](https://help.verkada.com/air-quality/configuration-and-setup/configure-bacnet-on-air-quality-sensors#bacnet-standardized-device-profile-annex-l) BACnet Standardized Device Profile (Annex L) * Smart Sensor BIBB Device profile: B-SS ### [](https://help.verkada.com/air-quality/configuration-and-setup/configure-bacnet-on-air-quality-sensors#list-all-bacnet-interoperability-building-blocks-supported-annex-k) List all BACnet Interoperability Building Blocks Supported (Annex K) **Data sharing/device and network management services** * DS-RP-B * DM-DDB-B * DM-DOB-B **Segmentation Capability** * Segmented requests supported: No Window Size * Segmented responses supported: No Window Size ### [](https://help.verkada.com/air-quality/configuration-and-setup/configure-bacnet-on-air-quality-sensors#standard-object-types-supported) Standard object types supported An object type is supported if it is present in the device. **Supported Models** **Name** **Object Type** **Instance** **Units** SV23, SV25 Vape Index AnalogInput 1 No Units SV21, SV23, SV25 Temperature (C) AnalogInput 2 Degrees Celsius SV21, SV23, SV25 Humidity AnalogInput 3 % Relative Humidity SV21, SV23, SV25 CO2 AnalogInput 4 ppm SV25 Carbon Monoxide AnalogInput 5 ppm SV23, SV25 Noise AnalogInput 6 dB SV23, SV25 AQI AnalogInput 7 No Units SV23, SV25 TVOC Index AnalogInput 8 No Units SV23, SV25 PM 2.5 AnalogInput 9 μg/m^3 SV21, SV23, SV25 Tamper AnalogInput 10 No Units SV23, SV25 Motion AnalogInput 11 No Units SV25 Light AnalogInput 12 Lux SV25 Pressure AnalogInput 13 Hectopascal SV25 Formaldehyde AnalogInput 14 ppb SV23, SV25 PM 4.0 AnalogInput 15 μg/m^3 SV23, SV25 PM 10.0 AnalogInput 16 μg/m^3 SV21, SV23, SV25 Heat Index AnalogInput 17 Degrees Celsius SV21, SV23, SV25 Dew Point AnalogInput 18 Degrees Celsius SV21, SV23, SV25 Humidex AnalogInput 19 No Units SV21, SV23, SV25 Mold Risk Index AnalogInput 20 No Units SV23, SV25 Reset Viral Index AnalogInput 21 % **Device** **Object Type** **ID** **Object Name** Device: Dynamically Creatable: No Dynamically Deletable: No **Data Link Layer Options** * BACnet IP, (Annex J) **Device Address Binding** Is static device binding supported? (This is currently necessary for two-way communication with MS/TP slaves and certain other devices.) * No **Character Sets Supported** Indicating support for multiple character sets does not imply that they can all be supported simultaneously. * ISO 10646 (UTF-8) Last updated 19 hours ago Was this helpful? --- # View Air Quality Sensor Data | Air Quality | Verkada Help Verkada [Air Quality Sensors](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) have varied readings that allow you to gain more insight into your building or monitor areas where video monitoring is not allowed. [](https://help.verkada.com/air-quality/sensor-data/view-air-quality-sensor-data#sensor-data-by-model) Sensor data by model -------------------------------------------------------------------------------------------------------------------------------- The data available depends on your sensor model. See [Sensor Readings](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) for more information about the breakdown of the different sensor readings per model. ### [](https://help.verkada.com/air-quality/sensor-data/view-air-quality-sensor-data#sv21) [SV21](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) Sensor Reading Data Output **Temperature** Room temperature **Humidity** Room humidity **Heat Index** A combined index that represents what the temperature feels like to the human body when relative humidity is combined with the temperature **Humidex** Humidex measures how hot we feel in hot, humid weather. **Mold Risk Index** The Mold Risk Index assesses the likelihood of mold growth in confined, unventilated spaces, based on temperature and humidity levels. **Dew Point** The dew point is the temperature to which air must be cooled, at constant pressure, for the air to reach 100% relative humidity, meaning the air becomes saturated with water vapor. **Carbon Dioxide** Concentration of CO2 gas, measured in ppm **Tamper** Indicates if the sensor is being tampered with ### [](https://help.verkada.com/air-quality/sensor-data/view-air-quality-sensor-data#sv23) [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) Includes all data output of the [SV21](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , plus the following. Sensor Reading Data Output **Vape Index** A combined index that represents the likelihood that someone is vaping in the vicinity of the sensor **Noise Level** Noise level in the room, measured in dB **Air Quality Index** U.S. Air Quality Index, derived from multiple sensors **TVOC** Volatile organic compound level in the air measured in an index **PM 2.5** **PM 4.0** **PM 10.0** Fine particulate level measured in microgrammes per cubic meter **Motion** Motion detected by the Passive Infrared (PIR) sensor **RESET® Viral Index** The RESET® Viral Index is an index designed to assess the likelihood of airborne virus transmission in indoor spaces. ### [](https://help.verkada.com/air-quality/sensor-data/view-air-quality-sensor-data#sv25) [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) Includes all data output of the [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) , plus the following. Sensor Reading Data Output **Carbon Monoxide** Concentration of Carbon Monoxide gas, measured in ppm **Formaldehyde (CH2O)** Concentration of Formaldehyde (CH2O) gas, measured in ppb **Barometric Pressure** Measurement of air pressure in the atmosphere ### [](https://help.verkada.com/air-quality/sensor-data/view-air-quality-sensor-data#sv11) [SV11](https://www.verkada.com/sensors/sv11/) Verkada’s first-generation sensor outputs data on the following readings. Sensor Reading Data Output **Vape Index** A combined index that represents the likelihood that someone is vaping in the vicinity of the sensor **Temperature** Room temperature **Humidity** Room humidity **Heat Index** A combined index that represents what the temperature feels like to the human body when relative humidity is combined with the temperature **Humidex** Humidex measures how hot we feel in hot, humid weather. **Mold Risk Index** The Mold Risk Index assesses the likelihood of mold growth in confined, unventilated spaces, based on temperature and humidity levels. **Dew Point** The dew point is the temperature to which air must be cooled, at constant pressure, for the air to reach 100% relative humidity, meaning the air becomes saturated with water vapor. **Noise Level** Noise level in the room, measured in dB **Air Quality Index** U.S. Air Quality Index, derived from multiple sensors **TVOC** Volatile organic compound level in the air, measured in parts per million **PM 2.5** **PM 4.0** **PM 10.0** Fine particulate level measured in micrograms per cubic meter **Tamper** Indicates if the sensor is being tampered with **Motion** Motion detected by the PIR sensor [](https://help.verkada.com/air-quality/sensor-data/view-air-quality-sensor-data#view-details-about-your-sensor) View details about your sensor ---------------------------------------------------------------------------------------------------------------------------------------------------- 1 **In Verkada Command, go to All Products > Air Quality.** 2 **Click a sensor device to go to the sensor’s Details page.** 3 **Select the sensor reading you want to see. Then select the time range for which you would like to view. By default, you should see the output of Today for the selected reading.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-4033bb26fa1ecaed455f61e83e36bc715b4fcd8e%252Fff989ea7e66a672094e4684f47eb2ba324e3bae7.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=2339c828&sv=2) 4 **Select which reading you want to view. For a detailed view, select from the list. Learn more about** [**sensor readings**](https://help.verkada.com/air-quality/sensor-data/air-quality-sensor-readings) **.** As you scrub through the graph, the side readings also follow the time frame you hover over. ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-032d05dd20c15e103c2340c5094fa0489ee0e796%252F580c397ba66bd34a9fc284b3353b2733dec0953d.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=77b483bc&sv=2) When you select a reading from the list on the left, the **Alerts** section below filters alerts for the selected reading. You can view all alerts by changing the filter on the right to **All Sensors**. [](https://help.verkada.com/air-quality/sensor-data/view-air-quality-sensor-data#select-a-time-range-and-custom-date-range) Select a time range and custom date range -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 1 **In Verkada Command, go to All Products > Air Quality.** 2 **Select a sensor to customize the time range.** 3 **Above the graph, select the dropdown menu and choose the date range of preset options (This Hour, This Week, This Month, This Year) to understand your device’s environment over a range of time. To return to the live sensor readings, at the top of the list, select Live.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-0ffe28ad7eff0a2d7e76a2655767abe6812a0f9b%252Fe169867e9a71378b19580a82b5f6a6449e87955a.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=86ebeaea&sv=2) 4 **(Optional) Specify a custom or present range using one of these options:** * On the dropdown menu above the graph, select **Custom** to specify a range of time from the calendar, and click **Apply**. (As your date range increases, the resolution of your chart decreases.) ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-87595f2419c8b2ffecf30255c7aa47a4bfe4bffe%252Faf0166e2ee88bee6d1ddaf49f3748a4eb1372d42.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=a6928133&sv=2) * Click and drag the cursor over the desired time frame. This zooms in on the data. (Click **Reset** to zoom out to the original time frame.) This can be useful in understanding how long-term and macro changes in your environment, such as seasons, can affect air quality or cleaning habits. [](https://help.verkada.com/air-quality/sensor-data/view-air-quality-sensor-data#data-retention-and-resolution) Data retention and resolution -------------------------------------------------------------------------------------------------------------------------------------------------- The Verkada sensors store sensor data for 365 days. After the 365th day, the oldest sensor data is overwritten with the newest data. * For the SV11, data is stored at a **1-second** resolution for **30 days**. For **days 31–365**, data is stored at a **5-minute** resolution. * For the SV20 series, data is stored at a **5-second** resolution for **30 days**. For days **31–365**, data is stored at a **5-minute** resolution. ### [](https://help.verkada.com/air-quality/sensor-data/view-air-quality-sensor-data#export-sensor-data-and-alerts) Export sensor data and alerts 1 **In Verkada Command, go to All Products > Air Quality.** 2 **Select a sensor.** 3 **On the toolbar, click the Download as CSV icon to export sensor data or sensor alert data via a comma-separated value (CSV) file.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-6a2463010b5f4a409c4210735fdddf07d72383c7%252Fa9f92bacc6f19fa3346c4ad5f6137401f6082761.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=30881289&sv=2) 4 **On Download CSV** a. Select **Sensor Data** or **Alerts**, depending on what type of data you want to download. b. Check the box next to the sensor readings you want to download. By default, the temperature is Fahrenheit. You can choose Celsius, if preferred. c. Set the date range (**Last 5 Minutes**, **Last Hour**, **Last Day**, **Last Week**, **Last Month**, **Last Year**, **Custom**) for the report. d. Choose the resolution (**1 Minute**, **5 Minutes**, **30 Minutes**, **1 Hour**, **1 Day**) and then click **Export**. ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3057705728-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJtgmyWYlTEX9DpjvBwTL%252Fuploads%252Fgit-blob-c27ddcad9cbf94654665e3823b205d403fa98326%252F62554bfee349f2b293a95f93f72cc9ddcd033569.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=45ce76b1&sv=2) For sensor data, you can export data at various predefined resolutions (5s, 1min, 5min, 30min, 1hr, 1day). The table shows the maximum resolution that can be exported for a given time range. **Time Range** **Maximum Resolution** 1 hour 5 seconds 1–24 hours 1 minute 24 hours–30 days 5 minutes 30–180 days 30 minutes 180–365 days 1 hour Once you click **Export**, Command sends an email with the CSV attached. This process can take up to 10 minutes, depending on the amount of data being requested. Last updated 19 hours ago Was this helpful? --- # Set Up the BC82 Alarm Console | Classic Alarms | Verkada Help The Verkada BC82 alarm console is used to arm/disarm alarm sites, with additional functionality, including a digital panic button, device status page, event feed, integrated camera, microphone for remote monitoring and talk-down from Verkada Command, 90db siren, and a built-in wireless hub to connect wireless sensors. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-0372668182addf3419cd52b426b155e3edc10352%252Fc3519f48467a6b01020bf991acb770567750beb8.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=babe8378&sv=2) [](https://help.verkada.com/classic-alarms/hardware-installation/set-up-the-bc82-alarm-console#before-you-begin) **Before you begin** ------------------------------------------------------------------------------------------------------------------------------------------ Before you begin the setup, review the requirements and recommendations. ### [](https://help.verkada.com/classic-alarms/hardware-installation/set-up-the-bc82-alarm-console#requirements) Requirements The BC82 requires 802.3at for power and network connectivity and includes a mounting bracket and the associated mounting hardware. **Note**: The alarm console must be mounted in portrait mode/vertically. ### [](https://help.verkada.com/classic-alarms/hardware-installation/set-up-the-bc82-alarm-console#recommendation) Recommendation Once you take the alarm console out of the box, we recommend that you stage the console and test its functionality before mounting: 1 **Attach an Ethernet cable to the BC82 located on the back of the console.** 2 **Connect the Ethernet cable to an open port on a Power over Ethernet (PoE) (802.3at) switch.** **Note:** When you first plug in the BC82, it may take a few minutes to build enough charge to boot. After a few minutes of the device being plugged in, press the power button located on the back to turn the console on. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-e27f1f6de9450fe7f3825da5c9b1f78d2f150aa2%252Fb9f5c39400bd000f537ec43ce27468dbad233b08.jpg%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=e5291d76&sv=2) [](https://help.verkada.com/classic-alarms/hardware-installation/set-up-the-bc82-alarm-console#add-the-device-to-command) Add the device to Command -------------------------------------------------------------------------------------------------------------------------------------------------------- 1 **Once the console powers on, using the serial number located on the box or on the console display, add the device to Command via the web interface.** 2 **In Command, ensure the console is added to the appropriate alarm site.** 3 **If the console has network connectivity to Verkada servers and the serial number has been added to Command, you should be redirected to this keypad interface:** ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-c9efe960e45ad5500b7c13d49482c048ec2ca93a%252Fcc986a939aa7e4fdb3f715998fc101f2f8b0ab3c.jpg%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=5698ec7f&sv=2) [](https://help.verkada.com/classic-alarms/hardware-installation/set-up-the-bc82-alarm-console#test-keypad-features) Test keypad features ---------------------------------------------------------------------------------------------------------------------------------------------- Prior to mounting to its final location, test the keypad features to ensure everything is working as expected: ### [](https://help.verkada.com/classic-alarms/hardware-installation/set-up-the-bc82-alarm-console#home-screen) Home screen The home screen shows status events of critical issues (yellow box) and sensors with activity (blue box). You can touch either box to pull up the associated devices. ### [](https://help.verkada.com/classic-alarms/hardware-installation/set-up-the-bc82-alarm-console#camera-page) Camera page From the home screen, swipe left to see the camera view. From here, you can select cameras in the site and view them. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-9d0f5c3d10d2e7d183609426bc33c228ed69865f%252F580443c76f044a7ea5aa40be6c382569d6e76d73.gif%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=2aa9c109&sv=2) ### [](https://help.verkada.com/classic-alarms/hardware-installation/set-up-the-bc82-alarm-console#devices-page) Devices page From the home screen, swipe right to go to the devices page. From here, you can see all devices and the last event that exists in the alarm site. This should mirror the **Devices** tab in the Alarms site in Command. ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-98bd09aa6553431dbb93b47be8fd65df7885796d%252Fca243c612d6fae8843d5cfb715c3c499062dccbc.gif%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=fe9085eb&sv=2) ### [](https://help.verkada.com/classic-alarms/hardware-installation/set-up-the-bc82-alarm-console#arm-tab) Arm tab On the **Arm** tab, you can test arm/disarm functionality with your [configured key codes](https://help.verkada.com/classic-alarms/configuration-and-setup/configure-classic-alarms-site-settings) in Command. ### [](https://help.verkada.com/classic-alarms/hardware-installation/set-up-the-bc82-alarm-console#two-way-talk-down-and-listening-in) Two-Way Talk-Down and Listening In **Recommendation**. This test is best performed with two people in separate rooms. Please have one individual in front of the console and the other on the Command web interface. On the Command UI, the Alarm console should display a live feed. * To test the listen-in feature, unmute the alarm console, where you should hear the sounds that the console is picking up. * To test two-way talk-down, initiate a video call by pressing the **Call** button in the video feed of the console. **Note**: From Command, the Alarm console includes an integrated camera and microphone for remote monitoring. A banner at the top of the Alarm console screen indicates when video or audio is being viewed or recorded. You can also choose to plug in a 3.5-mm audio jack to the console for broader/louder coverage for talk-down communications, including outdoor speakers. **Note:** To use the 3.5-mm audio jack, you need to use a speaker amp to increase the volume from the console. ### [](https://help.verkada.com/classic-alarms/hardware-installation/set-up-the-bc82-alarm-console#panic-button) Panic button Press the digital panic button to test an immediate alarm. You can disarm it with your configured key codes or via the Command web interface. [](https://help.verkada.com/classic-alarms/hardware-installation/set-up-the-bc82-alarm-console#add-wireless-sensors) Add wireless sensors ---------------------------------------------------------------------------------------------------------------------------------------------- You have two options on how to add new wireless sensors: * Via the main devices page and enter the serial number * On the Alarms devices page, click the plus (**+**) symbol > **Add wireless sensors**. Once events occur or on the first boot of the sensor, you should see the connection from the BC82 to the sensor. **Note:** If there are multiple hubs in the area (for example, BC82 or BH61), the sensors will join to the closest hub device (hub with the best signal strength). After testing these features, you can proceed to mount the alarm console in its final location using the mounting instructions included in the box. Last updated 23 hours ago Was this helpful? --- # Set Up and Install Wireless Sensors | Classic Alarms | Verkada Help Building materials, obstructions, distance, and general radio frequency (RF) interference are highly variable across different environments and from time of day. As a result, we highly suggest you adhere to the following guidelines to ensure that your wireless system operates to the best of its ability. [](https://help.verkada.com/classic-alarms/configuration-and-setup/set-up-and-install-wireless-sensors#add-your-wireless-hub-to-verkada-command) Add your wireless hub to Verkada Command ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 1 **Remove the cover from your alarm hub and plug the device into a Power over Ethernet (PoE) switch.** 2 **In Verkada Command, go to All Products > Device. Alternatively, you can go to All Products > Add Devices (and skip step 3).** 3 **Select your wireless hub.** 4 **At the top, click Add Devices. Enter the 12-character serial number located on the sensor or on the box that was provided. Alternatively, you can scan the QR code.** 5 **Once you add your wireless hub, it is assigned to the Unassigned Devices site. Follow the setup flow to configure your device name, site, and location.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-5ee2c9062ec096db846b01bafe759090944cef7b%252Fde969f1ac67b95a95ea4b875fb9397e9c69d64f9.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=af1adc1f&sv=2) 6 **Go to the Alarms Devices tab and verify that your wireless hub is reporting online and the LED on the hub is solid blue.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-04ce43dbedaa9232ce2bbc33e66c891fdc1fb003%252F9d5df4044057f4e49e38913cbfffac45a81c4855.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=fd194c5f&sv=2) [](https://help.verkada.com/classic-alarms/configuration-and-setup/set-up-and-install-wireless-sensors#add-your-wireless-sensors-to-verkada-command) Add your wireless sensors to Verkada Command ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Place your wireless sensors right next to the wireless hub. At Verkada, we verify that all of your sensors are properly communicating with your hub and reporting events to Command before installing the sensors in their final locations. 1 **In Verkada Command, go to All Products > Device > Add Devices. Alternatively, you can go to All Products > Add Devices.** 2 **Enter the 12-character serial number located on the sensor or on the box that was provided and select Add Device.** ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-51ad16b55259110e056452fdf1197d6b95fb98e7%252F158a15242e886891b3a147bce7c78cc097e7895b.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=b5f42f08&sv=2) 3 **Once you add your wireless hub, it is assigned to the Unassigned Devices site. Follow the setup flow to configure your device name, site, and location.** ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-84236f817dc6958938b8fb9b4ceb852988424599%252F59a443dc74b6b13798d98e7df9cd063587459b46.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=878a8d4d&sv=2) [](https://help.verkada.com/classic-alarms/configuration-and-setup/set-up-and-install-wireless-sensors#power-on-your-wireless-sensors) Power on your wireless sensors -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- When the sensors are first powered on, they automatically try to join the closest hub. 1 **Pull the battery tabs from your sensor(s) to power on the device. The sensors should automatically connect to the closest hub and appear online in Command. If not, show that they are connected to a hub; perform these steps:** a. Power cycle the sensor by completely removing the batteries and re-adding the batteries to the sensor. b. Initiate trigger event(s) as detailed in the [Wireless Deep Dive](https://help.verkada.com/classic-alarms/hardware-installation/set-up-your-wireless-alarm-devices) guide above for your particular sensor (door open/close, motion detected, button press, tamper, and so on.) 2 **Once the sensor(s) have communicated with a hub, the sensors show under their respective hub that they are connected to. From there, you can get/set the following information:** * Set the name of the sensor * Display the sensor type * Display the last event * Sensor serial number * Battery level * Signal strength * Attaching nearby camera(s) to the sensor * Configure the sensor ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-6540d883b7c323142926e1b889dcde88d7fed6c8%252F38efcc6e80046d2222efdf155405de8b1b850732.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=edff80a6&sv=2) [](https://help.verkada.com/classic-alarms/configuration-and-setup/set-up-and-install-wireless-sensors#validate-wireless-sensor-coverage) Validate wireless sensor coverage -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- You should place the hub as close to the desired location as possible, such as the center of the floor/building for maximum coverage. * The most recent sensor events are time-stamped in the Alarms site > **Devices** tab. You can monitor this page to ensure that sensor events are being reported to Command and the sensor’s current signal strength. * Relocate your wireless sensors to their desired install locations and send several trigger events (door open/close, motion detected, panic button press, glass break tester, and shorting the metal contacts on the water sensor). * Received Signal Strength Indicator (RSSI) values should be greater than –80 (for example, –75, –70, and so on) to account for variability in each environment as well as ensure there are no offline events for your devices once fully installed. When signal strength is confirmed, you can install the sensor in its final location and send one more event for good measure, otherwise: * If no events are being received, move closer to the hub to determine if the issue is related to signal coverage. * If you find that events are being received when you move closer to the hub, perform a site walk to determine if any obstructions could be dampening the signal. (walls, metal frames, windows, and so on). * You can also choose to reposition the hub for better coverage and restart the testing. * If the above fails, you may want to consider purchasing an additional hub to fully cover your floor/building. Last updated 23 hours ago Was this helpful? --- # Configure Camera Alarm Trigger Events | Classic Alarms | Verkada Help Verkada’s camera alarm triggers provide additional information to the monitoring agent to determine if the event is a threat to a person or property. You can also get [alerts](https://help.verkada.com/classic-alarms/events-and-alerts/configure-alarms-event-alerts) based on the alarm triggers configured. Vehicle detection events are **not video-verified** and will automatically raise an alarm. For more information on the types of alarm triggers see below: * [Person detection](https://help.verkada.com/classic-alarms/events-and-alerts/configure-camera-alarm-trigger-events#h_0f8f2047f8) * [Line crossing](https://help.verkada.com/classic-alarms/events-and-alerts/configure-camera-alarm-trigger-events#h_71ccaf8225) * [Loitering](https://help.verkada.com/classic-alarms/events-and-alerts/configure-camera-alarm-trigger-events#h_f4fc8818d9) [](https://help.verkada.com/classic-alarms/events-and-alerts/configure-camera-alarm-trigger-events#when-should-a-detection-occur) When should a detection occur? --------------------------------------------------------------------------------------------------------------------------------------------------------------------- When a Verkada camera detects an object, green bounding boxes appear over the detected object(s). You can see these bounding boxes when scrubbing through a camera’s [people and vehicle motion search](https://help.verkada.com/verkada-cameras/analytics-and-detection/people-and-vehicle-motion-search) or scrubbing through a camera’s historical video. Detection is determined when the center bottom of a person’s bounding box crosses a line or sits inside a loitering region (in the majority of cases, it is a person’s feet). ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-4af1dc445f323aa34ddcfc90e253e3f8489c610d%252Ff67bf5a923d65ebec1716839c6cbda6a2a32cda9.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=94a5ef66&sv=2) Trigger Point Trigger Point Use line crossing and loitering detection instead of person detection when available. Loitering detection and line crossing are only available on the CF81 and third-generation or newer cameras (models that end in "2" or higher), except the CP52. [](https://help.verkada.com/classic-alarms/events-and-alerts/configure-camera-alarm-trigger-events#configure-alarm-triggers) Configure alarm triggers ---------------------------------------------------------------------------------------------------------------------------------------------------------- 1 **In Verkada Command, go to All Products > Alarms.** 2 **Select a site, at the top left, click Settings.** 3 **Under Settings, go to Alarm Triggers.** 4 **On Camera Events:** a. Click **Select Cameras.** b. Select a camera to configure. c. Configure the trigger type(s) as needed. d. Click **Done.** 5 **A trigger badge appears on the camera to indicate which trigger type has been enabled.** 6 **(Optional) Repeat step 4 on other cameras as needed.** 7 **Click Done when finished.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-12778901c56cb48a7c099e89d83efe4a2099c6d5%252Fbdd9ba55dcedf8371e29e9946c048b5eca356ffd.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=186652e3&sv=2) [](https://help.verkada.com/classic-alarms/events-and-alerts/configure-camera-alarm-trigger-events#alarm-triggers) Alarm triggers -------------------------------------------------------------------------------------------------------------------------------------- ### [](https://help.verkada.com/classic-alarms/events-and-alerts/configure-camera-alarm-trigger-events#person-detection) Person detection Person detection is determined whenever any part of a person’s bounding box intersects with the configured region of interest. ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-0229492c11b75e418fe1b9fd7a605b6109d0f9a0%252F8a96c77c20687c749674a427e63ea46eaa0e9e87.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=a1a9992a&sv=2) ### [](https://help.verkada.com/classic-alarms/events-and-alerts/configure-camera-alarm-trigger-events#line-crossing-recommended) Line Crossing (recommended) Line crossing provides more control and granularity in a trigger by allowing you to define a unidirectional or bidirectional line that a person has to cross before detection occurs. You can define a maximum of 4 lines and choose the direction you expect people or vehicles to cross. ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-ecb2cdf1e8d4b164d80d58630bbbe35d72d391d4%252F336562a42cbe236201a6fd038881003f353163c0.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=cef57f92&sv=2) ### [](https://help.verkada.com/classic-alarms/events-and-alerts/configure-camera-alarm-trigger-events#loitering-detection) Loitering detection Loitering detection allows you to define a region with a freeform polygon and define how long a person has to stay in that region before detection occurs. Define up to 4 freeform polygon regions and define how long a person has to stay in that region before detection occurs. #### [](https://help.verkada.com/classic-alarms/events-and-alerts/configure-camera-alarm-trigger-events#how-it-works) How it works 1 **Once the person’s trigger point intersects the loitering region, the timer begins.** 2 **If the trigger point remains in this region for the configured time (one minute default) a detection event occurs.** 3 **If the person’s trigger point briefly exits and re-enters the loitering region within 4 seconds, the counter continues.** 4 **If the camera loses track of an individual (for example, walking out of frame) or the trigger point is outside the loitering region for more than 4 seconds, the counter resets.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-63ff6d488d8cf0fcaa8968405b80b25792ed4e8c%252F7897160efa8b9ec66bf5e3659cb0d73f13f3c6ca.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=1009a4b9&sv=2) Last updated 1 day ago Was this helpful? --- # Configure Alarms Event Alerts | Classic Alarms | Verkada Help You can enable alerts for a variety of Alarms events, depending on your configuration needs. For more information about the Alarms event types see [below](https://help.verkada.com/classic-alarms/events-and-alerts/configure-alarms-event-alerts#h_1cfb1d78c7) . [](https://help.verkada.com/classic-alarms/events-and-alerts/configure-alarms-event-alerts#configure-alarms-event-alerts) Configure Alarms event alerts ------------------------------------------------------------------------------------------------------------------------------------------------------------ ### [](https://help.verkada.com/classic-alarms/events-and-alerts/configure-alarms-event-alerts#create-alert-greater-than-events) Create Alert > Events 1 **Log in to Verkada Command.** 2 **On the Command homepage, left navigation, click Alerts .** 3 **On the Alerts page, next to My Alerts, click .** 4 **On Select Event, select the Alarms product type.** 5 **Search for or select an event to configure.** 6 **(Optional) Some event types are general and have more specific options once you select them. If prompted, complete any additional configuration steps then click Next.** 7 **Select your devices/sites, based on the alert type you can configure events to be device-specific, site-specific, or all devices.** * When you select **Sites** or **All Devices**, new devices added after alert creation will automatically generate alerts. Click **Done** to continue. 8 **(Optional) Some event types have additional setup steps. If that is the case, click the additional steps and follow the prompts in the configuration window.** 9 **Click Done and continue with the alert** [**recipients**](https://help.verkada.com/classic-alarms/events-and-alerts/configure-alarms-event-alerts#h_0b37105bb2) **.** **Note**: Wired sensors are not currently supported as individual selectable devices, but you can select **Sites** or **All Devices** to configure alerts for them. ### [](https://help.verkada.com/classic-alarms/events-and-alerts/configure-alarms-event-alerts#create-alert-greater-than-recipients) Create Alert > Recipients 1 **On Recipients, you can search for or select other Command users individually or you can assign the alert to a group.** 2 **Select the dropdown menu next to a user or group to choose their notification method(s). Recipients can be notified either via a push notification, SMS, or email.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-a30e5c666efe865b169b36f277c2ab798ad76c5d%252F3a9609d9912905edd0f35abfff403a95e0b820c8.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=4d04bdcf&sv=2) 3 **(Optional) By default, you will be added to the alert created. To remove yourself, select the dropdown menu and click Delete.** 4 **Click Done and continue with the alert** [**notification schedule**](https://help.verkada.com/classic-alarms/events-and-alerts/configure-alarms-event-alerts#h_1133acf090) **.** **Note:** Any recipient added to this alert will see it appear under the **Shared Alerts** section of their **Alerts** page. ### [](https://help.verkada.com/classic-alarms/events-and-alerts/configure-alarms-event-alerts#create-alert-greater-than-notification-schedule) Create Alert > Notification Schedule 1 **On Notification Schedule, you must specify what days and times you want alerts to be sent. By default, events are generated 24/7.** ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-b9042c786a9dd12580abefdd20f412fe59cbac5e%252F7b61969c185d482c85ec3b7f15a687d75aee8d13.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=5dbfda6f&sv=2) 2 **Click Done and continue with the alert** [**device actions**](https://help.verkada.com/classic-alarms/events-and-alerts/configure-alarms-event-alerts#h_1e427ac1c0) **or** [**finish the alert**](https://help.verkada.com/classic-alarms/events-and-alerts/configure-alarms-event-alerts#h_06c9e92cba) **.** ### [](https://help.verkada.com/classic-alarms/events-and-alerts/configure-alarms-event-alerts#create-alert-greater-than-device-action) Create Alert > Device Action In addition to notifying individuals, you can configure your horn speaker to play when an alert is triggered. These alerts can be text-to-speech or an uploaded MP3 file. 1 **On Device Action, select the horn speaker(s) you want to play your message.** 2 **Select your device’s notification preference (Text to Speech or Audio File).** a. For **Text to Speech,** enter the desired message up to 200 characters. b. For **Audio File,** drag and drop the file or click **choose a file** to upload your audio clip. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-6eebd070cac52d81c895573628cb7b21ba245804%252Fbd7aa4597a411933461874e312ac1e72683f4dab.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=1296423c&sv=2) 3 **Click Done and continue with** [**finish the alert**](https://help.verkada.com/classic-alarms/events-and-alerts/configure-alarms-event-alerts#h_06c9e92cba) **.** ### [](https://help.verkada.com/classic-alarms/events-and-alerts/configure-alarms-event-alerts#finish-the-alert) Finish the alert 1 **Click Next on the bottom right of the configuration window once you have configured all the desired alert settings.** 2 **Enter a descriptive name for the alert.** 3 **Click Done and you will start to receive alerts.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-75fcc30636d14fdd34cc9e376db710c1542f4ef2%252F943420792c6bfe40aee47eab735038e52669e4ac.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=cab60c29&sv=2) ### [](https://help.verkada.com/classic-alarms/events-and-alerts/configure-alarms-event-alerts#understand-the-various-alarms-event-types) Understand the various Alarms event types **Alert Type** **Description** **Online/Offline** Alarms device changed state to online or offline. **Alarm Site Status** Alarm site changed state to armed or disarmed. **Cellular Module Status** Selected cellular backup is in one or many of the following states **Active:** currently in use ​**On Standby:** Connected to the cellular network and not in use **Disconnected:** Cell backup was disconnected from the device **Offline:** Unable to connect to the cellular network **Sensor Events** Receive an alert when one of the following events is detected: Door Opened Door Held Opened Glass Break Detected Motion Detected Panic Button Pressed Water Detected **Device Power Status** A wireless sensor battery state changed. **Tamper** Interference or manipulation detected on an Alarms device. Last updated 23 hours ago Was this helpful? --- # Troubleshoot Inrush Current Issues | Classic Alarms | Verkada Help [](https://help.verkada.com/classic-alarms/troubleshooting/troubleshoot-inrush-current-issues#before-you-begin) Before you begin ------------------------------------------------------------------------------------------------------------------------------------- To help you troubleshoot inrush issues and what causes them, familiarize yourself with these terms: * **Capacitance**—The capability of a material to store electrical charge. Capacitors are the physical component that adds capacitance in electrical circuits. * **Inrush current**—Also called _input surge current_ or _switch-on surge_—the maximal instantaneous input current that is drawn by an electric device when it is first turned on. Generally speaking, the **higher** the capacitance of a device, the **higher** the inrush current draw that an individual device will have. [](https://help.verkada.com/classic-alarms/troubleshooting/troubleshoot-inrush-current-issues#understand-how-an-inrush-current-causes-problems) Understand how an inrush current causes problems ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- The image shown illustrates a large current draw when a device is first powered on that decreases into a steady-state current. The peak and the inrush current magnitude depends on the **number** and **type** of capacitors that are in an electrical circuit. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-45284fdda0392732aba44b13cbd4619b992feaac%252F6f38678e6b7200db2982f779d42be83321e7cf04.jpg%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=9f64efcb&sv=2) What is Inrush Current? What is Inrush Current? The image shown below is an example of 2 different motion sensors that have different capacitance levels despite the data sheet reporting similar power requirements. **Motion Sensor** **Power** **Example** **Honeywell IS335 (2 Capacitors)** 9–15VDC @ 12mA ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-c829dabf304a351c60db2ff8523c67e93e153b29%252F6bdad259cc8a7d026434c14a568b1a7153fe829b.png%3Falt%3Dmedia&width=300&dpr=4&quality=100&sign=3af71b0c&sv=2) **Honeywell DT7235T (10+ Capacitors)** 7.5–16VDC @ 24mA ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-c78667e449e90eaee693b176bd1f2b207fb2ce3b%252Fca6ff4025bcc6376edcac3e50986c767ee3ca490.png%3Falt%3Dmedia&width=300&dpr=4&quality=100&sign=5de0994d&sv=2) The Honeywell DT7235T has a **significantly higher capacitance and inrush current** compared to the Honeywell IS335 due to the number and size of capacitors needed to support its DUAL TEC functionality. [](https://help.verkada.com/classic-alarms/troubleshooting/troubleshoot-inrush-current-issues#how-to-identify-capacitance-issues) How to identify capacitance issues ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Generally speaking, capacitance issues present in 1 of 2 ways, as shown in the example of the [BP41 Alarm Panel](https://help.verkada.com/classic-alarms/hardware-installation/configure-and-wire-inputsoutputs-on-the-bp41) . * **Immediately after wiring in a high capacitance device**. The inrush current of the device is so high that it causes a **brownout** where the panels **lose power** due to an internal protective mechanism to protect the system from a short. * **After a power cycle, reboot, or firmware upgrade on the BP41**. The combined power requirements of system boot and inrush current of **all devices** **at once** exceed what can be supplied by the panel, again, causing a brownout where the panel loses power. This issue is not seen during the initial install because: * The panel is already in a fully booted state. * External sensors are added and wired in one-by-one, and each individual component is given enough time to charge its capacitors. * **There is an "AUX Output Failure" warning on the device and "AUX power disabled" warning shown in the alarm site.** The AUX is disabled to avoid the inrush issue from the 4-wire sensors and allow the system continue to boot and remain online. ​ ### [](https://help.verkada.com/classic-alarms/troubleshooting/troubleshoot-inrush-current-issues#what-to-expect) What to expect This can cause the panel to: * Fail to boot up completely until the sensors are removed from power OR * Introduce delays in boot up until the capacitors on the devices are charged enough to bypass the internal protective mechanism. The panel typically has its Panel Status LED (OFF) and the Power LED (ON). ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-8928842c733ea1f6d5102dc7a8931f2b2a4c220d%252F52a9934b430d667c5e7a2be76a294b88c49a6e04.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=4c56c34b&sv=2) [](https://help.verkada.com/classic-alarms/troubleshooting/troubleshoot-inrush-current-issues#how-to-solve-problems-with-inrush-current) How to solve problems with inrush current --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 1 **We recommend wiring a 100Ω resistor inline to the power of each of the sensors to help slow down current draw from the sensors and avoid a brownout.** ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-34047fe4ab9c8f3592bb588bfe9d7943b4fb0e8c%252Fbadd9f117ddde9dda8ae5d10d9f7c9b32f4b0630.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=d938ffbe&sv=2) 2 **After wiring in the resistors, confirm system operation by power cycling the panel and to ensure that the panel boots up properly.** Last updated 1 day ago Was this helpful? --- # Configure Classic Alarms Site Settings | Classic Alarms | Verkada Help When you create a Classic Alarms site in Verkada Command, you need to go through a few steps to configure settings for the site. You can modify these settings at any time: 1 **In Verkada Command, go to All Products > Alarms.** 2 **Select the site that you want to configure.** 3 **Configure your alarm site using the** [**Settings**](https://help.verkada.com/classic-alarms/configuration-and-setup/configure-classic-alarms-site-settings#h_7a41c203f0) [**options**](https://help.verkada.com/classic-alarms/configuration-and-setup/configure-classic-alarms-site-settings#h_7a41c203f0) **below.** [](https://help.verkada.com/classic-alarms/configuration-and-setup/configure-classic-alarms-site-settings#alarm-settings) Alarm settings --------------------------------------------------------------------------------------------------------------------------------------------- Click to expand each option below to learn more about settings options. General[](https://help.verkada.com/classic-alarms/configuration-and-setup/configure-classic-alarms-site-settings#general) On the **General** page, specify the physical location of your Alarms site. Ensure this address is accurate and specific. Verkada uses this address in case emergency services need to be dispatched. Each unique address requires one Alarms license. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-b4f727d79325a15b736d118445e805ae04b2571f%252Fd50a1cde3e195a117b84644e3a42eb2c4aece557.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=d4b30634&sv=2) Alarm triggers[](https://help.verkada.com/classic-alarms/configuration-and-setup/configure-classic-alarms-site-settings#alarm-triggers) You can choose which events should trigger an alarm: cameras, sensor inputs, and doors. The events that exist in this Alarms site can be selected as _alarm triggers_. This means that when the site is armed, any of the following events can trip the alarm. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-0cf5b1bb50feb06f83a23adebc3a69fbc7a7328b%252Ffcdd133335b45b9644986ba4138a71d69cb44113.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=56455d21&sv=2) **When alarm devices go offline** By default, if any alarm devices go offline for more than five minutes while the system is in an armed state, it automatically raises the alarm and sends an offline notification to the users on the contact list. If any alarm devices go offline while the system is in an _unarmed_ state: * It records the offline event and sends a notification to the users on the contact list, but does not raise an alarm. * It does not raise an alarm when the system is armed later, unless the Alarm device comes online and goes offline for more than five minutes. **Change default behavior of offline events** To change the default behavior of offline events: Navigate to **Settings** > **Offline Events**. Select **Raise alarm**, **Notify only**, or **Do nothing** in the event a selected device goes offline. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-7d12439b35067b9a3cdb5c37dbab38d6b5094ba3%252F927c3c4f0ff3524e42e6b62fc56bb653e8b98692.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=b6a81b8e&sv=2) Cameras[](https://help.verkada.com/classic-alarms/configuration-and-setup/configure-classic-alarms-site-settings#cameras) To enable a camera as an alarm trigger: On **Select Cameras**, select the camera for person detection. Once selected, anytime the system is armed and a person is detected, a video verification event is logged and sent to our monitoring agents for review. Click **Done** when you’re done with your selection. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252F3grM98EyYW0Ea662JJOk%252Fimage%2520%284%29.png%3Falt%3Dmedia%26token%3Dc856dee7-fec5-4636-b515-335c39de4907&width=768&dpr=4&quality=100&sign=949b42e4&sv=2) **Specify a region of interest** You can specify a region of interest where the selected region (in blue) is the only area where person detection is running; everything outside of the blue box is ignored. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252FSaRKe5zoBR9AnfRuoZq9%252Fimage%2520%283%29.png%3Falt%3Dmedia%26token%3Daa769836-b2ef-4235-8f4b-03157d1ff0a6&width=768&dpr=4&quality=100&sign=d1aac246&sv=2) Wired sensors[](https://help.verkada.com/classic-alarms/configuration-and-setup/configure-classic-alarms-site-settings#wired-sensors) An alarm panel detects a relevant state change (door open, glass break, water detected, motion detected, and so on). Wireless sensors[](https://help.verkada.com/classic-alarms/configuration-and-setup/configure-classic-alarms-site-settings#wireless-sensors) Configure wireless sensor-specific settings: **Door Sensor** * **Sensitivity Level (Low, Medium, High)**—The higher the sensitivity, the greater distance allowed between the sensor and the magnet to register a closed event. * **Universal Transmitter Mode (Normally Open, Normally Closed)**—Allows the door contact sensor to be utilized as a wireless transmitter, turning any standard 2-wire sensor into a wireless signal **Panic button** **Button Press Pattern (Single, Long, Double, Triple)**—Allows you to specify the type of button press pattern required to send a panic signal. Access control[](https://help.verkada.com/classic-alarms/configuration-and-setup/configure-classic-alarms-site-settings#access-control) An access controller detects a door open, door held open or door forced open event. Alarm console[](https://help.verkada.com/classic-alarms/configuration-and-setup/configure-classic-alarms-site-settings#alarm-console) You can configure an alarm console as a trigger by using person detection on its camera. Air quality sensor events[](https://help.verkada.com/classic-alarms/configuration-and-setup/configure-classic-alarms-site-settings#air-quality-sensor-events) A sensor detects motion, changes in temperature, humidity, air quality, and so on. **Required.** [Air Quality Sensor Thresholds](https://help.verkada.com/air-quality/events-and-alerts/configure-air-quality-event-alerts) must be configured for the particular readings that you want to use as a trigger to raise an alarm. Offline events[](https://help.verkada.com/classic-alarms/configuration-and-setup/configure-classic-alarms-site-settings#offline-events) Set the desired response when an alarm device goes offline. Alarm responses[](https://help.verkada.com/classic-alarms/configuration-and-setup/configure-classic-alarms-site-settings#alarm-responses) Video Verification If enabled, video verification allows for a Verkada monitoring agent to review video footage of an incident before raising an alarm. This reduces the likelihood of false alarms. You can configure these levels of security for video verification: * **Normal Security**—An alarm is only raised if there is a visible threat to a person or property. For example, a person brandishing a weapon, broken glass, etc. * **Max Security**—An alarm is raised if a person is present or if there are any signs of an intrusion. This alarm level helps to significantly reduce the chance of a false alarm occurring. * **Customer Security**—An administrator can choose what the monitoring agent will raise an alarm for depending on the video [verification rules](https://help.verkada.com/classic-alarms/configuration-and-setup/verification-rules) . Organizations that create their _**first**_ Alarms site on or after\*\* June 29, 2024, \*\*will no longer be able to select a video verification security level; the Alarms site will operate under max security verification. **Use case of trip event** Site is armedA camera detects a janitor in a safe roomTrip event occursVideo clip of the event is sent to the monitoring agent for review In _normal security_ mode, the agent determines that there is no visible threat to people or property and an alarm is not raised. In _max security_ mode, the agent raises an alarm immediately if a person is present when the site is armed. For video verification to be active for non-camera devices, you need to link your devices to nearby cameras that can provide context for alarm events. For air quality sensors and doors, the cameras you’ve previously associated with those devices are automatically used for video verification. For BH61 / BP41 sensor inputs, you can manually add nearby cameras when you configure those inputs. For more information on the video verification rules, refer to [Verification Rules](https://help.verkada.com/classic-alarms/configuration-and-setup/verification-rules) . ​ **Emergency Dispatch** If emergency dispatch is enabled, the Verkada monitoring agent contacts the individuals in the order of your contact list. If an emergency is confirmed or if no one can be reached, the agent dispatches emergency services to the site address. You must have at least one [contact](https://help.verkada.com/classic-alarms/configuration-and-setup/configure-classic-alarms-site-settings) with a valid phone number listed to use emergency dispatch. * **Immediate Dispatch on Panic** When enabled, Verkada monitoring agents dispatch emergency services immediately without confirming with contact list. This _only_ applies to duress and panic alarms. Notification recipients still receive a call/SMS to get visibility into the situation. * **Monitoring Test Mode** If enabled, the Verkada monitoring agent still reaches out in the order of your contact list, but does _not_ dispatch emergency services if they are unable to reach you. * **Permit Number (Optional)** You can optionally add a permit number to be shared with emergency services when dispatch is requested. _This is sometimes a requirement in certain counties and states_ and should be acquired via local Verkada Partner as requirements differ across jurisdictions. You can also provide property entry or gate codes for monitoring team to provide to emergency services: ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-4597c5f002562060870dcdefe1497fe02950f066%252F63a83ed3019308566fd244f2de7db373ab1e1486.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=bbc0433d&sv=2) * **Emergency Dispatch Context Cameras** By default, our monitoring agents do not have any access to your cameras. This setting allows you to grant **live-only** access to a **maximum of 10 cameras** in addition to any footage that has been video verified to gather additional context during an active alarm. Contact list[](https://help.verkada.com/classic-alarms/configuration-and-setup/configure-classic-alarms-site-settings#contact-list) Configure Command users to be notified via SMS and/or email notifications when an alarm is raised. These notifications can be sent, regardless of whether emergency dispatch is enabled. By default, all users will receive SMS and email notifications, but need to be explicitly designated as emergency dispatch contacts. To do that, click the **Dispatcher** icon. The call order is determined by the number to the right of the **Dispatcher** icon. **Important**. Please ask users on the notification list to save the following numbers to their contact list as "Verkada Monitoring". These are the numbers that we use to notify you of an emergency: **SMS** +16193298928 +16193298846 +16193298736 **Phone call** +16193044016 Alarm actions[](https://help.verkada.com/classic-alarms/configuration-and-setup/configure-classic-alarms-site-settings#alarm-actions) You can configure which actions to take when an alarm is raised: * **Alarm panel outputs** If you have a BP41 alarm panel, you can configure outputs A and B on the panel to provide 12V of power to sirens, strobes, and other alarm signaling devices in the event of an alarm. Find setup instructions [here](https://help.verkada.com/classic-alarms/hardware-installation/configure-and-wire-inputsoutputs-on-the-bp41) . * **Wireless outputs** If you have a BX21, you can configure the wireless relay as an output for a siren, strobe, or other alarm signaling devices. Find setup instructions [here](https://help.verkada.com/classic-alarms/hardware-installation/configure-a-bx21-wireless-relay) . * **Pay alert message** You can also choose to play an alert message on the alarm console. * **Access control lockdown** You can leverage a configured [lockdown](https://help.verkada.com/access-control/configuration-and-setup/emergency-lockdown) scenario through Verkada access control as a response to an alarm being raised. * * * ### [](https://help.verkada.com/classic-alarms/configuration-and-setup/configure-classic-alarms-site-settings#arm-disarm-settings) Arm/Disarm settings Setting Description **Entry Delay** Number of seconds to wait after a trigger event occurs before raising an alarm. **Exit Delay** Number of seconds to wait after entering the code entry before arming site. **Geofence Arm/Disarm** Restricts mobile app arm/disarm when the user is within 200 meters of the alarm site. **Note:** The Verkada Alarms app will be required to arm/disarm for users with Site Viewer permissions or lower. **Arm Schedule** Automatically arms the site during the specified window. **Auto Re-Arm** If disarmed during the arm period, automatically re-arms the site after a set period of time. **Auto Disarm** Automatically disarms the site at the end of the schedule. **Arm/Disarm Notification Window** Receive a notification whenever an arm/disarm occurs within a specific time range. **Output on Arm** A wired output is enabled when the site is armed and disabled when it is disarmed. **Disarm via Doors** Select which doors automatically disarm the site when the door is unlocked via a badge swipe. This option is only available if a door exists in the site. **Arm via Doors** Select which doors automatically arm the site when the door is unlocked via a badge swipe. This option is only available if a door exists in the site. **Note**: The exit delay is 20 seconds. **Toggle via Doors** Toggle between armed/disarmed for this site when one of these doors grant access. **Keycodes** You can add multiple site keycodes that arm/disarm the system and individual [user keycodes](https://help.verkada.com/classic-alarms/configuration-and-setup/generate-a-user-or-general-keycode-with-classic-alarms) . **Duress Keycode** You can enter this code to trigger a panic alarm on the alarm console in case of an emergency. When a duress code is entered into the console, the system disarms the site, but still triggers alarm notifications and emergency dispatch (if enabled). ### [](https://help.verkada.com/classic-alarms/configuration-and-setup/configure-classic-alarms-site-settings#alarm-console-settings) Alarm console settings Here are the settings you can configure for the alarm console. Setting Description **Enable Console Video Recording** Gives users access to live and historical video from the alarm console in Command. **Enable Console Video Stream** Gives users access to live video on the console for all cameras in the site. **Arm/Disarm Announcement** Console announces when a site is arming, armed, or disarmed. **Alarm Trigger Announcement** Console announces when a site has been tripped. **Alarm Raised Announcement** Console announces when an alarm is raised. **Enable Console Door Chime** Console plays an audio tone when a door in the site is opened. **Console Controls** Restarts the console remotely. Last updated 23 hours ago Was this helpful? --- # Cellular Gateway Status LEDs | Connectivity | Verkada Help Verkada’s [GC31/GC31-E Cellular Gateway](https://www.verkada.com/cellular-gateway) is equipped with LED light statuses by model: **Model** **Operation Type** [GC31](https://help.verkada.com/connectivity/configuration-and-setup/cellular-gateway-status-leds#h_40806a4487) (indoor) [Regular operation](https://help.verkada.com/connectivity/configuration-and-setup/cellular-gateway-status-leds#h_d160696649) [SIM card operation](https://help.verkada.com/connectivity/configuration-and-setup/cellular-gateway-status-leds#h_1f575e66f4) [GC31-E](https://help.verkada.com/connectivity/configuration-and-setup/cellular-gateway-status-leds#h_1394c2a584) (outdoor) [Regular operation](https://help.verkada.com/connectivity/configuration-and-setup/cellular-gateway-status-leds#h_b29c15c8c7) [SIM card operation](https://help.verkada.com/connectivity/configuration-and-setup/cellular-gateway-status-leds#h_fc60063a6b) Use this article to learn about the different LED characteristics to help you understand what they mean. * * * [](https://help.verkada.com/connectivity/configuration-and-setup/cellular-gateway-status-leds#gc31-status-leds) GC31 status LEDs ------------------------------------------------------------------------------------------------------------------------------------- ### [](https://help.verkada.com/connectivity/configuration-and-setup/cellular-gateway-status-leds#regular-operation) Regular operation The LED status light consists of the following states: * **Solid orange**—GC31 is on and booting up * **Flashing orange**—GC31 is updating firmware * **Solid blue**—GC31 is running and online * **Flashing blue**—GC31 is running and offline ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1814166542-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FiAGnzScvko5PkG7YBy3i%252Fuploads%252Fgit-blob-69e1d4c059601c36100ed37b6b99769d3ffc6ef7%252Fd5b68cd3f90b83812b020f3d35511878586cf2b5.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=1614e7b8&sv=2) ### [](https://help.verkada.com/connectivity/configuration-and-setup/cellular-gateway-status-leds#sim-card-operation) SIM card operation The LED status light consists of the following states: * **No light**—No SIM detected * **Solid white**—SIM card detected * **Flash white**—SIM card detected and running ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1814166542-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FiAGnzScvko5PkG7YBy3i%252Fuploads%252Fgit-blob-1b056f5a5321a4a0e28562672b174ef042d964c0%252Fabc94f0a57bb547b918af3058f6421e81aeda45b.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=b7299674&sv=2) * * * [](https://help.verkada.com/connectivity/configuration-and-setup/cellular-gateway-status-leds#gc31-e-status-leds) GC31-E status LEDs ----------------------------------------------------------------------------------------------------------------------------------------- ### [](https://help.verkada.com/connectivity/configuration-and-setup/cellular-gateway-status-leds#regular-operation-1) Regular operation The LED status light consists of the following states: * **Solid orange**—GC31 is on and booting up * **Flashing orange**—GC31 is updating firmware * **Solid blue**—GC31 is running and online * **Flashing blue**—GC31 is running and offline ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1814166542-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FiAGnzScvko5PkG7YBy3i%252Fuploads%252Fgit-blob-8105ba807a7d5028c83b8d432da35fc2614cbcfa%252F88089a6302c3188f8091be13f81e78090ab1166d.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=94944587&sv=2) ### [](https://help.verkada.com/connectivity/configuration-and-setup/cellular-gateway-status-leds#sim-card-operation-1) SIM card operation The LED status light consists of the following states: * **No light**—No SIM detected * **Solid white**—SIM card detected * **Flashing white**—SIM card detected and running ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1814166542-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FiAGnzScvko5PkG7YBy3i%252Fuploads%252Fgit-blob-01a8ed633c8b8a757f2c6e103d7fdb68e4356a67%252F7ce60ce007af44449885546fce8f0c5a23dedcc0.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=d22356d2&sv=2) Last updated 18 hours ago Was this helpful? --- # Use Cellular Gateways for WAN Failover | Connectivity | Verkada Help Cellular Gateways support WAN failover mode, which enables the gateway to act as an uplink to your existing network. In WAN failover mode, the Gateway’s cellular connection will act as a failover, helping ensure that your security devices remain online and operational even when your primary network experiences downtime. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1814166542-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FiAGnzScvko5PkG7YBy3i%252Fuploads%252Fgit-blob-df57d7d0a2ca12268ba9b242122d074d8a6c6299%252Fabdede7a2a1bab531cc76f831c98408ac12ededf.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=81ac894f&sv=2) The cellular connection will remain active when the device is in WAN failover mode and consume minimal data. When the wired ethernet connection fails, the cellular connection acts as a failover, keeping the gateway and any connected devices online. * * * [](https://help.verkada.com/connectivity/configuration-and-setup/use-cellular-gateways-for-wan-failover#enable-wan-mode) Enable WAN mode --------------------------------------------------------------------------------------------------------------------------------------------- #### [](https://help.verkada.com/connectivity/configuration-and-setup/use-cellular-gateways-for-wan-failover#outdoor-cellular-gateway) Outdoor Cellular Gateway WAN failover mode works automatically on the GC31-E. 1 **Plug the ethernet cable into the PoE In port, and the gateway will automatically detect the uplink and use the wired connection.** 2 **Once the gateway receives an IP address from the wired network, a WAN badge will appear on the gateway details page, indicating that the connection was successful and the gateway is now functioning in WAN failover mode.** 3 **Verkada devices need to be connected downstream on the PoE Out port of the cellular gateway and get their IP addresses from the gateway.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1814166542-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FiAGnzScvko5PkG7YBy3i%252Fuploads%252Fgit-blob-08ce6993b0fb2dea7b9bf48d76f111324963f0f4%252Ff2b8c50262e053b25e06f62c86a12cd72d3be911.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=36e6e1fe&sv=2) All downstream devices must receive their IP address & DHCP information from the gateway before a WAN failover can occur. #### [](https://help.verkada.com/connectivity/configuration-and-setup/use-cellular-gateways-for-wan-failover#indoor-cellular-gateway) Indoor Cellular Gateway To enable WAN failover mode on the GC31, you will need to configure **PoE Out Port 2** to act as an uplink. 1 **In Verkada Command, go to All Products > Gateways .** 2 **Select the gateway you want to configure.** 3 **In the top right, click Settings .** 4 **Under Network > Port 2 Configuration, select Wide Area Network (WAN).** 5 **Click Apply to save the configuration.** 6 **Click Confirm, and the device will reboot. PoE port 2 will now act as a WAN port.** 7 **Plug the ethernet cable into PoE port 2.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1814166542-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FiAGnzScvko5PkG7YBy3i%252Fuploads%252Fgit-blob-3e0d1178189fa871b6d48aa1b3ad335c5a18be6c%252F3850099f28c5cbb82f4179d014273fbfe1616b41.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=3e80447c&sv=2) 8 **Verkada devices need to be connected downstream on port 1 of the cellular gateway and get their IP addresses from the gateway.** 9 **When the device receives an IP from the wired network, a WAN badge will appear on the gateway details page.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1814166542-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FiAGnzScvko5PkG7YBy3i%252Fuploads%252Fgit-blob-0ce57203d4c2743f47ba88ee47734a61707566e7%252F981fdb5aa09d4b48643b196fe6fabe44eb67cd3b.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=aad1bbb1&sv=2) Last updated 17 hours ago Was this helpful? --- # Set Up Your Wireless Alarm Devices | Classic Alarms | Verkada Help This article is a guide for classic Alarms. Refer to this [article](https://help.verkada.com/new-alarms/configuration-and-setup/wireless-alarms-devices) if you have new Alarms. See [New Alarms vs Classic Alarms](https://help.verkada.com/new-alarms/new-alarms-vs-classic-alarms) if you are unsure which version of Alarms you have. * * * The Verkada wireless hub and sensors communicate over a proprietary sub-GHz wireless communication protocol. This custom protocol operates at 915 MHz (US, Canada)/868 MHz (UK, EU), and was built from the ground up to maximize security, range, and battery life. Our wireless signals are encrypted using AES-128. Through direct sequence spread spectrum (DSSS) technology, Verkada’s technology prevents signal jamming and other attacks, which can impact competitor systems. * * * ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-8e8c86fa7a71ac845ea88e0cdbc99a3120b01f3a%252Feeb781bf340e4d66baf9dd64881376ff1907c534.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=99d320d9&sv=2) [](https://help.verkada.com/classic-alarms/hardware-installation/set-up-your-wireless-alarm-devices#wireless-specs) Wireless specs --------------------------------------------------------------------------------------------------------------------------------------- SKU Description Line of Sight Typical Office Battery Life Power [BR31](https://docs.verkada.com/docs/br31-quick-start-guide.pdf) Door 1,000 ft (304.8m) 200 ft (61.26m) Up to 10 yrs 2x CR123A [BR32](https://docs.verkada.com/docs/br32-quick-start-guide.pdf) Motion 1,000 ft (304.8m) 200 ft (61.26m) Up to 5 yrs 2x CR123A [BR33](https://docs.verkada.com/docs/br33-quick-start-guide.pdf) Panic 1,000 ft (304.8m) 200 ft (61.26m) Up to 5 yrs 1x CR123A [BR34](https://docs.verkada.com/docs/br34-quick-start-guide.pdf) Glass 1,000 ft (304.8m) 200 ft (61.26m) Up to 2 yrs 1x CR123A [BR35](https://docs.verkada.com/docs/br35-quick-start-guide.pdf) Leak 1,000 ft (304.8m) 200 ft (61.26m) Up to 5 yrs 1x CR123A [BX21](https://docs.verkada.com/docs/wireless-relay-bx21-datasheet.pdf) Relay 1,000 ft (304.8m) 200 ft (61.26m) N/A 12/24v power supply * * * [](https://help.verkada.com/classic-alarms/hardware-installation/set-up-your-wireless-alarm-devices#wireless-alarms-devices) Wireless Alarms devices --------------------------------------------------------------------------------------------------------------------------------------------------------- BH61 wireless alarm hub[](https://help.verkada.com/classic-alarms/hardware-installation/set-up-your-wireless-alarm-devices#bh61-wireless-alarm-hub) The [BH61 wireless alarm hub](https://docs.verkada.com/docs/wireless-intrusion-overview.pdf#page=2) supports up to 60 wireless Verkada sensors. The typical unobstructed line-of-site range is up to 1,000 ft (304.8m) and up to 200 ft (61.26m) in typical office environments. The hub comes with a built-in backup battery to keep the system powered up to 12 hours in the event of a power loss. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-8cc663b3950e629615cebbe116d526c79f8387b9%252Fe100b45f00c775a151f443f291a56b3a96c875bf.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=49ef5625&sv=2) ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-999a2be81b8450a5c4fbbee880454034e0a45539%252F8b671ec81e1c25724c612b2c0d08ac5592f60749.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=fd9082c3&sv=2) **Install the BH61** **Recommended**. The BH61 is omnidirectional and performs best you mount the it at ceiling and install as close to the center of the building/floor as possible for maximum coverage. * Have 1 hub per floor of a building. * A typical office environment consists of: * 5–7 walls, with materials consisting of drywall or wood. * Coverage is 200 ft (61.26m) from the hub. * Range is highly variable with building materials consisting of concrete or metal. **Test the BH61** In **normal operation**, the LED signifies: * **Solid orange**—Hub is on and booting up. * **Flashing orange**—Hub is updating firmware. * **Flashing blue**—Hub can receive events, but cannot reach the server. * **Solid blue**—Hub is running, connected, and receiving events. **Required**: The BH61 alarm hub contains a dip switch on the front of the device under the white plastic cover. You must set this dip switch to the left for the device to power on. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-f84f9cec20853797148a49be553b50f24ce09c4b%252F6d4a6bef100c09fd16d5dda336418dadf80bdb4a.jpg%3Falt%3Dmedia&width=300&dpr=4&quality=100&sign=cfd9d519&sv=2) BR31 wireless door sensor[](https://help.verkada.com/classic-alarms/hardware-installation/set-up-your-wireless-alarm-devices#br31-wireless-door-sensor) The [BR31 wireless door sensor](https://docs.verkada.com/docs/wireless-intrusion-overview.pdf#page=4) is powered by 2 CR123A lithium batteries and has a battery life of up to 10 years. Configurable door gap width up to 2 in (5cm) to support different installation requirements. An optional configuration as a universal transmitter allows you to use internally wired input terminals to convert signals from a separate 2-wire sensor into wireless signals that can be received by the BH61 wireless hub. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-0b72a51ff9133d621d8a77b365f7976e4a27cffd%252Feb2095ec139c1d55a9c810e338bc70550bb209eb.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=869feeff&sv=2) ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-a407dd2d11b41f44e083cc25930e16beeb0b0f9f%252F2f7455bc10d0be147bb057117b1f7560f6c3eb67.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=87cfad18&sv=2) **Install the BR31** **Recommended**. Mount the magnet (left) on surfaces that experience movements, such as the door and the door sensor (right) on stationary surfaces, such as the door frame. * Position the magnet near the top of the wireless sensor where the status LED and test mode button reside for ideal operation. **Required:** You must position the door sensor as referenced below. Any other type of magnet positioning will induce false positive open/closed events ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-2ff83167188df9e7c55f27fc81469bd331bd6266%252Faefce4afe4fe5d21af6845e5404fbfad14baf214.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=ecf808b1&sv=2) Below is an example of improper installation as the magnet is facing toward the sensor. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-fc69e6e3c8d16d4fe7f9c101cd6c79308edf9768%252F8011e23700e328428baf127d4758933642ce4174.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=3f0f0aed&sv=2) * Configure the range between the magnet and door sensor up to 2 inches: 1. Under the **Alarms** site, click **Devices**. 2. Hover to the right, click the **kebab** and select **Edit Sensor**. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-03373611f4c4e1b4fc062aeba509b64cb9a44b44%252F836f2f8f3fb2528f81bb07ccc76cebbb19db637a.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=b7a45a2f&sv=2) 3. On the popup that appears, configure the sensitivity. The higher number indicates that the magnet can be further away; while low indicates that the magnet can be closer. ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252FTvGkSgMlU6rJlUsMyArW%252FScreen%2520Shot%25202022-07-11%2520at%25204.35.53%2520PM.png%3Falt%3Dmedia%26token%3D90c0e44a-ef2b-404e-adbc-bea94b140be8&width=768&dpr=4&quality=100&sign=9b5037c1&sv=2) **Required**. Once changed, you **must** open and close the door to change its state so that the sensor can reflect the change made in Verkada Command. ​ * (Optional) Configure additional settings, as necessary: * **Universal Transmitter Mode**—Toggle on and select the **Normal State** to transmit any signal wired into the sensor back to the wireless hub. * **Door Held Open**—When enabled, only door held open (DHO) events trigger an alarm. * **No Entry Delay**—When this device triggers an alarm, any delays are ignored. * **Panic Mode**—When this is activated, it raises an alarm when both armed and disarmed. It skips video verification and any entry delay. **Test the BR31** Click the top button to enable test mode. After 10 minutes in test mode, the device returns to normal operation. In test mode, the green LED:Turns on when the sensor is separated from the magnet (door open)Turns off when the sensor is brought close to the magnet (door close)While in normal operation, the green LED:Does not turn on when the sensor is separated from the magnetFlashes rapidly 2 to 3 times every 2 minutes to indicate low battery BR32 wireless motion sensor[](https://help.verkada.com/classic-alarms/hardware-installation/set-up-your-wireless-alarm-devices#br32-wireless-motion-sensor) The [BR32 wireless motion sensor](https://docs.verkada.com/docs/wireless-intrusion-overview.pdf#page=5) is powered by 2 CR123A lithium batteries and has a battery life of up to 5 years. The sensor uses passive infrared (PIR) to detect changes in infrared light with a 90° horizontal field of view and 35 ft (10m) detection range. Pet/animal-resistant up to 80 lb (36 kg). ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-081f6b68c9a2813fb7e07ef74866bf14b273cbc1%252F5192aa4d6319bf71ac729b1d58c96416abe731db.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=d3b43690&sv=2) **Install the BR32** **Recommended**. For ideal coverage, install the motion sensor 6 ft (1.8m) from the floor in the corner of a room, and with the LED on the top. Check the proper orientation by the top arrow inside the back cover. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-c56353ab552cb231c3290f7fd971a5981573012e%252Fb9c5501fb198e3438c5f5f6bd9b878b3b6c56149.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=91549858&sv=2) **Test the BR32** After installing the batteries, the motion sensor goes into walk test mode. After 10 minutes in test mode, the device returns to normal operation. In test mode, the green LED: * Turns on when motion is detected * Turns off after 5 seconds pass with no detected motion While in **normal operation**, the green LED: * **Does not** turn on when motion is detected * Flashes rapidly 2 times every 2 minutes to indicate low battery BR33 wireless panic button[](https://help.verkada.com/classic-alarms/hardware-installation/set-up-your-wireless-alarm-devices#br33-wireless-panic-button) The [BR33 wireless panic button](https://docs.verkada.com/docs/wireless-intrusion-overview.pdf#page=6) is powered by a 1 CR123A lithium battery and has a battery life of up to 5 years. Allows for custom alarm actions configurable in Command. Supports both wall/desk mounting only. The LED provides immediate feedback on whether a panic signal was successfully received by the hub. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-9c050306e810072c8733cc566185f34ffa9743a4%252Ff0342bfdb4132c761a703ec9456a3ce5f69d9f2d.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=af5eac2b&sv=2) ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-4b355bb64d9d7e20ec10f9456a5253aa2b7a0f6c%252F39c3ec438b54d69352910c6f6bc7c92325d23f16.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=cf52596f&sv=2) **Install the BR33** You can mount the BR33 panic button above, side, below, or worn as a pendant with the built-in loop on the mounting plate. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-a25b9dbff8f621cca26d1f8127437aa7314dbe55%252F461d8218da65d0e52935cc4e1f18d2b9471bcc4c.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=a04330bd&sv=2) **Test the BR33 panic button** * During **normal operation**, the green LED: * Blinks green at button press to signify that it has reached out to the hub and is awaiting a response * Solid green LED at button press to signify that the panic message has been received by the hub. * Flashes rapidly 3 times every 2 minutes to indicate low battery. * **Silent Mode**—Disables alarm outputs and console alerts. BR34 wireless glass break sensor[](https://help.verkada.com/classic-alarms/hardware-installation/set-up-your-wireless-alarm-devices#br34-wireless-glass-break-sensor) The [BR34 wireless glass break sensor](https://docs.verkada.com/docs/wireless-intrusion-overview.pdf#page=7) is powered by a 1 CR123A lithium battery and has a battery life of up to 2 years. The sensor uses dual detection to reduce false positives by requiring both impact and successive shattering frequencies to trigger an alarm with a detection range up to 15 ft (5m). ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-045beb9a4428ccd08c93d95b3954c7aa0c6a9086%252Fb5c4c85e064aaa6f1c48f13c290666571075349f.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=ec452d6b&sv=2) ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-246b388aaae4e39e489b0cc03b6eef5cb329fc23%252F27f9294d8fdf1282ef7b0b05c3ad0aa68a2ed2b4.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=e4797d0&sv=2) **Install the BR34** You can mount the BR33 on the ceiling or wall with a line-of-sight distance of no more than 15 ft (5m) from the window(s) that you want to protect. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-2815e99907eb5dc8728fecb04ab31311a391ea07%252F9410caef688f034d8f37ad87d1ef47dbe6092227.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=d5008d35&sv=2) **Recommended**. To avoid false positives, install the glass break sensors in areas without excessive vibrations. **Protected glass types** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-49141bc58eb0b59004b8febe07dc77d6ad910c2d%252Fe0218b185d548131d12d3c442af1891095a87f91.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=ce998fe&sv=2) **Note**: The minimum size for all types is 14 in (35 cm) square; glass must be framed in the wall or mounted in a barrier at least 36 in (91 cm) wide. Protected only if both plates in the unit are broken. **Test the BR34** **Recommended**. Purchase the Honeywell Intellisense FG-701 Microflex tester to verify sensor operation. Place the tester in "Test" and "Flex" mode.In Flex mode, the FG-701 Microflex tester listens for a "Flex" signal, which is a low-frequency thud before producing a burst of glass-break audio.Position the FG-701 within 118 in (3m) with the speaker facing the BR34 glass break sensor.Press the (red) Start button.The simulator clicks on and starts an 8-second armed period.Carefully strike a nearby wall, table, surface, or the glass break tester itselt to generate the flex signal.The BR34 glass sensor displays a green LED when a glass break is detected. During normal operation, the green LED:Turns on when the glass break event is detected. The light goes off after 5 seconds.Flashes rapidly 3 times every 2 minutes to indicate low battery. BR35 wireless water sensor[](https://help.verkada.com/classic-alarms/hardware-installation/set-up-your-wireless-alarm-devices#br35-wireless-water-sensor) The [BR35 wireless water leak sensor](https://docs.verkada.com/docs/wireless-intrusion-overview.pdf#page=8) is powered by a CR123A lithium battery and has a battery life of up to 5 years. The sensor has a 7 ft (2.1m)-extended probe that allows for precise placement in areas at risk for water leaks. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-814f47b8924f3f5d4e1d48af28d07dd3bf27b4fc%252F4e7dac01d22b10ebcce233ba862b10ce258c7145.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=103fa1bc&sv=2) ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-63114b38d7a68db96d0b22cc5158fcd7f58f1dc2%252Ff203b82154bf2dc6e2f7796caef8ef8e2e3baee5.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=4c0af02b&sv=2) **Install the BR35** **Recommended**. For ideal coverage, install the base module in the open with as little obstruction from the sensor to the wireless hub as possible. Install the probe on the floor where water will accumulate. ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-55c537c77c2e13cef3ffc75a6d957a9a3c82a3f3%252F0927251506ef5eb911e2fcf2a684502258d73058.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=12f77e73&sv=2) **Test the BR35** You can test the operation of the water sensor by shorting the 2 metal contacts at the end of the probe with a conductive material, such as water, a metal screwdriver, or your thumb (place the edge of your thumb on the farthest contact and allow the base of your thumb to touch the closest contact to complete the circuit). During normal operation, the green LED: * Turns on when water is detected. It stays on as long as the water is detected. * Turns off when no water is detected. * Flashes rapidly 3 times every 2 minutes to indicate low battery. BX21 wireless relay[](https://help.verkada.com/classic-alarms/hardware-installation/set-up-your-wireless-alarm-devices#bx21-wireless-relay) The [BX21 wireless relay](https://www.verkada.com/docs/wireless-relay-setup-guide/) is powered by an external 12/24 volt power source. The sensor allows you to control sirens or strobes when an alarm is raised. Optionally, the BX21 can be configured as a universal transmitter that allows you to use internally wired input terminals to convert signals from a separate 2-wire sensor into wireless signals that can be received by the [BH61 wireless hub](https://help.verkada.com/classic-alarms/hardware-installation/set-up-your-wireless-alarm-devices) . ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-2b489a86a336058e93877a9e0fa027a4f1425aa3%252F5eb0334f18ceb5f9e119d3e60700584160cb1f57.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=5c9ef0cf&sv=2) **Install the BX21** Mount the BX21 (vertically or horizontally) with the included screws or adhesive tape.Connect the siren/strobe to NC or NO and COM.Connect a power source to the positive and negative terminals.​ **Test the BX21** To test the functionality of the relay, use the included Allen key to push the test button. When you hold down the test button, the relay outputs to the end device, confirming functionality. **Configure the wireless output** Go to your alarm site **Settings > Alarm Responses > Wireless Relay Outputs > Add Output**. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-0f98fb5de38a4353aa885c31331c68ca2e483afb%252F1ce1ce9e082f226e08f0f93c38bde1258f985317.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=f96933d&sv=2) Cellular backup module[](https://help.verkada.com/classic-alarms/hardware-installation/set-up-your-wireless-alarm-devices#cellular-backup-module) The ACC-CEL-LTE [cellular backup module](https://docs.verkada.com/docs/cellular-module-overview.pdf) is a plug-and-play solution that is powered by a USB 2.0 connection to the BP41 alarm panel or BH61 wireless alarm hub. This module provides a multiple network LTE connection (AT&T and T-Mobile) with automatic failover to the best available network. An unlimited data plan for alarm signaling is included in the license. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-963af0e47b53966a5c4103adf4d114b289335856%252F8389917f9f19f73241607aebeb5e21a86bd21481.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=9793a771&sv=2) **Install the cellular backup module** The cellular backup module plugs into the [BH61 wireless hub](https://help.verkada.com/classic-alarms/hardware-installation/set-up-your-wireless-alarm-devices) or [BP41 wired alarm panel](https://docs.verkada.com/docs/alarm-panel-overview.pdf) via USB and is plug-and-play. Mount the cellular module and position the antenna in a way that provides the greatest signal strength and minimizes obstruction.Test the module. You can test cellular failover capabilities by simply unplugging the Ethernet cable from the BP41 alarm panel or BH61 alarm hub.​ ​Note: Please allow the hub at least 30 minutes to charge its internal battery before testing. ​Mount the cellular module and position the antenna in a way that provides the greatest signal strength and minimizes obstruction. **Test the module** Unplug the Ethernet cable from the BP41 alarm panel or BH61 alarm hub to test cellular failover capabilities.Check that the hub LED should transition from solid blue to blinking blue, and finally back to solid blue.Initiate a trigger from any wireless sensor device and check if Command has received the event. * * * [](https://help.verkada.com/classic-alarms/hardware-installation/set-up-your-wireless-alarm-devices#mute-device-and-tamper-events-on-wireless-sensors) Mute device and tamper events on wireless sensors ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- All wireless sensors now have the capability to mute to the events and tamper events. To configure this for the sensor, navigate to the device in the alarms site. 1 **In Verkada Command, go to All Products > Alarms.** 2 **Select your alarm site.** 3 **Click Devices.** 4 **On Devices, select your sensor, click and select Edit Sensor.** 5 **On the popup, toggle the settings, as needed. These are useful if there may be a fault in the install and you want to have the device not raise an alarm. Use the toggle instead of moving the sensor to a separate site or removing the sensor from command.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-86704259a134bcb000fb2e942eba0c672a96568b%252F97d8ac1f55c6314741681001f082ae5392ed16fb.gif%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=4c805d15&sv=2) Last updated 23 hours ago Was this helpful? --- # Set Up Universal Transmitter Mode on a BR31 with Classic Alarms | Classic Alarms | Verkada Help This article is a guide for classic Alarms. Refer to this [article](https://help.verkada.com/new-alarms/hardware-installation/set-up-universal-transmitter-mode-on-a-br31) if you have new Alarms. See [New Alarms vs Classic Alarms](https://help.verkada.com/new-alarms/new-alarms-vs-classic-alarms) if you are unsure which version of Alarms you have. * * * The [Verkada BR31 wireless door sensor](https://docs.verkada.com/docs/br31-quick-start-guide.pdf) can be used as a universal transmitter, enabling wired alarm devices to communicate wirelessly with Verkada wireless hubs. 1 **Collect the required components, including the main body of the BR31, a T10 Torx screwdriver, and the wired sensor.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-d57a67c36fb40b19e5cd90c987957baa6b2c945d%252F49be12bc0d256ff07e624dd29ba775602110b0d5.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=f04ced57&sv=2) 2 **Use the T10 Torx screwdriver to unscrew the Torx screw on the underside of the BR31. Remove the backplate of the unit.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-4b349e335eed96502f5ad6435511bd64c221ba99%252Ffbcd443d5c1e411846602fdd0171a70a5eaede2a.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=4e7a8331&sv=2) 3 **Plug the leads of the wired alarm sensor into the 2 inputs at the top of the BR31 unit. Polarity does not matter in this case.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-19f927b67b9137bc1563fb7992a507da264e3612%252Fed446f22e60d730d92a4df061260ee8745e9ecff.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=e2d834e7&sv=2) * * * [](https://help.verkada.com/classic-alarms/hardware-installation/set-up-universal-transmitter-mode-on-a-br31-with-classic-alarms#command-set-up) Command set up -------------------------------------------------------------------------------------------------------------------------------------------------------------------- [Add the device](https://help.verkada.com/verkada-cameras/configuration-and-setup/add-a-device-to-your-command-organization) to Command before you continue. 1 **Navigate to the Devices page in the alarm site.** a. At the top right, click the **ellipsis** icon. b. Click **Edit Sensor**. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-6119c55b12c92713a4743726b6d603124a9cea9e%252F9253f4f4eaae2a301b66dde7bd2a35394c110d64.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=5a99885c&sv=2) ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-b55a3d81a9a4b440838ab019091e2fabb5ae1580%252Fca4680999ea4c5163139c656e83f348905fc6838.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=80bce50b&sv=2) 2 **In the device settings:** a. Enable **Universal Transmitter Mode**. b. Select the normal state of the sensor (see specific, relevant sensor). Wired door contact sensors are commonly "Normally Closed". c. Click **Done** and wait a few minutes for the new configuration to update on the BR31. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-f3611e72a0b3ea23282bbbc45299d4724e94b9e8%252Fc9bbab302d6330fb03d5e0c46b426f3013bf436c.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=11c9f8fb&sv=2) 3 **Manually trigger the wired sensor to confirm that the BR31 is transmitting the sensor events to Command.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-7dda210138cf6c3d5ba0bbc93f808883cda2a4ea%252F3bf5203e1938943c0cc8c56ba682f4a820b8fc9e.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=bc1556d3&sv=2) 4 **Once device performance is confirmed, follow the mounting steps in the** [**BR31 Install Guide**](https://docs.verkada.com/docs/br31-quick-start-guide.pdf) **to complete the installation.** Last updated 1 day ago Was this helpful? --- # Smart Data Usage | Connectivity | Verkada Help Verkada optimizes video streaming on cameras connected to gateways with smart data usage. When smart data usage is enabled for a gateway, its connected cameras will have the following behavior: * Live streams will default to standard quality (SQ). Users can manually switch to high-quality (HQ) if needed. * On grids and viewing stations, thumbnails will be displayed when no motion is detected. The cameras will begin streaming video once motion is detected. * Cloud backup and RTSP cannot be enabled. * * * [](https://help.verkada.com/connectivity/cellular-data-options/smart-data-usage#disable-smart-data-usage) Disable smart data usage --------------------------------------------------------------------------------------------------------------------------------------- Smart data usage is enabled by default on Cellular Gateways and disabled by default on Wi-Fi Gateways. You can disable this feature on cellular gateways that are using a non-Verkada SIM card. 1 **In Verkada Command, go to All Products > Gateways .** 2 **Select a gateway.** 3 **In the top right, click Settings .** 4 **Under Device, turn off Smart Data Usage.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1814166542-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FiAGnzScvko5PkG7YBy3i%252Fuploads%252Fgit-blob-63b390530bf5e21725e7c3282ba93373ba8fb628%252F51248fb7a2b736950c84259091bb625d86c47423.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=26ef1acd&sv=2) Smart data usage cannot be disabled when using the Verkada data plan. Last updated 20 hours ago Was this helpful? --- # Determine Relevant Alarm Permits | Classic Alarms | Verkada Help Ensuring compliance with local regulations and codes is crucial for receiving police dispatch for alarm events. In response to rising rates of false alarms, many police departments now require you, as an alarm user, to submit a registration form listing their installer and alarm company. Once submitted, this registration form helps you secure an alarm permit. The registration and permitting process can vary, depending on the city and state. [](https://help.verkada.com/classic-alarms/compliance-licensing-trials/determine-relevant-alarm-permits#prior-to-installation) Prior to installation --------------------------------------------------------------------------------------------------------------------------------------------------------- ### [](https://help.verkada.com/classic-alarms/compliance-licensing-trials/determine-relevant-alarm-permits#determine-permit-regulations-ahead) Determine permit regulations ahead Not securing the necessary alarm permit could lead to fines imposed by the municipality or a lack of police response to alarm events. To determine whether a permit is mandatory in your vicinity, contact your local police, sheriff, or fire departments through their non-emergency phone line, locate their contact information online, or check to see if they have a publicly available alarm ordinance. ### [](https://help.verkada.com/classic-alarms/compliance-licensing-trials/determine-relevant-alarm-permits#recommendations-for-alarm-partners-and-installers) Recommendations for alarm partners and installers * **Check city and state regulations** Always check the alarm regulations and codes in the city and state of installation. Requirements for alarm permits can vary significantly from one location to another. Check to see if the city has an Alarm Ordinance online prior to installation. ​ * **Find relevant registration forms** In some areas, resellers and installers may need to provide end users with a registration form to enable police dispatch services. Verify local requirements to determine if this step is necessary for your customers. ​ * **Check the Partner Portal** For reference about nationwide regulations, read Verkada’s Dealer Packet in the [Partner Portal](https://partners.verkada.com/) (under **Training** > **Selling Verkada Alarms**). This resource can provide valuable insights into general requirements and help streamline the permitting process across different locations. ### [](https://help.verkada.com/classic-alarms/compliance-licensing-trials/determine-relevant-alarm-permits#recommendations-for-customers-who-use-verkada-alarms) Recommendations for customers who use Verkada Alarms Obtaining any necessary alarm permits is a crucial step in ensuring the effectiveness of your Verkada alarm system. * **Familiarize yourself with local city codes** Take the time to understand the alarm regulations and codes specific to your city. This knowledge can empower you to ask informed questions and ensure compliance with local requirements. ​ * **Ask your installer for registration forms** If your local regulations require a registration form or permit for police dispatch, inquire with your alarm system installer. They should be able to provide you with the necessary documentation to complete the permitting process. In some cases they are also the ones responsible for registering the new system. ​ * **List Verkada on registration forms** * If the registration form asks for the name of the alarm company, enter **Verkada** and provide our license number in the states where we are licensed. For details, see our [Alarms Compliance and Availability.](https://www.verkada.com/alarms-availability/) * If the form asks for the name of the alarm installer, list your partner or installer. * If the form asks for the name of the monitoring center, refer to the appropriate Pima link for [Classic Alarms](https://my.pima.app/p/verkada/classic-alarm-monitoring-partners) or [New Alarms](https://my.pima.app/p/verkada/new-alarm-monitoring-partners) . * If you need further assistance, contact [Verkada Sales](https://help.verkada.com/cdn-cgi/l/email-protection#b8cbd9d4ddcbf8ceddcad3d9dcd996dbd7d5) or [Verkada Support](https://help.verkada.com/command/need-help/contact-verkada-support) . Last updated 23 hours ago Was this helpful? --- # Set Up the BK11/BK21 Alarm Keypad | Classic Alarms | Verkada Help The Verkada [BK11/BK21 alarm keypad](https://docs.verkada.com/docs/alarm-keypad-overview.pdf) is multi-functional where you can arm/disarm with a key code, view live camera feeds and device status, and connect wireless intrusion sensors (**BK21 only**). No extra hardware needed. ### [](https://help.verkada.com/classic-alarms/hardware-installation/set-up-the-bk11bk21-alarm-keypad#requirements) Requirements * The BK11/BK21 requires Power over Ethernet (PoE) (IEEE 802.3af) for power and network connectivity. * The BK11/BK21 includes a mounting bracket and associated mounting hardware for ease of install. This **must** be mounted horizontally (landscape mode). Stage the alarm keypad and test its functionality before mounting. * * * ### [](https://help.verkada.com/classic-alarms/hardware-installation/set-up-the-bk11bk21-alarm-keypad#before-you-begin) Before you begin For testing purposes, place the system in **Test Mode**. ### [](https://help.verkada.com/classic-alarms/hardware-installation/set-up-the-bk11bk21-alarm-keypad#whats-included) What’s included * **BK11/21 Alarm keypad** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-3626e99dcb4f8b1ddbf02b2b9e562f02b7cb9f4c%252Fb4a9a317788f77b464647da33f1d4be74956d1fb.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=d610c695&sv=2) * **Mounting screws** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-76b0c618da3a2824058c035a401a718f35e5ad5d%252F3bd373c75513939011487460c0e8c1caab5e6650.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=4d194c26&sv=2) * * * [](https://help.verkada.com/classic-alarms/hardware-installation/set-up-the-bk11bk21-alarm-keypad#installation) Installation --------------------------------------------------------------------------------------------------------------------------------- 1 **Attach an Ethernet cable to the BK11/BK21 (located in the back).** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-ecb1182109963a1bb9204f22a667c10f21fa47a3%252F261df46891d46c36ce50f92b16498c009c978f98.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=7a2209ae&sv=2) 2 **In Verkada Command, add the BK11/BK21 serial number or order number. This number is used to add to an alarm site. Learn more about how to** [**Add a Device to Your Command Account**](https://help.verkada.com/verkada-cameras/configuration-and-setup/add-a-device-to-your-command-organization) **.** 3 **Verify that the Alarm keypad power is on and is online in Command.** ​ The image below shows the default landing (Home) screen for the BK11/BK21. You use this screen to view/change the **Arm/Disarm** status, the date and time, and to use the **Panic** functionality. ​ 4 **Both the keypad and Web Command should be showing an Alarm status. Disregard this status:** _**enter your key code or manually resolve in Web Command**_**.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-d71fcd7ae259069e8130b5947a54f16b82c8f82b%252F7a1ce8faf87c46c9bf7edf6e13511468bf62adf3.jpg%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=d8f77132&sv=2) 5 **Press Arm to test the arm/disarm functionality. You can utilize your user-generated (random) code or, under General Codes, use a generic code.** ​ The first image below shows the keypad screen where you are redirected when you press **Arm** on the Home screen. You can also use this screen to enter your code to arm/disarm the site (second image). ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-b34daa679dc0fe7b4ee18abe8065d9ba8782c12b%252F6dd1771e6320d5509a697c456af60d7f6d1ec3ef.jpg%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=6ce161c5&sv=2) ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-e9244598aaf7ec602b16f6d90b209129ca505fbc%252F9802bfef50fde25426932215757c583be0e3ad71.jpg%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=dcb6ed91&sv=2) 6 **If you have live cameras in the same site, from the Home screen > swipe left to view the live stream of available cameras and tap them. Ensure that the Enable Cameras streams on Device toggle is on (on the Alarm Site settings for this screen to be visible).** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-c7f4f8e5a0cd0b38dfc9c76953345f6d8f4fefa1%252F656ffbe0901211d85baf0163b35b319694a70906.jpg%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=354c64cd&sv=2) 7 **If you have other devices in your alarm site, from the Home screen > swipe right to:** a. View a list of devices in their current statuses. (If you have a BK21, it should show the wireless sensors that have connected to the keypad). b. At the top right, you can filter devices by **All**, **Warning**, **Error**, or **Triggering**. c. Press the **information** (i) icon to view additional information, such as **Name**, **Serial Number**, **MAC address**, and current **IP address**. d. Tap a device to expand and view past event logs for that device. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-d1b625cc706efdccc10949ee31e7cf5257e32920%252F53f7744134c448349d5cf69ac9b452a1d0bbbae9.jpg%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=cb7a46f9&sv=2) Follow the [install guide](https://docs.verkada.com/docs/bk11-bk21-quick-start-guide.pdf) to mount your keypad after testing the functionality. * * * [](https://help.verkada.com/classic-alarms/hardware-installation/set-up-the-bk11bk21-alarm-keypad#command-set-up) Command set up ------------------------------------------------------------------------------------------------------------------------------------- 1 **In Verkada Command, add the BK11/BK21 serial number or order number. This number is used to add to an Alarm site. Learn more about how to** [**Add a Device to Your Command Account**](https://help.verkada.com/verkada-cameras/configuration-and-setup/add-a-device-to-your-command-organization) **.** 2 **Select the Alarm Site Settings > Arm/Disarm settings and add any required key codes. You can utilize your user-generated (random) code or, under General Codes, use a generic code.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-dd729afb9048e1970efaba898ede10e01d3ba861%252F5d9afa5f96fd66c31ec9a62e5a4dd6f2ef6e9c1d.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=10e64ef4&sv=2) ​ 3 **Under Alarm Site Settings > Console & Keypad > Video.** a. Toggle to turn on **Enable Other Camera Streams on Device** to view camera live streams on the BK11/BK21 device. 4 **Under Alarm Site Settings > Console & Keypad > Audio.** a. Toggle to turn on **Arm/Disarm Announcement**, **Alarm Trigger Announcement**, **Alarm Raised Announcement**, or **Door Chime** to use those features for the BK11/BK21 device. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-4b7d4e643474cb19ba5619ad4c10ed02d58cd5fb%252F1d343aa56adef7a53c4cff1d23efd07d3a59d8f6.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=8c5e6ba1&sv=2) 5 **In Command, you can also adjust the volume and brightness of the screen and view the device details:** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-e400d58e45be2af6b02134c8a87a73a1414e87e5%252F896e496e8020ac631c58953b4e32c02418d51382.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=12503c2c&sv=2) Last updated 1 day ago Was this helpful? --- # Verkada Monitoring Phone Numbers for Classic Alarms | Classic Alarms | Verkada Help This article is a guide for classic Alarms. Refer to this [article](https://help.verkada.com/new-alarms/alarms-specifications/verkada-monitoring-phone-numbers) if you have new Alarms. See [New Alarms vs Classic Alarms](https://help.verkada.com/new-alarms/new-alarms-vs-classic-alarms) if you are unsure which version of Alarms you have. When a Verkada alarm is triggered: 1 **Our monitoring team will contact users who are specified in your org’s** [**contact list**](https://help.verkada.com/classic-alarms/configuration-and-setup/configure-classic-alarms-site-settings) **.** 2 **The team will verify the nature of the emergency and determine if emergency dispatch is needed.** Users on the notifications list should save these numbers to their contact list as "Verkada Monitoring". For organizations using both classic Alarms and new Alarms, save this number as ’Classic Alarms - Verkada Monitoring." These are the numbers that we use to notify you of an emergency: ### [](https://help.verkada.com/classic-alarms/networking-and-reports/verkada-monitoring-phone-numbers-for-classic-alarms#voice) Voice +16193044016 #### [](https://help.verkada.com/classic-alarms/networking-and-reports/verkada-monitoring-phone-numbers-for-classic-alarms#sms) SMS +16193298928 +16193298846 +16193298736 Last updated 23 hours ago Was this helpful? --- # Configure Static IP Addresses for Cameras | Verkada Cameras | Verkada Help [Verkada cameras](https://www.verkada.com/security-cameras/) can be configured with a static IP to ensure that your cameras maintain consistent network communication without relying on dynamic IP allocation protocols, such as the Dynamic Host Configuration Protocol (DHCP). Verkada cameras support private IP addresses, as defined in [RFC 1918](https://datatracker.ietf.org/doc/rfc1918/) . This means that only private IP ranges specified in the RFC, such as 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16, are compatible with the static IP configuration. ### [](https://help.verkada.com/verkada-cameras/hardware-installation/advanced-installation/configure-static-ip-addresses-for-cameras#before-you-begin) Before you begin To configure a static IP address on a camera, the camera must initially connect to Command and update to the latest firmware using DHCP. Once the camera’s update process is complete, it will be able to receive the new static IP configuration. * * * [](https://help.verkada.com/verkada-cameras/hardware-installation/advanced-installation/configure-static-ip-addresses-for-cameras#configure-a-static-ip-address) Configure a static IP address --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Only [Site Admins](https://help.verkada.com/verkada-cameras/configuration-and-setup/roles-and-permissions-for-cameras) can enable this feature or modify static IP configurations. 1 **In Verkada Command, go to All Products > Cameras .** 2 **Select a camera to configure.** 3 **At the right of the camera feed, click the Settings icon.** 4 **Under Device > Camera IP, click the dropdown and select Manual.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1795869993-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FylYKicREo6JpuOJH4teK%252Fuploads%252Fgit-blob-3a6b965e5af70d0daedfce95b2a7b9260dffb81a%252F2137cb1b6f4347624b54faefb7718b8e86f3adc2.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=7c33c951&sv=2) 5 **On Manual IP Settings, enter the static IP addressing information.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1795869993-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FylYKicREo6JpuOJH4teK%252Fuploads%252Fgit-blob-02557b161ed1ea997aa03f443043be4f4526b2f1%252F68d9c3f35be8ff594326ac92c7fb92bffcf51ab3.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=52b6479b&sv=2) 6 **Click Save to save the configuration. This change is immediately applied to the camera interface.** ### [](https://help.verkada.com/verkada-cameras/hardware-installation/advanced-installation/configure-static-ip-addresses-for-cameras#bulk-configuration) Bulk configuration For large deployments requiring static IP addressing, you can configure camera IP addresses in bulk by uploading a comma-separated value (CSV) file. To perform this bulk operation, navigate to the **Cameras** section of Command and perform the following: 1 **In Verkada Command, go to All Products > Cameras .** 2 **On the left navigation, click Camera Settings.** 3 **Click Bulk Static IP > Download CSV Template to download a CSV file with the necessary columns to configure static IP for cameras.** 4 **Edit the CSV file to add the camera serials and IP address configurations required and upload the file.** 5 **Once you upload the CSV file, you can make additional edits on the preview table shown on Command before saving your changes.** * * * [](https://help.verkada.com/verkada-cameras/hardware-installation/advanced-installation/configure-static-ip-addresses-for-cameras#recovery-mechanisms) Recovery mechanisms ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- In case of any configuration mistakes or network changes, cameras have a recovery mechanism. The camera performs the following checks at regular intervals to ensure connectivity. In case any of these tests fail, the camera falls back to the DHCP operation. **Recovery Mechanism** **How to Perform this Task** **On the subnet, verify there is no duplicate IP conflict** Send Address Resolution Protocol (ARP) requests for the configured camera IP. If the camera receives an ARP request, the reply it considers it as a duplicate IP conflict. **Verify there is a default gateway** Send ARP requests for the configured gateway IP. If no reply is received by the camera, the gateway is considered unreachable. **DNS resolution is operational for Verkada domains** Perform Domain Name Server (DNS) lookups for Verkada domains. In case the camera doesn’t receive a response from any of the domains, this test fails. **SSL/TLS sessions can be established with the required endpoints** Send HyperText Transfer Protocol Secure (HTTPS) requests to the Verkada endpoints required for camera operation. In case the camera is unable to perform a Transport Layer Security (TLS) handshake with any of the endpoints, or in case there is any error while performing this handshake, this makes the test fail. ### [](https://help.verkada.com/verkada-cameras/hardware-installation/advanced-installation/configure-static-ip-addresses-for-cameras#endpoints-for-dns-tests) Endpoints for DNS tests The following list of endpoints is used for DNS tests, as these are critical for camera operation. For a full list of endpoints, see [Video Security Network Settings](https://help.verkada.com/verkada-cameras/camera-specifications/camera-network-settings) . Copy api.control.verkada.com - TCP/443 relay.control.verkada.com - TCP/443 index.control.verkada.com - TCP/443 firmware.control.verkada.com - TCP/443 Update.control.verkada.com - TCP/443 kinesisvideo.us-west-2.amazonaws.com - UDP/443 ### [](https://help.verkada.com/verkada-cameras/hardware-installation/advanced-installation/configure-static-ip-addresses-for-cameras#endpoint-for-tls-tests) Endpoint for TLS tests For TLS tests, only the first endpoint is used. In case the camera is unable to establish a TLS connection with the **api.control.verkada.com** endpoint, it falls back to the DHCP operation. * * * [](https://help.verkada.com/verkada-cameras/hardware-installation/advanced-installation/configure-static-ip-addresses-for-cameras#troubleshooting) Troubleshooting ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- 1 **If the camera encounters any issues during these checks, it attempts to fall back to its default DHCP operation and perform the connectivity tests listed above.** 2 **If the DHCP connection fails, the camera retries using the static IP configuration.** 3 **If the camera fails to connect again while using its static IP configuration, the camera alternates between static IP and DHCP operations in exponential backoff increments, ranging from 20 seconds up to 1 hour.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1795869993-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FylYKicREo6JpuOJH4teK%252Fuploads%252Fgit-blob-c387e70e82b63b92ee5d0ea44c77d38b2d413912%252F92a3759374339ad658e0c5426df55aba53e80f8c.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=2368cf0c&sv=2) If the camera successfully connects to Verkada Command using DHCP, it continues to operate on DHCP until it is rebooted via Command or by power cycling the camera. Last updated 1 day ago Was this helpful? --- # Bring Your Own Data Plan | Connectivity | Verkada Help As a customer, you have the option to bring your own (BYO) data plan to use with the GC31 Cellular Gateway. In this case, you don’t need to purchase a Verkada data license. When the GC31 is using a customer-provided SIM: * The gateway does not limit traffic to third party devices * [Smart data usage](https://help.verkada.com/connectivity/cellular-data-options/smart-data-usage) can be disabled, which allows: * Cloud backup and RTSP to be enabled on connected Verkada cameras * Video streaming to be enabled on BK11/21 Alarm Keypads and BC82 Alarm Consoles [](https://help.verkada.com/connectivity/cellular-data-options/bring-your-own-data-plan#dual-sim-with-auto-sim-failover) Dual SIM with auto SIM failover ------------------------------------------------------------------------------------------------------------------------------------------------------------- The GC31 and GC31-E have [2 SIM slots](https://help.verkada.com/connectivity/configuration-and-setup/cellular-gateway-dual-sim-support) each: * Slot 1 (Primary)—Default * Slot 2 (Secondary)—Has pre-inserted Verkada data SIM We recommend inserting your own SIM card in slot 1 and keeping the Verkada SIM card in slot 2. The customer-provided SIM acts as the **primary** and fails over to the Verkada SIM if needed. Customers can also insert their own SIM cards in both slots and configure which slot is primary. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1814166542-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FiAGnzScvko5PkG7YBy3i%252Fuploads%252Fgit-blob-2083b376745d252afd8b4a2ee46f16a7649f71e0%252F712a41ee3eac38e02e909c84277012f68e8c9cea.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=50ba8351&sv=2) [](https://help.verkada.com/connectivity/cellular-data-options/bring-your-own-data-plan#tested-carriers) Tested carriers ----------------------------------------------------------------------------------------------------------------------------- The GC31 is compatible with SIM cards from most major carriers across the world. The following carriers have been tested and verified by Verkada. Other carriers may also be compatible but have not been tested by Verkada. **Country** **Carrier** US Verizon, T-Mobile, AT&T Canada Telus, Bell, Rogers UK Three, Vodafone, EE Australia Optus, Telstra, Vodafone [](https://help.verkada.com/connectivity/cellular-data-options/bring-your-own-data-plan#faqs) FAQs ------------------------------------------------------------------------------------------------------- How does the Verkada SIM act as a failover?[](https://help.verkada.com/connectivity/cellular-data-options/bring-your-own-data-plan#how-does-the-verkada-sim-act-as-a-failover) In the case that your own SIM (primary SIM) disconnects from the tower, the device has a mechanism that constantly runs to monitor the connectivity. Once it senses a disconnect, it fails over to the Verkada SIM card (secondary SIM). The Verkada SIM can help ensure the gateway is still reachable if your main network is down. How does the device know when to failover to the secondary SIM?[](https://help.verkada.com/connectivity/cellular-data-options/bring-your-own-data-plan#how-does-the-device-know-when-to-failover-to-the-secondary-sim) The device has a state machine that constantly monitors SIM activity. For details, see [GC31 Cellular Gateway Dual-SIM Support](https://help.verkada.com/connectivity/configuration-and-setup/cellular-gateway-dual-sim-support) . How can I manually choose the APN my data SIM needs to connect to?[](https://help.verkada.com/connectivity/cellular-data-options/bring-your-own-data-plan#how-can-i-manually-choose-the-apn-my-data-sim-needs-to-connect-to) You can access the GC31’s local server page to set manual APN details. Learn more about the [GC31 local server](https://help.verkada.com/connectivity/configuration-and-setup/access-the-cellular-gateway-local-server-page) . Last updated 17 hours ago Was this helpful? --- # Gateway Monthly Data Usage Alerts | Connectivity | Verkada Help Each Verkada gateway enables the user to track the amount of data used by the gateway and any connected devices. You can configure a gateway to trigger an alert when monthly data usage exceeds a preset threshold. **Required.** You need Site Admin permissions to create gateway alerts. Site Admins can designate Site Viewers as alert recipients. ### [](https://help.verkada.com/connectivity/events-and-alerts/gateway-monthly-data-usage-alerts#create-alert-greater-than-events) **Create Alert > Events** 1 **Log in to Verkada Command.** 2 **On the Command homepage, left navigation, click Alerts .** 3 **On the Alerts page, next to My Alerts, click .** 4 **On Select Event, choose Gateway > Monthly Data Usage.** 5 **On Gateways:** a. Choose to receive alerts from **All Gateways, Sites,** or **Individual Gateways.** b. Click **Done** and continue with the alert [recipients](https://help.verkada.com/connectivity/events-and-alerts/gateway-monthly-data-usage-alerts#h_5f5fa7261e) . ### [](https://help.verkada.com/connectivity/events-and-alerts/gateway-monthly-data-usage-alerts#create-alert-greater-than-data-usage-threshold) **Create Alert > Data Usage Threshold** 1 **Select the dropdown menu to choose the start date for the monthly usage cycle.** 2 **Set the data threshold that will trigger the alert.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1814166542-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FiAGnzScvko5PkG7YBy3i%252Fuploads%252Fgit-blob-66026d798e0641ee99dc536e29eed274c7dfc78b%252F6f9682b10772eb64c51dc133a31d986f1e900762.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=7156ff71&sv=2) **Note:** The data threshold is a device-level alert. Users will be notified for each device that crosses the threshold. ### [](https://help.verkada.com/connectivity/events-and-alerts/gateway-monthly-data-usage-alerts#create-alert-greater-than-recipients) **Create Alert > Recipients** 1 **On Recipients, you can search for and select other Command users individually or you can assign the alert to a group.** 2 **Select the dropdown menu next to a user or group to choose their notification method(s). Recipients can be notified either via a push notification, SMS, or email.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1814166542-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FiAGnzScvko5PkG7YBy3i%252Fuploads%252Fgit-blob-a30e5c666efe865b169b36f277c2ab798ad76c5d%252F3a9609d9912905edd0f35abfff403a95e0b820c8.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=3deca5d7&sv=2) 3 **(Optional) By default, you will be added to the alert created. To remove yourself, select the dropdown menu and click Delete.** 4 **Click Done and continue with the alert** [**notification schedule**](https://help.verkada.com/connectivity/events-and-alerts/gateway-monthly-data-usage-alerts#h_f283b9a7f4) **.** **Note:** Any recipient added to this alert will see it appear under the Shared Alerts section of their Alerts page. ### [](https://help.verkada.com/connectivity/events-and-alerts/gateway-monthly-data-usage-alerts#create-alert-greater-than-notification-schedule) **Create Alert > Notification Schedule** 1 **On Notification Schedule, you must specify what days and times you want alerts to be sent. By default, events are generated 24/7.** ​ ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1814166542-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FiAGnzScvko5PkG7YBy3i%252Fuploads%252Fgit-blob-b9042c786a9dd12580abefdd20f412fe59cbac5e%252F7b61969c185d482c85ec3b7f15a687d75aee8d13.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=ad0e8a77&sv=2) 2 **Click Done and and continue with the alert** [**device actions**](https://help.verkada.com/connectivity/events-and-alerts/gateway-monthly-data-usage-alerts#h_32891fdcd2) **or** [**finish the alert**](https://help.verkada.com/connectivity/events-and-alerts/gateway-monthly-data-usage-alerts#h_f63a98f8d6) **.** ### [](https://help.verkada.com/connectivity/events-and-alerts/gateway-monthly-data-usage-alerts#create-alert-greater-than-device-action) Create Alert > Device Action In addition to notifying individuals, you can configure your horn speaker to play when an alert is triggered. These alerts can be text-to-speech or an uploaded MP3 file. 1 **On Device Action, select the horn speaker(s) you want to play your message.** 2 **Select your device’s notification preference (Text to Speech or Audio File).** a. For **Text to Speech,** enter the desired message up to 200 characters. b. For **Audio File,** drag and drop the file or click **choose a file** to upload your audio clip. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1814166542-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FiAGnzScvko5PkG7YBy3i%252Fuploads%252Fgit-blob-6eebd070cac52d81c895573628cb7b21ba245804%252Fbd7aa4597a411933461874e312ac1e72683f4dab.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=63cd4d14&sv=2) 3 **Click Done and continue with** [**finish the alert**](https://help.verkada.com/connectivity/events-and-alerts/gateway-monthly-data-usage-alerts#h_f63a98f8d6) **.** ### [](https://help.verkada.com/connectivity/events-and-alerts/gateway-monthly-data-usage-alerts#finish-the-alert) **Finish the alert** 1 **Click Next on the bottom right of the configuration window once you have configured all the desired alert settings.** 2 **Enter a descriptive name for the alert.** 3 **Click Done and you will start to receive alerts.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1814166542-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FiAGnzScvko5PkG7YBy3i%252Fuploads%252Fgit-blob-75fcc30636d14fdd34cc9e376db710c1542f4ef2%252F943420792c6bfe40aee47eab735038e52669e4ac.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=2b507181&sv=2) Last updated 19 hours ago Was this helpful? --- # Enable Historical GPS Data on GC31-E Gateways | Connectivity | Verkada Help Verkada Outdoor Cellular Gateways can report their location at regular intervals. When this feature is enabled, the Gateway stores location data in the cloud, allowing users to view the historical routes of Mobile Gateway deployments directly in Command. This feature is helpful for investigations as well as general vehicle tracking. Only Cellular Gateway devices can report GPS coordinates. This feature is not available on Wi-Fi Gateways. * * * [](https://help.verkada.com/connectivity/configuration-and-setup/enable-historical-gps-data-on-gc31-e-gateways#enable-gateway-gps-history) Enable Gateway GPS History -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ### [](https://help.verkada.com/connectivity/configuration-and-setup/enable-historical-gps-data-on-gc31-e-gateways#organization-level) Organization level To activate the GPS History functionality on your cellular gateway, you first need to enable the feature for your organization. 1 **In Verkada Command, go to All Products > Admin.** 2 **Select Feature Manager.** 3 **Under Gateway > Gateway GPS History, select Enabled from the dropdown menu.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1814166542-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FiAGnzScvko5PkG7YBy3i%252Fuploads%252Fgit-blob-5cc74ce7b63608610337145f2f61aadb41273dfd%252F78bce3c1d4add7019b37818ba85ce54a4bbd846a.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=4de7c441&sv=2) ### [](https://help.verkada.com/connectivity/configuration-and-setup/enable-historical-gps-data-on-gc31-e-gateways#verkada-cellular-gateway) Verkada Cellular Gateway 1 **In Verkada Command, go to All Products > Gateways.** 2 **Select the gateway you want to configure.** 3 **In the top right, click Settings.** 4 **Under GPS > GPS History, select On from the dropdown menu. Once enabled, you can access the feature from the gateway details page.** The gateway will begin reporting historical GPS coordinates, which can assist with investigations and general vehicle tracking. * * * [](https://help.verkada.com/connectivity/configuration-and-setup/enable-historical-gps-data-on-gc31-e-gateways#view-signal-coverage-data-from-gps-history) View signal coverage data from GPS History ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 1 **In Verkada Command, go to All Products > Gateways.** 2 **Select the gateway you want to view.** 3 **Click GPS History.** a. Toggle on **Signal Strength** to view the historical carrier signal data along the gateway’s route. b. Once toggled on, you can view carrier information along the gateway’s route. * * * [](https://help.verkada.com/connectivity/configuration-and-setup/enable-historical-gps-data-on-gc31-e-gateways#faq) FAQ ---------------------------------------------------------------------------------------------------------------------------- How often does the gateway collect GPS data?[](https://help.verkada.com/connectivity/configuration-and-setup/enable-historical-gps-data-on-gc31-e-gateways#how-often-does-the-gateway-collect-gps-data) The GC31-E samples GPS data every 10 seconds. How often is GPS data uploaded to the cloud?[](https://help.verkada.com/connectivity/configuration-and-setup/enable-historical-gps-data-on-gc31-e-gateways#how-often-is-gps-data-uploaded-to-the-cloud) GPS data is uploaded to the cloud in two-minute intervals. Is cellular connectivity required to upload GPS data to the cloud?[](https://help.verkada.com/connectivity/configuration-and-setup/enable-historical-gps-data-on-gc31-e-gateways#is-cellular-connectivity-required-to-upload-gps-data-to-the-cloud) GPS sampling occurs without cellular connectivity, but uploading the data to the cloud requires a cellular connection on the GC31-E. How accurate is the reported GPS location?[](https://help.verkada.com/connectivity/configuration-and-setup/enable-historical-gps-data-on-gc31-e-gateways#how-accurate-is-the-reported-gps-location) The Cellular Gateway’s GPS provides an accuracy of approximately ±50 meters. Last updated 18 hours ago Was this helpful? --- # Configure a BX21 Wireless Relay | Classic Alarms | Verkada Help The [Verkada BX21 wireless relay](https://docs.verkada.com/docs/wireless-relay-bx21-datasheet.pdf) is a controlled alarm output device that allows customers to connect 12/24 volt sirens, strobes, or other alarm signaling devices. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-4120798c6ee3fd99a860e5a888a744b50bb9d771%252F397a7d7882c42c53e68be7b0810e71ec3a079c2a.png%3Falt%3Dmedia&width=300&dpr=4&quality=100&sign=34110412&sv=2) **Interface/Connectors** 1\. Relay Output (NO, COM, NC)\* ​ 2\. (Optional) Wired Signal Input (GND, IN) 3\. Relay Power Input (GND, 12-24VDC) 4\. Test/Pairing Button \*12VDC operates at 2.5A Max \*24VDC operates at 1.25A Max [](https://help.verkada.com/classic-alarms/hardware-installation/configure-a-bx21-wireless-relay#supported-devices) Supported devices ------------------------------------------------------------------------------------------------------------------------------------------ **Output devices** The BX21 has 1 NO/NC alarm output, with a max power draw of 2.5A. The most common output devices are sirens, bells, and strobe lights that are activated when an alarm is raised. In Verkada Command, you can select outputs to turn on in response to an alarm. When an alarm is raised, the relay supplies power to those outputs. Multiple output devices can be wired in parallel so that activating a single output can turn on several devices simultaneously. **Signal devices** The BX21 supports 2-wire devices, such as door contacts, that are wired to the input and GND terminal. It does not matter which wire goes into which terminal. **Power devices** The BX21 takes a 12VDC at 2.5A or a 24VDC at 1.25A. This is connected to the GND and 12–24v terminals. **Recommendation**. If you use an output device that draws a lot of current, the max amperage power supply should be used to avoid problems. [](https://help.verkada.com/classic-alarms/hardware-installation/configure-a-bx21-wireless-relay#add-edit-the-relay-as-an-output-device) Add/edit the relay as an output device ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ When you add a relay to an alarm site, an output is auto configured. 1 **In Verkada Command, go to All Products > Alarms.** 2 **Go to your Alarm site settings > Alarm Actions > Wireless Relay Outputs > Add Output.** [](https://help.verkada.com/classic-alarms/hardware-installation/configure-a-bx21-wireless-relay#configure-an-input-in-command) Configure an input in Command ------------------------------------------------------------------------------------------------------------------------------------------------------------------ 1 **In Verkada Command, go to All Products > Alarms.** 2 **Go to your Alarm site settings > Devices > Add Device > Add Wired Input.** 3 **Configure the input and select the appropriate BX21.** Last updated 23 hours ago Was this helpful? --- # Configure Static IP Addresses for Command Connector | Command Connector | Verkada Help Command Connectors can be configured with a static IP to ensure that they maintain consistent network communication without relying on dynamic IP allocation protocols, such as the Dynamic Host Configuration Protocol (DHCP). Command Connectors support private IP addresses, as defined in [RFC 1918](https://datatracker.ietf.org/doc/rfc1918/) . This means only private IP ranges specified in the RFC, such as 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16, are compatible with the static IP configuration. ### [](https://help.verkada.com/command-connector/configuration-and-setup/configure-static-ip-addresses-for-command-connector#before-you-begin) Before you begin To configure a static IP address on a Command Connector, it must initially connect to Command and update to the latest firmware using DHCP. Once the update process is complete, you can configure a static IP. * * * [](https://help.verkada.com/command-connector/configuration-and-setup/configure-static-ip-addresses-for-command-connector#configuration) Configuration ----------------------------------------------------------------------------------------------------------------------------------------------------------- Only [Site Admins](https://help.verkada.com/verkada-cameras/configuration-and-setup/roles-and-permissions-for-cameras) can enable or modify static IP configurations. 1 **In Verkada Command, go to All Products > Cameras .** 2 **Select a Command Connector to configure.** 3 **On the right, click the Settings.** 4 **Under General > Command Connector IP, click the dropdown and select Manual.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3780751499-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FNje42M0OzzbT2nhzkB3K%252Fuploads%252Fgit-blob-60c8fc4121c40953e9081f32f33665a8e2a8ea6a%252F5704f9ceacc309454fe8f3361862299edc23be0e.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=78274700&sv=2) 5 **On Manual IP Settings, enter the static IP addressing information.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3780751499-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FNje42M0OzzbT2nhzkB3K%252Fuploads%252Fgit-blob-02557b161ed1ea997aa03f443043be4f4526b2f1%252F68d9c3f35be8ff594326ac92c7fb92bffcf51ab3.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=7602f2cd&sv=2) 6 **Click Save.** * * * [](https://help.verkada.com/command-connector/configuration-and-setup/configure-static-ip-addresses-for-command-connector#recovery-mechanisms) Recovery mechanisms ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- In case of any configuration mistakes or network changes, Command Connectors have a recovery mechanism. The Command Connector performs the following checks at regular intervals to ensure connectivity. In case any of these tests fail, it falls back to the DHCP operation. **Recovery Mechanism** **How to Perform this Task** **On the subnet, verify there is no duplicate IP conflict** Send Address Resolution Protocol (ARP) requests for the configured Command Connector IP. If the Command Connector receives an ARP request, it considers the reply a duplicate IP conflict. **Verify there is a default gateway** Send ARP requests for the configured gateway IP. If no reply is received by the Command Connector, the gateway is considered unreachable. **DNS resolution is operational for Verkada domains** Perform Domain Name Server (DNS) lookups for Verkada domains. In case the Command Connector doesn’t receive a response from any of the domains, this test fails. **SSL/TLS sessions can be established with the required endpoints** Send HyperText Transfer Protocol Secure (HTTPS) requests to the Verkada endpoints required for Command Connector operation. In case the Command Connector is unable to perform a Transport Layer Security (TLS) handshake with any of the endpoints, or in case there is any error while performing this handshake, this makes the test fail. ### [](https://help.verkada.com/command-connector/configuration-and-setup/configure-static-ip-addresses-for-command-connector#endpoints-for-dns-tests) Endpoints for DNS tests The following list of endpoints is used for DNS tests in US organizations, for other regions their equivalent endpoint will be used. For a full list of endpoints, see [Video Security Network Settings](https://help.verkada.com/command-connector/command-connector-network-settings) . Copy api.control.verkada.com - TCP/443 vprovision.command.verkada.com - TCP/443 For TLS tests, only the first endpoint is used. In case the Command Connector is unable to establish a TLS connection with the **api.control.verkada.com** endpoint, it falls back to the DHCP operation. * * * [](https://help.verkada.com/command-connector/configuration-and-setup/configure-static-ip-addresses-for-command-connector#troubleshooting) Troubleshooting --------------------------------------------------------------------------------------------------------------------------------------------------------------- 1 **If the Command Connector encounters any issues during these checks, it attempts to fall back to its default DHCP operation and perform the connectivity tests listed above.** 2 **If the DHCP connection fails, the Command Connector retries using the static IP configuration.** 3 **If the Command Connector fails to connect again while using its static IP configuration, it alternates between static IP and DHCP operations in exponential backoff increments, ranging from 20 seconds up to 1 hour.** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3780751499-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FNje42M0OzzbT2nhzkB3K%252Fuploads%252Fgit-blob-c387e70e82b63b92ee5d0ea44c77d38b2d413912%252F92a3759374339ad658e0c5426df55aba53e80f8c.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=337824a2&sv=2) If the Command Connector successfully connects to Verkada Command using DHCP, it continues to operate on DHCP until it is rebooted via Command or by power cycling the Command Connector. Last updated 1 day ago Was this helpful? --- # Use a PoE Switch with Outdoor Gateways | Connectivity | Verkada Help You can use a PoE switch with the outdoor gateway to increase the power and/or number of ports for downstream devices such as Verkada cameras. We recommend following this topology: ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1814166542-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FiAGnzScvko5PkG7YBy3i%252Fuploads%252Fgit-blob-45e0d56f902440ee51e4526dde77868dfaa43ac3%252F2be38605698bb41881c927171fe751276d354ea0.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=aa21e3a7&sv=2) In this topology, the customer-provided PoE switch sends power to the gateway’s PoE **In** port and gets data back from the same port. To enable this setup, you need to change the PoE **In** port configuration to LAN. * * * ### [](https://help.verkada.com/connectivity/configuration-and-setup/use-a-poe-switch-with-outdoor-gateways#change-poe-in-port-configuration-to-lan) Change PoE In port configuration to LAN **Note:** This configuration is only available on outdoor gateways. 1 **In Verkada Command, go to All Products > Gateways .** 2 **Select the gateway you want to configure.** 3 **In the top right, click Settings .** 4 **Under Network > Connection, select Local Area Network (LAN).** ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F1814166542-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FiAGnzScvko5PkG7YBy3i%252Fuploads%252Fgit-blob-530d02c5c3701bd87237fbc9c88a1c2d96e72231%252Faa4919508c82e5db6888019937dc7a782db7c34f.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=c3929604&sv=2) **Note:** The PoE IN port on the outdoor gateways is set to WAN by default. 5 **Click Apply, then Confirm to save.** Last updated 17 hours ago Was this helpful? --- # Set Up the BZ11 Horn Speaker with Classic Alarms | Classic Alarms | Verkada Help This article is a guide for classic Alarms. Refer to this [article](https://help.verkada.com/new-alarms/configuration-and-setup/set-up-the-bz11-horn-speaker) if you have new Alarms. See [New Alarms vs Classic Alarms](https://help.verkada.com/new-alarms/new-alarms-vs-classic-alarms) if you are unsure which version of Alarms you have. * * * You can use the Verkada [BZ11 horn speaker](https://docs.verkada.com/docs/horn-speaker-bz11-datasheet.pdf) with and without Verkada cameras, and it can also be paired with an Alarms license to provide advanced functionality, including [agent talk down](https://help.verkada.com/classic-alarms/configuration-and-setup/set-up-the-bz11-horn-speaker-with-classic-alarms#h_6b24a7b152) . As a standalone device, you can use it from the **Devices** page to initiate a call from Verkada Command to the speaker. When associated with a Verkada camera, you can use the camera to provide the Command user with the necessary context for the talk-down. Admins can configure custom audio files to play through the BZ11 when an alarm is raised. You can also enable Agent Talk Down, allowing Verkada’s video monitoring agents to respond to threats and live talk-down through the BZ11 to deter intruders. * * * [](https://help.verkada.com/classic-alarms/configuration-and-setup/set-up-the-bz11-horn-speaker-with-classic-alarms#initiate-call-from-devices-page) Initiate call from Devices page ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 1 **In Verkada Command, go to All Products > Devices.** 2 **Select your BZ11.** 3 **Click Play to play a short test sound.** 4 **Click Phone to initiate the call.** You can adjust the volume and microphone settings using the sliders and check box under the speaker settings. * * * [](https://help.verkada.com/classic-alarms/configuration-and-setup/set-up-the-bz11-horn-speaker-with-classic-alarms#initiate-easy-from-camera-live-stream) Initiate easy from camera live stream ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- You need to associate a camera with the speaker before you can initiate a talk down from a camera. ### [](https://help.verkada.com/classic-alarms/configuration-and-setup/set-up-the-bz11-horn-speaker-with-classic-alarms#pair-cameras) Pair cameras 1 **In Verkada Command, go to All Products > Devices.** 2 **Select your horn speaker.** 3 **Under the speaking settings, click Select Cameras.** a. Select the camera(s) to add. b. Click **Done.** ### [](https://help.verkada.com/classic-alarms/configuration-and-setup/set-up-the-bz11-horn-speaker-with-classic-alarms#initial-call) Initial call 1 **In Verkada Command, go to All Products > Devices.** 2 **Select your horn speaker.** 3 **Select your camera from the Paired Cameras list.** 4 **At the bottom right of the live feed, click to initiate the call.** 5 **(Optional) If multiple speaker devices are configured for the same camera, click to select the specific device you want to call.** * * * [](https://help.verkada.com/classic-alarms/configuration-and-setup/set-up-the-bz11-horn-speaker-with-classic-alarms#enable-the-speaker-to-be-an-alarm-output) Enable the speaker to be an Alarm output ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- By default, play audio is disabled when the speaker is first added to an alarm site. To enable the speaker to play when an alarm is raised: 1 **In Command, go to All Products > Classic Alarms.** 2 **Select an alarm.** 3 **At the top, click the Settings tab.** 4 **Go to Alarm Responses > Alarm Actions > Enable Play Audio. This setting plays the default alert message,** _**Alarm has been raised please leave the premise immediately**_**, when an alarm has been raised. You can customize this message by** [**uploading your own .mp3 file**](https://help.verkada.com/classic-alarms/configuration-and-setup/set-up-the-bz11-horn-speaker-with-classic-alarms#h_296f284a3b) **.** * * * [](https://help.verkada.com/classic-alarms/configuration-and-setup/set-up-the-bz11-horn-speaker-with-classic-alarms#upload-a-custom-mp3-file) Upload a custom MP3 file --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Uploading a custom MP3 file requires an [alarm location license](https://help.verkada.com/command/licensing-and-warranty/manage-your-licenses) . 1 **In Command, go to All Products > Classic Alarms.** 2 **Select a site.** 3 **At the top, click Settings.** 4 **Under Alarm Responses > Alarm Actions > Enable Play Audio > Upload Audio File upload your file.** The BZ11 is only compatible with .mp3 files and the file must be under 20 MB. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F2326462210-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F9tIFgMOGbY4p9wWaKQhl%252Fuploads%252Fgit-blob-0aa366308423ba799dcca95616d26a1c44fc5ea2%252F732ddb476618dd9ab10d199653ed7661ab942429.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=e8a23ab3&sv=2) * * * [](https://help.verkada.com/classic-alarms/configuration-and-setup/set-up-the-bz11-horn-speaker-with-classic-alarms#configure-agent-talk-down) Configure Agent Talk Down ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Verkada’s video monitoring agents can use agent talk down to initial a call to deter intrudes at a site. The agent will still call the users on the contact list regardless of the outcome of the talk down. 1 **In Command, go to All Products > Classic Alarms.** 2 **Select a site.** 3 **At the top, click Settings.** 4 **Under Alarm Responses > Emergency Dispatch, toggle on Agent Talk Down.** In order for agents to use the speaker, the camera that is associated to the BZ11 must be configured as a context camera or trigger for the Alarms site. Last updated 23 hours ago Was this helpful? --- # Verkada Alarms Monitoring Certificate | New Alarms | Verkada Help An Alarm Monitoring Certificate confirms that Verkada professionally monitors your alarm system and serves as proof for your insurance provider. * * * [](https://help.verkada.com/new-alarms/alarms-specifications/verkada-alarms-monitoring-certificate#obtain-the-certificate) Obtain the certificate ------------------------------------------------------------------------------------------------------------------------------------------------------ [Contact Verkada Support](https://help.verkada.com/command/need-help/contact-verkada-support) with the following information to request your certificate: * **Site name:** Exact name to appear on the certificate. * **Site address:** Complete street address (including city, state, zip, and country of the monitored location). * **Monitoring start date:** The date on which Verkada began monitoring the site. Requests are typically processed within **1–2 business days.** Last updated 22 hours ago Was this helpful? --- # Change a non-Verkada Channel Orientation | Command Connector | Verkada Help Sometimes, non-Verkada camera feeds may appear with an incorrect orientation. The Command Connector provides an easy way to rotate these feeds directly in Command, ensuring proper alignment for better visibility. * * * [](https://help.verkada.com/command-connector/configuration-and-setup/change-a-non-verkada-channel-orientation#configuration) Configuration ------------------------------------------------------------------------------------------------------------------------------------------------ 1 **In Verkada Command, go to All Products > Cameras .** 2 **Select the non-Verkada channel you want to configure.** 3 **At the bottom right, click Settings .** 4 **Under Device > Orientation, click Change.** a. Select an orientation mode. b. Click **Save** to confirm changes. ![](https://help.verkada.com/~gitbook/image?url=https%3A%2F%2F3780751499-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FNje42M0OzzbT2nhzkB3K%252Fuploads%252Fgit-blob-b2d990dab20fe6188d65e50ae8bb34c1c853abe8%252F88cacdfd55ddccaea797014e2b1ea2c357d8d713.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=aa092aea&sv=2) A Command Connector can rotate up to four non-Verkada camera feeds. Only H.264 main and high profiles support camera rotation. Last updated 19 hours ago Was this helpful? ---