Include tablets and telephone receivers in the access review even when they have no named Command account.
\nVerkada intercom authority depends both on site roles and on receiver configuration. The guide says a user must be configured as a receiver to receive calls. Desk Stations and SIP phones are receivers that are not tied to a Command user and cannot be assigned site roles. Receiver authority includes viewing live intercom video outside calls, unlocking during and outside calls, and talk-down. Reviewing only the organization’s list of named user roles therefore misses a separately configured path to intercom functions.
\nSource: Verkada Help — Roles and Permissions for Intercom.
\nApplies to the receiver permissions documented for Verkada Intercom. Confirm the current role matrix and device configuration; this does not assign permissions or state that every receiver is a named employee.
\nDSE recommends inventorying receivers alongside user accounts during an entrance-access review. Map each tablet, extension, and personal receiver to an accountable owner and approved physical or telephone location. Check whether continuous viewing and out-of-call unlocking are appropriate for that endpoint. Remove stale receiver destinations when a desk, phone extension, or employee role changes, and validate the intended fallback call flow afterward. Treat receiver configuration as an access decision requiring an owner.
\nCompare the receiver list with the approved endpoint inventory and test one authorized receiver’s available functions outside a call. Verify that a removed disposable receiver no longer receives test calls. Record any authority that cannot be expressed through a site-role assignment so future reviews do not silently omit it.
\nVerkada Help — Roles and Permissions for Intercom. Reviewed October 15, 2026.
", "content_text": "Include tablets and telephone receivers in the access review even when they have no named Command account.\nSource facts\nVerkada intercom authority depends both on site roles and on receiver configuration. The guide says a user must be configured as a receiver to receive calls. Desk Stations and SIP phones are receivers that are not tied to a Command user and cannot be assigned site roles. Receiver authority includes viewing live intercom video outside calls, unlocking during and outside calls, and talk-down. Reviewing only the organization’s list of named user roles therefore misses a separately configured path to intercom functions.\nSource: Verkada Help — Roles and Permissions for Intercom.\nApplicability\nApplies to the receiver permissions documented for Verkada Intercom. Confirm the current role matrix and device configuration; this does not assign permissions or state that every receiver is a named employee.\nDSE recommendation\nDSE recommends inventorying receivers alongside user accounts during an entrance-access review. Map each tablet, extension, and personal receiver to an accountable owner and approved physical or telephone location. Check whether continuous viewing and out-of-call unlocking are appropriate for that endpoint. Remove stale receiver destinations when a desk, phone extension, or employee role changes, and validate the intended fallback call flow afterward. Treat receiver configuration as an access decision requiring an owner.\nVerification\nCompare the receiver list with the approved endpoint inventory and test one authorized receiver’s available functions outside a call. Verify that a removed disposable receiver no longer receives test calls. Record any authority that cannot be expressed through a site-role assignment so future reviews do not silently omit it.\nOfficial reference\nVerkada Help — Roles and Permissions for Intercom. Reviewed October 15, 2026.", "content_markdown": "Include tablets and telephone receivers in the access review even when they have no named Command account.\n\n## Source facts\n\nVerkada intercom authority depends both on site roles and on receiver configuration. The guide says a user must be configured as a receiver to receive calls. Desk Stations and SIP phones are receivers that are not tied to a Command user and cannot be assigned site roles. Receiver authority includes viewing live intercom video outside calls, unlocking during and outside calls, and talk-down. Reviewing only the organization’s list of named user roles therefore misses a separately configured path to intercom functions.\n\nSource: [Verkada Help — Roles and Permissions for Intercom](https://help.verkada.com/intercom/getting-started/roles-and-permissions-for-intercom).\n\n## Applicability\n\nApplies to the receiver permissions documented for Verkada Intercom. Confirm the current role matrix and device configuration; this does not assign permissions or state that every receiver is a named employee.\n\n## DSE recommendation\n\nDSE recommends inventorying receivers alongside user accounts during an entrance-access review. Map each tablet, extension, and personal receiver to an accountable owner and approved physical or telephone location. Check whether continuous viewing and out-of-call unlocking are appropriate for that endpoint. Remove stale receiver destinations when a desk, phone extension, or employee role changes, and validate the intended fallback call flow afterward. Treat receiver configuration as an access decision requiring an owner.\n\n## Verification\n\nCompare the receiver list with the approved endpoint inventory and test one authorized receiver’s available functions outside a call. Verify that a removed disposable receiver no longer receives test calls. Record any authority that cannot be expressed through a site-role assignment so future reviews do not silently omit it.\n\n## Official reference\n\n[Verkada Help — Roles and Permissions for Intercom](https://help.verkada.com/intercom/getting-started/roles-and-permissions-for-intercom). Reviewed October 15, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/review-intercom-receiver-authority-even-when-no-command-user-is-assigned/", "url": "https://update.dsesecurity.com/updates/review-intercom-receiver-authority-even-when-no-command-user-is-assigned/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-15" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/review-intercom-receiver-authority-even-when-no-command-user-is-assigned/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Review intercom receiver authority even when no Command user is assigned", "item": "https://update.dsesecurity.com/updates/review-intercom-receiver-authority-even-when-no-command-user-is-assigned/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/review-intercom-receiver-authority-even-when-no-command-user-is-assigned/#article", "identifier": "https://update.dsesecurity.com/updates/review-intercom-receiver-authority-even-when-no-command-user-is-assigned/", "url": "https://update.dsesecurity.com/updates/review-intercom-receiver-authority-even-when-no-command-user-is-assigned/", "headline": "Review intercom receiver authority even when no Command user is assigned", "description": "Include tablets and telephone receivers in the access review even when they have no named Command account.", "abstract": "Include tablets and telephone receivers in the access review even when they have no named Command account.", "articleBody": "Include tablets and telephone receivers in the access review even when they have no named Command account.\nSource facts\nVerkada intercom authority depends both on site roles and on receiver configuration. The guide says a user must be configured as a receiver to receive calls. Desk Stations and SIP phones are receivers that are not tied to a Command user and cannot be assigned site roles. Receiver authority includes viewing live intercom video outside calls, unlocking during and outside calls, and talk-down. Reviewing only the organization’s list of named user roles therefore misses a separately configured path to intercom functions.\nSource: Verkada Help — Roles and Permissions for Intercom.\nApplicability\nApplies to the receiver permissions documented for Verkada Intercom. Confirm the current role matrix and device configuration; this does not assign permissions or state that every receiver is a named employee.\nDSE recommendation\nDSE recommends inventorying receivers alongside user accounts during an entrance-access review. Map each tablet, extension, and personal receiver to an accountable owner and approved physical or telephone location. Check whether continuous viewing and out-of-call unlocking are appropriate for that endpoint. Remove stale receiver destinations when a desk, phone extension, or employee role changes, and validate the intended fallback call flow afterward. Treat receiver configuration as an access decision requiring an owner.\nVerification\nCompare the receiver list with the approved endpoint inventory and test one authorized receiver’s available functions outside a call. Verify that a removed disposable receiver no longer receives test calls. Record any authority that cannot be expressed through a site-role assignment so future reviews do not silently omit it.\nOfficial reference\nVerkada Help — Roles and Permissions for Intercom. Reviewed October 15, 2026.", "datePublished": "2026-10-15T13:31:58+00:00", "dateModified": "2026-10-15T13:36:14+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/review-intercom-receiver-authority-even-when-no-command-user-is-assigned/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/review-intercom-receiver-authority-even-when-no-command-user-is-assigned/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Review intercom receiver authority even when no Command user is assigned" }, "articleSection": [ "Access Control" ], "keywords": [ "Access Control", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Access Control", "url": "https://update.dsesecurity.com/topic/access-control/" } ], "wordCount": 276, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Verkada Help — Roles and Permissions for Intercom", "url": "https://help.verkada.com/intercom/getting-started/roles-and-permissions-for-intercom" } } ] } }