<h3></h3> <h3>Introduction, Scope, and Purpose</h3>Worldwide, a large and growing number of businesses and government agencies rely on ScreenMeet Support Software-as-a-Service (SaaS) to streamline business processes for customer support.ScreenMeet Support makes security the top priority in the design, deployment, and maintenance of our network, platform, and applications. Consequently, ScreenMeet Support is prepared to operate in even the most stringent and secure computing environments.Understanding the security and design parameters of ScreenMeet Support and the underlying communications infrastructure is an important component.The following document provides detailed information on the security infrastructure for ScreenMeet Support support sessions from the agent browser, to the cloud infrastructure, and to the end-user desktop. In addition, it describes the oauth process as well as data storage and retention policies.In accordance with best security and functionality practices, please ensure your network is configured properly, and install and maintain the most up-to-date version of your browser and OS.<h3>Network Configuration</h3>Important: In order to ensure Screenmeet/ScreenMeet Remote Assist works per specification, the following network configurations are needed:-Whitelist “*.screenmeet.com” and “*.scrn.mt” for port 443 via TCP and UDP. Please note that ScreenMeet uses port 443 for multiple protocols, including regular REST/HTTP requests over TLS, Secure WebSockets (WSS), RTP traffic which can be either UDP or TCP, as well as TURN/STUN.You may check your network configuration with our validation tool&nbsp;<a target="_blank" rel="noopener noreferrer nofollow" href="https://integration.screenmeet.com/webrtctest/index.html">available here</a>.<h3>Remote Support - Supported Browsers (Agent)</h3>ScreenMeet Support supports the following browsers and versions for Agent use in support sessions:Chrome: 72+Edge: 17+Safari: 12+<h3>Remote Support - Supported OS&nbsp;(User)&nbsp;</h3>The ScreenMeet Support client supports the following OS and versions on end user devices:Windows: 10, 11 (Requires .NET Framework 4.6.2+)&nbsp;MacOS: 10.14+Linux: Ubuntu 18.04.3+, Redhat 7.6+iOS: 12.3.x+Android: 5.0+Windows Server:&nbsp;Server 2022, Server 2019, &nbsp;Server 2016&nbsp;<h3>Cobrowse&nbsp;</h3>ScreenMeet Cobrowse supports the following browser and versions on the end user devices:Windows: Edge, Chrome, FirefoxMacOS: Safari, Chrome, FirefoxiOS: Safari, ChromeAndroid: Chrome, Firefox<h3>Live Video/Voice</h3>ScreenMeet Live supports the following browsers and versions on the end user devices:Windows: Edge, Chrome, FirefoxMacOS: Safari, Chrome, FirefoxiOS: SafariAndroid: Chrome, Firefox[Chrome vers 79+, Firefox vers 74+, Edge vers 79+, Safari vers 12+]<h3>ScreenMeet Support Cloud Infrastructure&nbsp;</h3>Globally deployed across multiple cloud hosting providers, ScreenMeet Support uses docker for simple and scalable deployment operations.Least Busy ArchitectureScreenMeet Support is designed to utilize the scalability and geographic distribution of its architecture. This means that as Edge servers are brought on-line, the multitenant ScreenMeet Support architecture scales logically. Sessions are assigned to the geo-located least busy resource. Session data from the end-user’s device is routed to the agent’s browser instantly across this architecture and deleted promptly after transmission.<h3>Data Centers</h3>ScreenMeet Support uses standard server instances across multiple cloud providers. ScreenMeet Support is hosted in AWS data centers around the world in North America, Europe, Asia(Japan, South Korea, Singapore) , India, and Australia. ScreenMeet Support does not have physical access to these sites.<h3>Remote Access Policy</h3>ScreenMeet Support maintains a process for remote access which is a privileged access management solution on systems containing customer assets. ScreenMeet Support access management solution includes:<ul><li>Encryption of authentication credentials when stored or transmitted at all times</li><li>Passwords for user-level accounts are not shared between multiple individuals</li><li>Passwords are changed immediately whenever it is believed that an account may have been compromised</li><li>Passwords are not communicated via email messages or other forms of electronic communication, other than one-time use passwords</li><li>Passwords for individual user accounts are not given to, or shared with, someone other than the account owner</li><li>A user’s identity is verified before their password is reset and an email is sent to notify the user that their password was reset</li><li>Procedures exist for tracking and provisioning privileged accounts</li><li>Procedures exist for prompt notification or termination of access or rights in response to organization change</li></ul><h3>Data Security/Encryption</h3>All data throughout operation of the ScreenMeet Support application is SSL encrypted using TLS 1.2 transport security with AES-256-bit encryption. This covers all data transmitted from the remote device to our web servers and from our web servers to the Agent browser and conversely.Further, each session is assigned a unique, 1 time key used to bridge the gap between the Agent and the end user. Finally, on PCs, the application auto-deletes after each session so there is no possibility for further access without the end users’ consent and intent.During a ScreenMeet Support session, data is temporarily written to memory, then sent to the remote Agent’s browser and then deleted. No data is permanently stored or retained on the end user or Agent’s device.Encryption Key ManagementScreenMeet Support's strong encryption key management practices include:<ul><li>Equipment used to generate, store, and archive cryptographic keys is physically protected</li><li>ScreenMeet Support has standards and procedures in place to support all aspects of the key management policy (including recovery, backup, and destroying of keys)</li></ul><h3>Transport Layer Security</h3>All session data is transported as SSL encrypted using TLS 1.2 transport security with AES-256-bit encryption. Rather than using firewall port 80 (standard HTTP Internet traffic) to pass through the firewall, ScreenMeet Support uses firewall port 443 (HTTPS traffic).<h3>Firewall Compatibility</h3>All application traffic uses a secure connection over HTTPS (port 443). There is no firewall configuration that is required for any user.<h3>Post Session Data/File Storage</h3>No session information is retained on the end user’s computer or by ScreenMeet Support. All relevant data is written to the CRM/ITSM platform. Also, any files that are transferred or recordings that are made are also written to the CRM/ITSM platform’s cloud storage.<h3>SSO/OAUTH</h3>ScreenMeet Support lets you use your existing CRM/ITSM platform credentials. You can oauth in via the relevant platform app.

Security

ScreenMeet 2025 Release Notes

403 Forbidden while making API request

404 NO_ACCESS

Installing ScreenMeet for Salesforce

Advanced CSS customization

AI Assist

AI Assist Overview

Overview

AI Release Notes Q4 24

Requirements

AI Summarization

AI Summary History

AI Summary Privacy

AI Summary Studio

Android SDK Quickstart

How-to: Setup the app for Laser Pointer

How-to: Display a video stream to the end-user

Egress IP Addresses

AWS S3 File Storage

Configuring ScreenMeet / Microsoft Entra ID integration

Signing into ScreenMeet console with Microsoft Entra ID (Azure AD)

Beam Client: Installation, Deployment, and Configuration Guide

Beam Groups: Setup, Settings, and Access Management

Beam Release Notes Q1 22

Beam Release Notes Q1 23

Beam Release Notes Q1 24

Beam Release Notes Q2 22

Beam Release Notes Q2 23

Beam Release Notes Q2 24

Beam Release Notes Q3 23

Beam Release Notes Q3 22

Beam Release Notes Q4 22

Beam Release Notes Q4 24

New Remote Support Client for Mac

Canvas

Certificate-Based Device Validation

Clone - Remote Support Release Notes Q4 23

Clone - Test ScreenMeet 2025 Release Notes

File Storage on AWS

Configuring Information Security & PII

Creating a Custom UI

Custom Copy

Cobrowse Demo

CoBrowse Deployments

Events

Hotkeys

Localization

CoBrowse Release Notes Q1 23

CoBrowse Release Notes Q1 22

CoBrowse Release Notes Q1 24

CoBrowse Release Notes Q2 22

CoBrowse Release Notes Q2 23

CoBrowse Release Notes Q2 24

CoBrowse Release Notes Q3 22

CoBrowse Release Notes Q3 23

CoBrowse Release Notes Q3 24

CoBrowse Release Notes Q4 22

CoBrowse Release Notes Q4 23

CoBrowse Release Notes Q4 24

Remote Control

Remove End Cobrowse Button

Cobrowse Script

Cobrowse Settings

Starting a Session with a URL

Configuration and validation troubleshooting

Configure API service

Configure ScreenMeet for a New Salesforce Sandbox

Configure ScreenMeet to only show on specified tables

Configuring Environment Variables

Configuring Webhooks for Data Sync

Connecting to ChromeOS devices

Connecting to Mac devices

Connection Information

Create Multiple Sessions

Creating a Replay Recording

Creating a session

Custom Consent Message

Custom permission configuration for ServiceNow

Custom URL

Custom Windows Tools

Deploying a Pre-installed Client

Developer Notes

Developer Notes (3.0.11)

Device Requirements

Enable ScreenMeet for Omnichannel Chat Widget

Enabling features within the Salesforce + ScreenMeet component