<h2>Relationships to Other Objects: Data</h2><h3>Overview</h3>This guide explains how to relate ScreenMeet Live Session records to any standard or custom Salesforce object, such as Case, Opportunity, or a custom record type. When configured, a related list on the parent record will display all ScreenMeet sessions that were launched from it.The approach uses a junction object to store the relationship between the parent record and the Live Session record. An Apex Trigger on <code>screenmeet__Live_Session__c</code> fires on insert and creates the junction record automatically. You can support multiple parent object types in a single trigger by adding a branch for each.Advanced TopicThis guide assumes familiarity with Salesforce Object Manager, Apex Triggers, and Permission Sets. Foundational knowledge of relational data models is recommended before proceeding.<hr><h3>Prerequisites</h3><ul><li>System Administrator access to the Salesforce org</li><li>ScreenMeet managed package installed and configured</li><li>The ScreenMeet widget added to the target object's page layout</li><li>Knowledge of which Salesforce object you are linking to ScreenMeet sessions (for example, <code>Case</code>, <code>Opportunity</code>)</li></ul><hr><h3>Step 1: Create the Junction Object</h3>Create one junction object for each Salesforce object you want to relate to ScreenMeet sessions. Repeat this step for each object type.<ol><li>Sign in as a System Administrator and open Setup.</li><li>Enter Object Manager in Quick Find, then open Object Manager.</li><li>Click Create in the top-right corner and choose Custom Object.</li><li>Fill in the following fields, substituting your object name where indicated:</li></ol><table style="min-width: 75px;"><tbody><tr><th colspan="1" rowspan="1">Field</th><th colspan="1" rowspan="1">Example Value (Case)</th><th colspan="1" rowspan="1">Example Value (Opportunity)</th></tr><tr><td colspan="1" rowspan="1">Label</td><td colspan="1" rowspan="1"><code>ScreenMeet Case Session</code></td><td colspan="1" rowspan="1"><code>ScreenMeet Opportunity Session</code></td></tr><tr><td colspan="1" rowspan="1">Plural Label</td><td colspan="1" rowspan="1"><code>ScreenMeet Case Sessions</code></td><td colspan="1" rowspan="1"><code>ScreenMeet Opportunity Sessions</code></td></tr><tr><td colspan="1" rowspan="1">Object Name</td><td colspan="1" rowspan="1"><code>ScreenMeet_Case_Session</code></td><td colspan="1" rowspan="1"><code>ScreenMeet_Opportunity_Session</code></td></tr><tr><td colspan="1" rowspan="1">Record Name</td><td colspan="1" rowspan="1"><code>Case Session</code></td><td colspan="1" rowspan="1"><code>Opportunity Session</code></td></tr><tr><td colspan="1" rowspan="1">Data Type</td><td colspan="1" rowspan="1">Text</td><td colspan="1" rowspan="1">Text</td></tr></tbody></table><ol><li>Click Save. Note the API name assigned to your new object (for example, <code>ScreenMeet_Opportunity_Session__c</code>). You will need this in the trigger code.</li></ol><hr><h3>Step 2: Add Lookup Fields to the Junction Object</h3>Add two lookup fields to the junction object: one pointing to your parent object (for example, Opportunity) and one pointing to ScreenMeet Live Session.Use Lookup, Not Master-Detail, for ScreenMeet Live SessionThe <code>screenmeet__Live_Session__c</code> object is part of a managed package. Salesforce does not allow Master-Detail relationships to be created against managed objects from outside the package. Select Lookup Relationship for the ScreenMeet Live Session field or the field creation will fail.From your new junction object, open Fields &amp; Relationships and complete the following:<h4>Field 1: Parent Object Lookup</h4><ol><li>Click New.</li><li>Select Lookup Relationship (or Master-Detail Relationship if preferred and supported for your object), then click Next.</li><li>From Related To, select your parent object (for example, Opportunity), then click Next.</li><li>Set the Field Label and Field Name to match the object name (for example, <code>Opportunity</code>).</li><li>Click through the remaining screens and click Save &amp; New.</li></ol><h4>Field 2: ScreenMeet Live Session Lookup</h4><ol><li>Select Lookup Relationship, then click Next.</li><li>From Related To, select ScreenMeet Live Session, then click Next.</li><li>Set the Field Label to <code>ScreenMeet Live Session</code> and the Field Name to <code>ScreenMeet_Live_Session</code>.</li><li>Click through the remaining screens and click Save.</li></ol>Verify Field API Names Before Writing Trigger CodeAfter saving, go to Fields &amp; Relationships on the junction object and note the exact API names for both fields. The Field Name you enter during setup becomes the API name with <code>__c</code> appended. Use these exact values in the trigger code in Step 3.<hr><h3>Step 3: Identify the Parent Object Type Value</h3>The trigger uses the <code>screenmeet__parentObjectType__c</code> field on the Live Session record to determine which junction object to write to. You must know the exact value this field contains when a session is started from your target object.To find the value, start a test ScreenMeet session from the target object record, then open the resulting Live Session record in Salesforce and check the <code>screenmeet__parentObjectType__c</code> field. Common values are <code>case</code> and <code>opportunity</code> (lowercase).Value Must Match ExactlyThe string comparison in the trigger is case-sensitive. If the field contains <code>opportunity</code> and the trigger checks for <code>Opportunity</code>, the branch will not fire and no junction record will be created.<hr><h3>Step 4: Add the Apex Trigger</h3>There can only be one trigger per object event on <code>screenmeet__Live_Session__c</code>. If you are adding support for a second object type and a trigger already exists, edit the existing trigger to add a new branch rather than creating a new one.<ol><li>Open Object Manager.</li><li>Find ScreenMeet Live Session (API name: <code>screenmeet__Live_Session__c</code>) and open it.</li><li>Click Triggers, then click New (or open the existing trigger to edit it).</li><li>Paste or update the trigger code below, adding or adjusting branches for each object type you are supporting.</li><li>Click Save.</li></ol>The following example supports both Case and Opportunity. Substitute the correct junction object API names, field API names, and <code>parentObjectType__c</code> values for your implementation.Namespace Prefix on Managed Junction ObjectsIf your Case junction object was created by the ScreenMeet managed package installer, its API name and field names will include the <code>screenmeet__</code> namespace prefix (for example, <code>screenmeet__ScreenMeet_Case_Session__c</code>). Junction objects you create manually will not have a prefix. Check Object Manager to confirm the correct API names before saving the trigger.<pre><code class="language-plaintext">trigger Live_Link_Object_Trigger on screenmeet__Live_Session__c (after insert) {
 if (Trigger.isInsert) {
 for (screenmeet__Live_Session__c newSessionRow : Trigger.new) {

 // Case branch - update object and field API names if your junction object
 // was installed by the managed package (e.g. screenmeet__ScreenMeet_Case_Session__c)
 if (newSessionRow.screenmeet__parentObjectType__c == 'case') {
 screenmeet__ScreenMeet_Case_Session__c junction = new screenmeet__ScreenMeet_Case_Session__c(
 screenmeet__ScreenMeet_Live_Session__c = newSessionRow.Id,
 screenmeet__Case__c = newSessionRow.screenmeet__parentObjectId__c,
 Name = newSessionRow.screenmeet__session_type__c + ': ' + newSessionRow.screenmeet__Session_Id__c
 );
 insert junction;

 // Opportunity branch - substitute your junction object and field API names
 } else if (newSessionRow.screenmeet__parentObjectType__c == 'opportunity') {
 ScreenMeet_Opportunity_Session__c junction = new ScreenMeet_Opportunity_Session__c(
 ScreenMeet_Live_Session__c = newSessionRow.Id,
 Opportunity__c = newSessionRow.screenmeet__parentObjectId__c,
 Name = newSessionRow.screenmeet__session_type__c + ': ' + newSessionRow.screenmeet__Session_Id__c
 );
 insert junction;

 // Add additional else if branches here for other object types
 }
 }
 }
}</code></pre><hr><h3>Step 5: Set Permissions on the Junction Object</h3>Repeat the following for each junction object you created. Two layers of access must be configured: the service account needs Create access to write junction records, and agents need Read access to view the related list.<h4>Service Account Permissions</h4><ol><li>Go to Setup and open Permission Sets.</li><li>Open the permission set assigned to the ScreenMeet service account. If you are unsure which one, go to the service account user record and check Permission Set Assignments.</li><li>Click Object Settings and find the junction object.</li><li>Click Edit and enable Read, Create, Edit, and all Field Permissions.</li><li>Click Save.</li></ol>Missing Service Account Permissions Will Break Session CreationIf the service account does not have Create access on the junction object, the trigger will throw a <code>System.SecurityException: Access to entity denied</code> error when a session is started, causing the session launch to fail for the agent.<h4>Agent Read Access</h4>The ScreenMeet Agent permission set is part of the managed package and cannot be edited. Instead, configure object-level Read access at the profile level and open up record visibility org-wide.Set Organization-Wide Default to Public Read Only:<ol><li>Go to Setup and open Sharing Settings.</li><li>Scroll to your junction object in the Organization-Wide Defaults table and click Edit.</li><li>Set the default access to Public Read Only and click Save.</li></ol>Grant Read access via Profile:<ol><li>Go to Setup and open Profiles.</li><li>Open the profile assigned to your ScreenMeet agents.</li><li>Find the junction object under Custom Object Permissions, enable Read, and click Save.</li><li>Repeat for any other profiles that require visibility into ScreenMeet session related lists.</li></ol>Two Layers of Access RequiredSalesforce enforces object-level permissions and record-level sharing separately. The OWD setting controls which records a user can see, but the profile must still grant Read access to the object itself before any records are visible. Both must be configured.<hr><h3>Step 6: Configure the Page Layout</h3><ol><li>Navigate to a record of the target object type (for example, an Opportunity).</li><li>Click the Gear icon in the top right and select Edit Object.</li><li>Click Page Layouts and open the layout you want to update.</li><li>Scroll to the Related Lists section. If the junction object's related list is not already on the layout, drag it in from the palette.</li><li>Click the Wrench icon on the related list and add the following columns:</li></ol><ul><li>Junction Object: Record Name (for example, Opportunity Session)</li><li>ScreenMeet Live Session: Live Session (provides the link to the session record)</li><li>ScreenMeet Live Session: Status</li><li>ScreenMeet Live Session: Created Date</li></ul><ol><li>Set Sort By to ScreenMeet Live Session: Created Date and Order to Descending.</li><li>Click OK, then click Save.</li></ol>Duplicate Related ListsIf you see two related lists for the same junction object on the page layout, check Fields &amp; Relationships on the junction object for duplicate lookup fields pointing to the same parent object. Delete the extra field and the corresponding related list will be removed automatically.<hr>

Salesforce Junction Object

Relationships to Other Objects: Data

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