<h2>Overview</h2>Beam Groups in ScreenMeet allow organizations to segment access to devices across different teams, use cases, or access levels. This guide walks through how to create, configure, and manage Beam Groups, including access rules, device association using group keys, and lifecycle policies for inactive devices.<hr><h2>1. Viewing Beam Groups</h2>The Beam Groups dashboard provides a list of all active and inactive groups. Each row shows:<ul><li>Group ID and Name</li><li>Number of devices associated</li><li>Whether the group is active</li><li>Access control setting</li><li>Timestamps for creation and last update</li></ul>Clicking a group name opens its detail page, where admins can manage users, view connected devices, and edit group settings.<hr><h2>2. Creating a Beam Group</h2>To create a Beam Group:<ol><li>Go to <a target="_blank" rel="noopener noreferrer nofollow" href="http://console.screenmeet.com">console.screenmeet.com</a></li><li>Navigate to Beam Groups</li><li>Click Create Beam Group</li></ol>Fill out:<ul><li>Name: A unique name for the group</li><li>Who Can Access These Devices:<ul><li>All Agents: All active agents in your org can access these devices</li><li>Organization Administrators Only: Only users with admin privileges</li><li>Specific Users: Access is controlled manually (see Section 5)</li><li>Use External ACL: Access is granted dynamically based on external authorization logic</li></ul></li></ul>Click Create Beam Group to finalize.<hr><h2>3. Group Key and Device Registration</h2>Once the Beam Group is created, you will be presented with a Group Key. This key is required to register devices to that group.<h3>What is the Group Key?</h3><ul><li>The key binds the device to the selected Beam Group.</li><li>It can be used:<ul><li>During manual setup via the Beam client GUI.</li><li>As part of automated deployments through MDM or custom scripts.</li></ul></li></ul><h3>Example Use Cases</h3>Organizations may have multiple Beam Groups such as:<ul><li>IT Admin Machines</li><li>Executive/VIP Devices</li><li>Department-based groupings (Sales, Engineering, etc.)</li></ul>Each group can have different access permissions and purge policies, providing flexibility for how remote access is managed and secured.You can copy or download the key during creation, and retrieve it later by navigating to the group details page.<hr><h2>4. Session Prompt Policy</h2>This determines if the end-user will receive a prompt to accept or deny the session from starting on their device.<ul><li>Default: All groups are initially set to default which does not prompt the end user</li><li>Auto-Detect: ScreenMeet detects whether an end user is present and prompts them if detected</li><li>Always Prompt: Always prompts the end user to accept the session</li><li>Never Prompt: Allows the agent to connect unattended without end-user interaction</li></ul><hr><h2>5. Device Purging Policy</h2>Each group can enforce an optional Device Purging Policy. This automatically removes devices that have remained offline for a specified number of days.<ul><li>Toggle the policy on or off.</li><li>Enter the number of days (e.g., 30 days).</li><li>Devices that do not check in within the duration will be removed from the group.</li></ul>This helps organizations keep their device lists clean and relevant.<hr><h2>6. Editing Beam Group Settings</h2>To make changes to an existing group:<ol><li>Select the group from the list.</li><li>Click Edit Beam Group.</li></ol>You can update:<ul><li>Group name</li><li>Active status</li><li>Access control mode</li><li>Device purging settings</li></ul>Click Save Beam Group after making changes.<hr><h2>7. Assigning Access for Specific Users</h2>If the group uses the Specific Users access mode:<ol><li>Go to the Authorized Users tab.</li><li>Click Add Authorized Users.</li><li>Select users from your org.</li><li>Click Save.</li></ol>To remove access, select users and click Remove access from selected.Important Note on User Visibility: When setting up a Beam Group and selecting "Specific Users" for access control, users with ScreenMeet roles will only appear in the "Add Authorized Users" list after they have become "active." This typically happens when:<ul><li>They log in to <code>console.screenmeet.com</code> for the first time.</li><li>They load the ScreenMeet component through an assigned record page (e.g., in a Salesforce environment).</li></ul>Until one of these actions occurs, even if they have the appropriate ScreenMeet roles assigned, they will not be displayed in the "Specific Users" list because only active users are rendered there.<hr><h2>8. Viewing Devices in a Group</h2>Each Beam Group has a Devices tab displaying all associated devices, including:<ul><li>Status (online or offline)</li><li>Device name and ID</li><li>Domain and OS</li><li>IP address (local and remote)</li><li>Tags, labels, and client version</li></ul>Use search and filters to quickly find devices by name or property.<hr><h2>Summary</h2><table style="min-width: 75px;"><tbody><tr><th colspan="1" rowspan="1">Task</th><th colspan="1" rowspan="1">Location</th><th colspan="1" rowspan="1">Notes</th></tr><tr><td colspan="1" rowspan="1">Create Beam Group</td><td colspan="1" rowspan="1">Beam Groups &gt; Create</td><td colspan="1" rowspan="1">Choose access level, define purging settings if needed</td></tr><tr><td colspan="1" rowspan="1">Copy Group Key</td><td colspan="1" rowspan="1">After creation or group view</td><td colspan="1" rowspan="1">Used in deployments to bind devices to the group</td></tr><tr><td colspan="1" rowspan="1">Edit Group Settings</td><td colspan="1" rowspan="1">Group Detail &gt; Edit</td><td colspan="1" rowspan="1">Update name, access, and lifecycle rules</td></tr><tr><td colspan="1" rowspan="1">Assign Specific Users</td><td colspan="1" rowspan="1">Group Detail &gt; Authorized Users</td><td colspan="1" rowspan="1">Only needed when access mode is set to <code>Specific Users</code>. Users must be active to appear.</td></tr><tr><td colspan="1" rowspan="1">View Connected Devices</td><td colspan="1" rowspan="1">Group Detail &gt; Devices</td><td colspan="1" rowspan="1">Device inventory and connection state</td></tr></tbody></table>

Beam Groups: Setup, Settings, and Access Management

Getting Application from ServiceNow Store

Using your Azure Blob for ScreenMeet File Storage

Minimal Cobrowse Script

Frequently Asked Questions

Timeout Settings

July

Remote Control

IP Access Control Feature

Live Release Notes Q2 2024

Video Chat Integration

Cobrowse Settings

CoBrowse Release Notes Q2 23

Connecting to Mac devices

Connecting to a Device Using Beam

Windows Tools

Starting a session

CoBrowse Release Notes Q1 22

Remote Support Release Notes Q4 24

Clipboard

Release Summer 21 (1.14)

Virtual Agent Integration w/ ScreenMeet

Android SDK Quickstart

Security

Remote Support Release Notes Q3 23

Replay Settings

Custom Copy

CoBrowse Deployments

AI Summary History

Integration Signing Key

Microsoft D365 Release Notes Q4 2022

Replay Release Notes Q2 24

October

Live Settings

ScreenMeet Console Customers

Hosting a Desktop Session

Remote Support Release Notes Q2 23

Creating a Replay Recording

AI Assist Overview

Included Reports and how to add them into Dashboards

Custom Domain

Networking Configuration

AI Summarization

Remote Support

Overview

Remote Support Settings

CoBrowse Release Notes Q2 24

Sign in to console.screenmeet.com

Multiple Domain and Subdomain support

February

File Transfer Settings

Exporting ScreenMeet + Salesforce data to third party visualization tools

Beam Release Notes Q1 24

Regional Geo-Fencing

Custom Branding

AI Assist

Configure API service

Beam Release Notes Q3 23

Joining & Completing a Live Plus session

Egress IP Addresses

Custom URL

Starting a Session from within Salesforce

Settings and Policies

Requirements

How To Install ScreenMeet in Your Genesys Instance

Localization

Configuring Environment Variables

Reviewing a Session

August

Remote Support Release Notes Q1 23

Live Release Notes Q2 22

Release Summer 2020 (1.9)

Device Requirements

System Information

Create Multiple Sessions

ServiceNow Release Notes Q4 24

403 Forbidden while making API request

Manage Beam Group Permission Set

ScreenMeet Platform Release Notes Q3 23

Remote Support Release Notes - Q1 22

Screen Annotation

Creating a Session

Custom Background

Remote Support Release Notes Q2 24

AI Summary Studio

Instructions to Person at End Point Device

Beam Client: Installation, Deployment, and Configuration Guide

Component settings

Customer initiated sessions with a chatbot

ScreenMeet 2024 Release Notes

Package Installation Error - Case-Case Layout: feedLayout is not supported for this layout

Developer Notes (3.0.11)

Starting a Session from Dynamics

ScreenMeet Platform Release Notes Q1 23

Remote Support Release Notes Q2 22