ScreenMeet has the ability to customize the domain that is shown during a given ScreenMeet Live session.There are a two options available in order to setup a custom domain:1) Using a URL with a custom subdomain and <a target="_blank" rel="noopener noreferrer nofollow" href="http://screenmeet.com/">screenmeet.com</a> top-level-domain.With this approach, we could use URL's such as &lt;custom&gt;.<a target="_blank" rel="noopener noreferrer nofollow" href="http://screenmeet.com/">screenmeet.com</a> - eg, <a target="_blank" rel="noopener noreferrer nofollow" href="http://salesforce.screenmeet.com/">customdomain.screenmeet.com</a>This option is the easiest and would require no additional effort from you.&nbsp; &nbsp; &nbsp;This is an additional, optional ScreenMeet service that is offered. Please contact us at <a target="_blank" rel="noopener noreferrer nofollow" href="mailto:support@screenmeet.com">support@screenmeet.com</a> for pricing and to setup your custom domain.2) Using a fully custom URLWith this approach, we could use any URL. eg: <a target="_blank" rel="noopener noreferrer nofollow" href="http://meet.salesforce.com/">meet.customdomain.com</a> or similar.There are a few possible technical implementation paths here:<ol><li>Your organization could set up a proxy at a URL of their choice and use <a target="_blank" rel="noopener noreferrer nofollow" href="https://live.screenmeet.com/">https://live.screenmeet.com</a> as the origin. Proxy should be configured to forward querystrings / headers / etc with one important exception for the host header. The host&nbsp;header should be hard-coded to&nbsp;live.screenmeet.com.</li><li>Your organization&nbsp;could set up DNS CNAME entries to point at a CDN end-point provided by screenmeet. In this case, we would also have to set up an SSL certificate, for which we also have several options:<ul><li>ScreenMeet could use AWS ACM to provision the SSL certificate for the desired hostname (eg, <a target="_blank" rel="noopener noreferrer nofollow" href="http://meet.salesforce.com/">meet.customdomain.com</a>). In this case, there would be a total of 2 CNAME entries required, one for the actual hostname, and another for SSL certificate validation, which would look something like this:&nbsp;_<a target="_blank" rel="noopener noreferrer nofollow" href="http://a79865eb4cd1a6ab990a45779b4e0b96.salesforce.com/">a79865eb4cd1a6ab990a45779b4e0b96.customdomain.com</a>. With this approach, ScreenMeet could manage renewals of this certificate automatically as it expires annually / bi-annually. If someone were to click the certificate info in their browser it would show that the certificate is issued by Amazon.</li><li>Your organization could provide an SSL certificate they provision themselves to ScreenMeet, which we could import into our CDN. This would require bi-annual maintenance/updates as all SSL certificates have a maximum lifetime of 2 years.</li></ul></li></ol>

Live Custom Domain

Custom Domain

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

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

Beam Groups: Setup, Settings, and Access Management

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