<h2>Cobrowse Settings</h2><p>These settings are available in the ScreenMeet console and apply to all Cobrowse sessions started by a specific organization.</p><h3><br>Link Scrambling</h3><p>A cobrowsing agent can view the shared website if a website contains URLS which either contain sensitive data that the agent should not be able to see. Enabling this option will mean that all link urls are replaced with random but unique urls which will obscure an sensitive data contained within the link url. If the link text contains sensitive information then PII masking should be used instead. See <a target="_blank" rel="nofollow" href="/v1/docs/cobrowse-configuring-information-security-pii">Configuring Information Security &amp; PII</a></p><h3>Laser Pointer</h3><p>If enabled, this will allow an agent to begin using the laser pointer tool without requesting permission from the end-user cobrowsing a page.</p><h3>Highlighter</h3><p>If enabled, this will allow an agent to begin using the highlighter tool without requesting permission from the end-user cobrowsing a page.</p><h3>Confidential Overlay Enable</h3><p>Enabled by default, when sensitive page elements are marked as masked from the agent, cobrowse will create transparent overlays to indicate to the end-user cobrowsing the page which elements are private and not visible to to the agent.&nbsp;</p><h3>Confidential Overlay Color</h3><p>The transparent overlays have a light red color to indicate their privacy but if that conflicts with page styles and coloring then the color can be customized to better work with the page aesthetics.&nbsp;</p><h3>File Transfer</h3><p>Provide options enabling either bidirectional or unidirectional file transfer between agent and end users. Either both an agent and client can send each other files, or only the agent can send files or only the client can or neither. All files transferred are saved as part of the session record and are scanned for known viruses. An allowable filetype configuration is available as well.</p><h3>Disable Scroll</h3><p>Disables the unlock scroll feature for agents. Ensures that the agent only looks at the screen portion presented by the user.</p><h3>Multidomain</h3><p>Required to be enabled, if a website uses multiple domains or subdomains which are intended to work together and support a cobrowse session working consistently as a user navigates between them. It is not needed if a website is only expecting to cobrowse a single domain. Your organization admin can create and edit deployments keys (see <a target="_blank" rel="nofollow" href="/v1/docs/cobrowse-deployments">CoBrowse Deployments</a>).</p><h3>Video Chat</h3><p>If enabled, this will allow an agent to request a video/voice chat session.</p><h3>Combined Session Url</h3><p>A mandatory setting if video chat is enabled. It is used facilitate a consistent video connection while a user traverses through a cobrowsing website a specific url is needed to be setup on a customer domain. See <a target="_blank" rel="nofollow" href="/v1/docs/video-chat-integration">Video Chat Integration</a></p><h3>Remote Control</h3><p>If enabled, this will allow an agent to request remote control to perform actions on a cobrowsing page on behalf&nbsp;</p><h3>Screenshot</h3><p>If enabled, it will present a button to the session agent to take a screenshot of their screen and upload it to be part of the case record. If disabled, the agent will not be able to take screenshots using the cobrowse tools.</p><h3>Inactivity Timeout Duration</h3><p>A session will timeout if no activity is present for X minutes.</p><h3>Session ID Length</h3><p>When creating a new cobrowse session, how long should the ID be. This is not client facing but will be visible to the agent and will be present in reports and logs about cobrowse sessions.</p><h3>Session Pin Length</h3><p>The pin is the code entered by the end-users attempting to share their screen with an agent. Cobrowse session pin length can be adjusted for ease of use (shorter pins) or security (longer pins).</p><h3>Startup Config</h3><p>This setting is currently only for specifying multiple Combined Session Urls for organizations with multiple deployment groups.</p><h3>Single Tab Cobrowse</h3><p>Cobrowse will track a session across multiple tabs. If a user is on a cobrowseable page and then open the new tab in the same deployment group (i.e the same website or an associated domain if multidomain is enabled), it will see the existing session and start cobrowsing the tab. The Agent will see the tab which the user is currently focused on. The user can freely switch between tabs and the cobrowse session will follow them. Single tab is more restricted for customers who are more security focused. If a session is started with this setting enabled then when a user opens a tab in the deployment group, it will not continue the cobrowse session on the new tab.</p><p>For developers: Cobrowse normally saves its session state in `window.localStorage` under keys prefixed with `SMCobrowse`. When Single Tab Cobrowse is enabled then it saves data with the same keys in `window.sessionStorage`.</p><h3>URL Invites</h3><p>This will enable a cobrowsing agent to generate a url to invite another person into viewing a cobrowse session. The agent will then be able to approve or deny requests of users who follow the link trying to join the session.&nbsp;</p><h3>Session Recording</h3><p>Set the default behavior of recording a session. Either an agent has the option to decide to record a session or every session is recorded or none are.</p><h3>Server CSS Cacheing</h3><p>CSS cacheing is an action that Cobrowse does to improve the fidelity of the cobrowse session. The cobrowse server reaches out to the customer website and grabs the css files referenced by the html. It does it once initially and then it saves the css result to speed up subsequent page loads. However, some customers might want to turn that off because their css files are unavailable to the public because the website is actually behind a vpn, in which case the Cobrowse server will delay page loads waiting for unavailable files. This option is provided to turn off this default behavior which will result in a faster page startup for private websites, but will incur a slowdown due to reprocessing CSS.&nbsp;</p><h3>Use Proxy</h3><p>If a website is entirely private or the agents or users are working behind a restrictive firewall policy then the dynamic domains and shifting ip addresses of the scaleable cobrowse server fleet can cause connection difficulties. If this setting is enabled then all cobrowse sessions will connect to a single domain, rt-proxy.screenmeet.com <span style="color: rgb(34, 34, 34);">using https and wss protocols&nbsp;</span>which will route to an appropriately local proxy to a local cobrowse server. Enabling this will add latency to every cobrowse session, but will simplify the firewall rules.</p><h3>Canvas Streaming</h3><p>If a canvas element is an essential feature of a website and sharing that content with the agent is important to a Cobrowse session, then enabling this setting will allow specially marked canvas elements to be streamed to the agent.&nbsp;</p><h3></h3><p><br></p>

CoBrowse Settings

Cobrowse 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

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