<h2>Overview</h2>In order to ensure ScreenMeet works properly in a cloned environment, please follow the steps below.<h3>Confirming successful cloning/transfer of ScreenMeet settings</h3>The steps below are to ensure the cloning process pulled in all of the required ScreenMeet options. In general, with a full cloning process, these values will likely exist though the section below serves as a way to confirm.<ul><li>Ensure that the ScreenMeet application was included in the instance cloning process<ul><li>Add the link below to the end of your ServiceNow URL.</li><li>/now/nav/ui/classic/params/target/sys_store_app_<a target="_blank" rel="noopener noreferrer nofollow" href="http://list.do">list.do</a>%3Fsysparm_query%3DnameSTARTSWITHScreenMeet%26sysparm_first_row%3D1%26sysparm_view%3D%26sysparm_choice_query_raw%3D%26sysparm_list_header_search%3Dtrue</li><li>Example: <a target="_blank" rel="noopener noreferrer nofollow" href="https://ven03265.service-now.com/now/nav/ui/classic/params/target/sys_store_app_list.do%3Fsysparm_query%3DnameSTARTSWITHScreenMeet%26sysparm_first_row%3D1%26sysparm_view%3D%26sysparm_choice_query_raw%3D%26sysparm_list_header_search%3Dtrue">https://ven03265.service-now.com/now/nav/ui/classic/params/target/sys_store_app_list.do%3Fsysparm_query%3DnameSTARTSWITHScreenMeet%26sysparm_first_row%3D1%26sysparm_view%3D%26sysparm_choice_query_raw%3D%26sysparm_list_header_search%3Dtrue</a></li></ul></li><li>Ensure that the application registry for ScreenMeet connect exists<ul><li>Add the link below to the end of your ServiceNow URL or navigate to System oAuth → Application registries</li><li>now/nav/ui/classic/params/target/oauth_entity_<a target="_blank" rel="noopener noreferrer nofollow" href="http://list.do">list.do</a>%3Fsysparm_query%3DnameSTARTSWITHScreenMeet%2520Connect%26sysparm_first_row%3D1%26sysparm_view%3D%26sysparm_choice_query_raw%3D%26sysparm_list_header_search%3Dtrue</li><li>The client secret/application registry entry should look identical to the screenshot below with the proper client secret.</li></ul></li><li>Ensure that the Service account for ScreenMeet was included in the cloning process<ul><li>Ensure that the service account exists and has the requisite ScreenMeet roles</li><li></li></ul><blockquote>IMPORTANT: Ensure that the service account password is the same or reset it / note it for the next section.</blockquote></li><li>Ensure that the preexisting ScreenMeet role assignment is assigned to any/all users.<ul><li>Agents, admins, Service account.</li></ul></li></ul><h2>Service Account Setup</h2>After confirming that the cloning process propagated all of the required settings, the organization will need to be configured.This is primarily due to the fact that it is treated as a new ScreenMeet organization.<ul><li>As a user with the ScreenMeet admin role assigned to your ServiceNow profile<ul><li>navigate to console.screenmeet.com and select ServiceNow</li><li>Login to the instance using the instance URL and your credentials.</li><li>Press “allow” on the ScreenMeet connect prompt.</li></ul></li><li>Once logged in, navigate to Organization → Settings and Policies → ServiceNow configuration.</li><li>Enter the service account username and password for the given organization and press save.</li><li></li></ul><blockquote>IMPORTANT: press configure and validate ServiceNow instance.</blockquote><ul><li></li></ul><blockquote>a successful configuration + validation process is required in order for the integration to work successfully</blockquote><ul><li>If this process fails, generally the service account username or password is invalid</li><li>alternatively, the clone may have not propagated one of the required settings in the section below.</li><li>Once you have configured the service account successfully, the integration should work as expected at a basic level.</li></ul><h2>Service Account Setup</h2>Since the ScreenMeet organization is unique, product features (such as where files are stored, feature enablement, etc) must be reconfigured for that given unique organization.You may go through the organization settings and policies and adjust the settings as desired, or reach out to ScreenMeet via our support desk to import your settings from a pre-existing organization.<ul><li>If you would like us to import the settings to save some time and ensure a 1:1 setup,<ul><li>create a ticket using our portal here: <a target="_blank" rel="noopener noreferrer nofollow" href="https://screenmeet.atlassian.net/servicedesk/customer/portal/2/group/2/create/9">https://screenmeet.atlassian.net/servicedesk/customer/portal/2/group/2/create/9</a></li><li>please provide the instance URL of the source organization and the instance URL of the destination organization.<ul><li>example: please import the settings from <a target="_blank" rel="noopener noreferrer nofollow" href="http://ven03265.service-now.com">ven03265.service-now.com</a> to ven0333333.service-now.com</li><li>Note: we cannot import the ServiceNow Integration settings</li></ul></li></ul></li></ul>

Ensuring Successful Cloning of a New ServiceNow Instance with ScreenMeet Settings

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