---
title: "Beam Groups: Setup, Settings, and Access Management"
slug: "beam-groups-setup-settings-and-access-management"
description: "Manage Beam Groups in ScreenMeet to control device access, set permissions, and streamline device lifecycle policies for your organization."
updated: 2026-04-28T16:14:31Z
published: 2026-04-28T16:14:31Z
canonical: "docs.screenmeet.com/beam-groups-setup-settings-and-access-management"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.screenmeet.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Beam Groups: Setup, Settings, and Access Management

## Overview

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.

---

## 1. Viewing Beam Groups

The **Beam Groups** dashboard provides a list of all active and inactive groups. Each row shows:

- Group ID and Name
- Number of devices associated
- Whether the group is active
- Access control setting
- Timestamps for creation and last update

Clicking a group name opens its detail page, where admins can manage users, view connected devices, and edit group settings.

---

## 2. Creating a Beam Group

To create a Beam Group:

1. Go to [console.screenmeet.com](http://console.screenmeet.com)
2. Navigate to **Beam Groups**
3. Click **Create Beam Group**

Fill out:

- **Name**: A unique name for the group
- **Who Can Access These Devices**:
  - **All Agents**: All active agents in your org can access these devices
  - **Organization Administrators Only**: Only users with admin privileges
  - **Specific Users**: Access is controlled manually (see Section 5)
  - **Use External ACL**: Access is granted dynamically based on external authorization logic

Click **Create Beam Group** to finalize.

---

## 3. Group Key and Device Registration

Once the Beam Group is created, you will be presented with a **Group Key**. This key is required to register devices to that group.

### What is the Group Key?

- The key binds the device to the selected Beam Group.
- It can be used:
  - During manual setup via the Beam client GUI.
  - As part of automated deployments through MDM or custom scripts.

### Example Use Cases

Organizations may have multiple Beam Groups such as:

- IT Admin Machines
- Executive/VIP Devices
- Department-based groupings (Sales, Engineering, etc.)

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.

---

## 4. Session Prompt Policy

This determines if the end-user will receive a prompt to accept or deny the session from starting on their device.

- Default: All groups are initially set to default which does not prompt the end user
- Auto-Detect: ScreenMeet detects whether an end user is present and prompts them if detected
- Always Prompt: Always prompts the end user to accept the session
- Never Prompt: Allows the agent to connect unattended without end-user interaction

---

## 5. Device Purging Policy

Each group can enforce an optional **Device Purging Policy**. This automatically removes devices that have remained **offline** for a specified number of days.

- Toggle the policy on or off.
- Enter the number of days (e.g., 30 days).
- Devices that do not check in within the duration will be removed from the group.

This helps organizations keep their device lists clean and relevant.

---

## 6. Editing Beam Group Settings

To make changes to an existing group:

1. Select the group from the list.
2. Click **Edit Beam Group**.

You can update:

- Group name
- Active status
- Access control mode
- Device purging settings

Click **Save Beam Group** after making changes.

---

## 7. Assigning Access for Specific Users

If the group uses the **Specific Users** access mode:

1. Go to the **Authorized Users** tab.
2. Click **Add Authorized Users**.
3. Select users from your org.
4. Click **Save**.

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:

- They log in to `console.screenmeet.com` for the first time.
- They load the ScreenMeet component through an assigned record page (e.g., in a Salesforce environment).

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.

---

## 8. Viewing Devices in a Group

Each Beam Group has a **Devices** tab displaying all associated devices, including:

- Status (online or offline)
- Device name and ID
- Domain and OS
- IP address (local and remote)
- Tags, labels, and client version

Use search and filters to quickly find devices by name or property.

---

## Summary

| Task | Location | Notes |
| --- | --- | --- |
| Create Beam Group | Beam Groups > Create | Choose access level, define purging settings if needed |
| Copy Group Key | After creation or group view | Used in deployments to bind devices to the group |
| Edit Group Settings | Group Detail > Edit | Update name, access, and lifecycle rules |
| Assign Specific Users | Group Detail > Authorized Users | Only needed when access mode is set to `Specific Users`. Users must be active to appear. |
| View Connected Devices | Group Detail > Devices | Device inventory and connection state |